Werk 06 — who carries it
The platform werk owns what everything else stands on. A migration that lands on an unpaved substrate produces the same delivery friction at a different address, with a cloud bill attached.
The offer
A substrate product teams can ship on without asking permission: cloud landing zones, an internal platform, and the observability that makes production legible.
Account and network topology, security baseline, migration waves and the cost model that comes with them.
Golden paths, self-service environments, templates and the paved road that removes the ticket queue between a team and production.
Telemetry, SLOs, alerting that pages a human only when it should, and the on-call model behind it.
Everything declared, reviewed and reproducible, with drift detection and automated promotion between environments.
Platform assessment, target design, cost and reliability plan.
Standards, landing-zone design, vendor and cost arbitration.
The platform built and the teams migrated onto it.
State of the proof
Experiences that prove it
Sub-capabilities and evidence
Publishable figures
Questions
- Which clouds has the collective delivered on?
- AWS at PMU and at Societe Generale, where the BU MassMarketing estate left owned datacenters and total cost of ownership fell 37% on cloud-based and API-based application patterns. And a secure European cloud at Satelia, chosen because a cardiovascular telemonitoring platform entering the EU market carries data residency and medical-device constraints that decide the substrate for you.
- Is platform engineering the same as cloud migration?
- No. Migration moves an estate once. Platform engineering builds the paved road that keeps every team after you from rebuilding the same pipeline — which is what was industrialized at AXA as a group software and digital factory, and what made a 2.5-month time-to-market possible on the product that ran on it.
- What is honestly not proven here?
- Infrastructure as code, Kubernetes and GitOps are declared. They are standard components of the mandates above and no published case isolates them, so they are listed as declared rather than implied. A buyer who needs a Kubernetes platform built from zero should ask what has been run, and will get a straight answer.