Cloud Platform
One platform layer that every division's services deploy onto: account and network topology, identity, policy and cost controls, reproducible environments, and pipelines that gate on real signal. The point is that a division ships product, not infrastructure.
Inside the platform
Landing zones
Account topology, identity, network and policy established before the first workload lands.
Delivery pipelines
One signed artefact promoted through environments, with rollback as a promotion in reverse rather than a rebuild.
Container platform
Cluster design and GitOps delivery, with platform runbooks maintained centrally.
Observability
Metrics, logs and traces wired to meaningful service objectives, with on-call practice and post-incident review.
The shape of the work
One promotion path, one artefact
The same signed build moves through every environment. Rollback is a promotion in reverse, not a rebuild — and every stage reports to the same observability layer.
Used across the group
- Every division
Ownership
A shared platform. It has no natural home in any single unit, so the group funds it centrally and the shared engineering bench maintains it. Every company and division draws on the same version.
How we decide what is sharedOther platforms
Firmware SDK
The common embedded foundation — hardware abstraction, drivers, secure boot and update, with timing you can reason about.
Read moreDevice Management
Fleet identity, provisioning and health — knowing what is deployed, where, running what.
Read moreOTA Platform
Staged, reversible firmware campaigns across a fleet — the return path designed at the same time as the forward one.
Read moreBuilding something that needs Cloud Platform?
Tell us the constraints and we will come back with how this platform would carry them — or say plainly if it would not.