The Cloud Engineering standard has moved from scoping into active drafting. Fourteen organisations across five countries are contributing to the employer council, including three that operate regulated workloads.
The draft capability areas
- Platform design — choosing an architecture that fits the workload rather than the trend.
- Infrastructure as code — reproducible environments, reviewed and versioned.
- Resilience — failure modes, redundancy, and what actually happens in a region outage.
- Cost discipline — making spend visible and defensible before finance asks.
- Cloud security — identity, network boundaries, least privilege by default.
- Migration — moving live systems without a weekend of downtime.
The contested one
Cost discipline generated the most debate. One view held it was a finance responsibility rather than an engineering capability. The council rejected that. In practice the architectural decisions that determine spend are made by engineers, often months before anyone in finance sees a bill.
You cannot separate resilience from cost. Every redundancy decision is a spending decision, and pretending otherwise produces architectures nobody can afford to run.
Timeline
Draft descriptors go to public consultation in November, with a pilot assessment cohort in Q1 2027 and full publication expected in the first half of the year. Providers interested in accreditation against the standard can register interest now.