Allianz Future Cloud Platform
The Allianz Future Cloud Platform is an internal developer platform powering cloud-native insurance microservices at Allianz. Built on Kubernetes and AWS, it provides platform engineering capabilities including service deployment, infrastructure management, observability, and GitOps automation across Allianz's global insurance operations.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Allianz Future Cloud Platform the way a machine reads it — 65 machine-readable artifacts across 5 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Allianz Future Cloud Platform scores 49.5/100 (developing), with a separate agent-readiness read of 45/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Allianz Future Cloud Platform
Each block below is one kind of artifact we hold for Allianz Future Cloud Platform. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 5
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Allianz Future Cloud Platform Deployments API
Deployment lifecycle management operations
Allianz Future Cloud Platform Infrastructure API
Infrastructure provisioning and management operations
Allianz Future Cloud Platform Namespaces API
Kubernetes namespace management operations
Allianz Future Cloud Platform Observability API
Monitoring, metrics, and alerting configuration operations
Allianz Future Cloud Platform Services API
Service registration and management operations
Features 6
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Kubernetes Platform Engineering
Internal developer platform built on Kubernetes (EKS) providing standardized deployment, scaling, and orchestration for insurance microservices.
GitOps Deployment
ArgoCD and Tekton-based CI/CD pipelines enabling GitOps workflows for continuous delivery of insurance applications.
Infrastructure as Code
Terraform and Crossplane-based infrastructure management enabling repeatable, auditable cloud resource provisioning.
Observability Stack
Prometheus, Grafana, and OpenTelemetry based observability platform providing metrics, tracing, and alerting for platform services.
Multi-tenant Architecture
Namespace-level multi-tenancy supporting multiple insurance product teams on shared Kubernetes infrastructure.
Event Streaming
AWS MSK (Managed Kafka) for high-throughput event streaming between insurance microservices and downstream consumers.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Spectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
JSON Schema 12
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
DeployServiceRequest
JSON SCHEMADeploymentList
JSON SCHEMADeployment
JSON SCHEMAInfrastructureResource
JSON SCHEMAMetricsResponse
JSON SCHEMANamespaceList
JSON SCHEMANamespace
JSON SCHEMAProvisionResourceRequest
JSON SCHEMARegisterServiceRequest
JSON SCHEMAResourceRequirements
JSON SCHEMAServiceList
JSON SCHEMAService
JSON SCHEMAScroll within the panel for all 12 ·
JSON Structure 12
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Platform Services Deploy Service Request Structure
JSON STRUCTUREPlatform Services Deployment List Structure
JSON STRUCTUREPlatform Services Deployment Structure
JSON STRUCTUREPlatform Services Infrastructure Resource Structure
JSON STRUCTUREPlatform Services Metrics Response Structure
JSON STRUCTUREPlatform Services Namespace List Structure
JSON STRUCTUREPlatform Services Namespace Structure
JSON STRUCTUREPlatform Services Provision Resource Request Structure
JSON STRUCTUREPlatform Services Register Service Request Structure
JSON STRUCTUREPlatform Services Resource Requirements Structure
JSON STRUCTUREPlatform Services Service List Structure
JSON STRUCTUREPlatform Services Service Structure
JSON STRUCTUREScroll within the panel for all 12 ·
Examples 12
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 12 ·
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Insurance Microservice Deployment
Deploy and manage Kotlin and Java insurance microservices on the platform with standardized CI/CD pipelines and GitOps workflows.
Platform Onboarding
Onboard new insurance product teams onto the shared Kubernetes platform with pre-configured namespaces and RBAC policies.
Observability and Monitoring
Configure monitoring dashboards and alerting for insurance services using the platform's built-in Prometheus and Grafana stack.
Infrastructure Provisioning
Provision cloud infrastructure resources using Terraform and Crossplane through the platform's infrastructure API.
Integrations 6
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Amazon Web Services
Primary cloud provider with EKS, MSK, ElastiCache Redis, and storage services powering the platform.
ArgoCD
GitOps continuous delivery for declarative application deployment and state synchronization.
Terraform
Infrastructure as code for cloud resource provisioning and management integrated with Atlantis for PR automation.
Crossplane
Multi-cloud resource management extending Kubernetes for cloud-agnostic infrastructure provisioning.
OpenTelemetry
Distributed tracing and metrics collection across microservices for observability and performance analysis.
Apache Kafka
AWS MSK for event-driven communication between insurance microservices and downstream systems.
Resources
Every other property we hold for Allianz Future Cloud Platform — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 3
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/allianz-future-cloud-platform · machine-readable index on apis.io