Cloud Transformation at Allianz: Building an Internal Cloud Platform (FCP)

A senior engineer needs a test environment before a Friday release. She files the ticket and waits, because that is what the ticket has always meant: weeks of approvals when everything goes smoothly. At its worst, standing up new infrastructure at Allianz took 12 to 18 months, between manual sign-offs, bespoke networking per entity and a queue that no single team owned.

The waiting was only half the damage. Engineers who wait build workarounds: local setups that don't match production, shared servers nobody administers, deployments that bypass the approval process entirely. For one of the world's largest insurers, handling regulated financial data in every jurisdiction it operates in, that shadow estate was the bigger liability, and no dashboard showed it.

I joined as technical product owner for the Future Cloud Platform (FCP), and the decision that shaped everything else was what to measure. I picked the time between an engineer asking for an environment and deploying their first code into it. That one number forces trade-offs a milestone plan lets you avoid. Golden paths replaced bespoke setups, which meant telling country entities that their custom configurations were going away. Some of those conversations were long. The bet was that a compliant default available in days would win against a tailored setup that takes a year, and that engineers would show their preference by where they put their workloads.

FCP put a policy-controlled boundary around all Allianz workloads: public-cloud flexibility with private-grade compliance. Multiple cloud vendors, fit for purpose per entity, under one security baseline. Data sovereignty was a matter of configuration, so Australian customer data stays in Australia. Underneath, platform engineering ran on Kubernetes, Helm and Argo. My layer was the one above the plumbing: the contracts, defaults and paved roads that decide whether engineers adopt a platform or work around it.

The failure mode I most wanted to avoid is a familiar one. Architecture settles for months, then Security and Compliance review it at the end and find structural problems. So IT, Security and Compliance sat inside platform governance from the start, and their requirements became pipeline checks: automated auditing, GDPR-compliant data handling, region-specific hosting. Engineers under deadline take the compliant path when it is also the quick one, so the checks had to live in the pipeline, where following them costs nothing.

The migration ran on-premise and cloud in parallel throughout, so mission-critical systems never went dark. Work that had previously taken 12 to 18 months completed in four, with zero downtime.

• Standard environment provisioning went from months to days, through self-service templates and Infrastructure-as-Code.
• Operations standardised across multiple providers and 70+ countries.
• Engineering teams across the group got CI/CD, observability and golden paths as platform defaults.
• The platform now carries Allianz's enterprise AI workloads, including the Enterprise Knowledge Assistant processing 90,000+ paragraphs for customer service.

The platform self-service and paved-road patterns I used here inform The AI-native Platform Playbook.