The BuiltForProd Standard
The BuiltForProd Standard defines what production-ready means: a system is built for production when it is Secure, Reliable, Observable, Scalable, Automated, Recoverable, Compliant and Operable. Each property is a design constraint, not a later upgrade, and each pillar page on this site names the units, services and workflows in each Baseline edition and its blueprints that deliver it.
The eight pillars
| Pillar | A BuiltForProd system... | Page |
|---|---|---|
| Secure | protects identities, data, workloads and supply chains | Secure |
| Reliable | continues operating through expected failures | Reliable |
| Observable | makes its state and behavior visible to operators | Observable |
| Scalable | grows predictably without architectural failure | Scalable |
| Automated | makes routine provisioning, deployment, validation and operations repeatable | Automated |
| Recoverable | has tested recovery mechanisms for failures and disasters | Recoverable |
| Compliant | can demonstrate controls and evidence consistently | Compliant |
| Operable | can be understood, operated, troubleshot and changed safely by humans | Operable |
The BuiltForProd test
The test is one question, "Would you trust this in production?", asked eight ways:
| Dimension | Question |
|---|---|
| Security | Is it secure by default? |
| Reliability | What happens when something fails? |
| Observability | Can operators see what is happening? |
| Scalability | What happens when demand grows 10x? |
| Automation | How much depends on manual intervention? |
| Recovery | Can the system actually be restored? |
| Compliance | Can controls and evidence be demonstrated? |
| Operations | Can another engineer operate it safely? |
A demo passes none of these. A system that "works" answers only the first half of each question. The pillar pages answer all eight for each edition, the AWS, Azure and GCP Enterprise Baseline, and the blueprints that deploy on it, with the concrete mechanism and how you verify it in your own environment.
How the pillars map to the platform
Each pillar is delivered by several parts of the platform, and most parts serve more than one pillar. The table shows the principal mechanisms per edition; the pillar pages hold the full lists.
| Pillar | AWS Enterprise Baseline | Azure Enterprise Baseline | GCP Enterprise Baseline |
|---|---|---|---|
| Secure | Three service control policies, IAM Identity Center, GitHub OIDC, KMS, SOPS, GuardDuty, Security Hub, Firewall Manager WAF, isolation domains | Azure Policy guardrails at mg-acme, Entra groups with Conditional Access and PIM, federated identities, Key Vault keys, Defender for Cloud, Front Door WAF, Azure Firewall | 19 organization policy constraints, IAM deny policies, Google groups with Privileged Access Manager, Workload Identity Federation, Cloud KMS, Security Command Center, Cloud Armor |
| Reliable | Three Availability Zones, NAT per AZ, multi-AZ DocumentDB and Redis in staging and prod, ArgoCD HA, autoscalers and disruption budgets | Firewall and runners across three zones, zone-redundant storage, zone-redundant Cosmos DB and Redis in staging and prod, ArgoCD HA, autoscalers and disruption budgets | Regional GKE across three zones in staging and prod, a Valkey replica with automatic failover, regional Firestore, ArgoCD HA, autoscalers and budgets |
| Observable | Organization CloudTrail, VPC Flow Logs, the CloudWatch OAM sink, seven CIS alarms, Fluent Bit, X-Ray | Activity Log and Entra logs in the audit workspace, VNet flow logs, 10 activity-log and 6 KQL alerts, Defender alerts, Container Insights, Application Insights | Two aggregated organization sinks, flow logs on every workload subnet, a metrics scope over every project, 13 log-based detections, Cloud Trace |
| Scalable | A /8 plan for 16 regions and 8 stages per region, IPAM, Karpenter and Cluster Autoscaler, Spot runners that scale to zero | A /8 plan, AKS pods outside the VNet, Node Auto Provisioning under a vCPU ceiling, Container Apps jobs that scale from zero, Databricks job clusters | A /8 plan with eight stage blocks per region, node auto-provisioning under CPU and memory ceilings, bounded Dataproc Serverless batches |
| Automated | Plan on pull request, apply on merge, drift detection, guard scripts, immutable images promoted by pull request, secrets synced on merge | Plan and apply through a federated identity on Container Apps runners, drift detection, guard scripts, locked registry tags, secrets synced to Key Vault | Plan and apply through Workload Identity Federation, drift detection, guard scripts, immutable Artifact Registry tags, secrets synced to Secret Manager |
| Recoverable | Versioned and locked state, DocumentDB backups and deletion protection in prod, S3 versioning, Git revert, promotion of a previous tag | Versioned state with 90-day soft delete, delete locks on the prod data stores, immutable audit storage, Git revert, promotion of a previous tag | Versioned state with soft delete, Firestore point-in-time recovery and daily backups in prod, deletion protection, Git revert, previous tag |
| Compliant | The SOC 2 baseline conformance pack, 28 further packs, Security Hub standards, an audit-protection SCP, auditor permission sets that cannot read data | A custom SOC 2 baseline initiative in Audit, built-in framework initiatives in DoNotEnforce, DenyAction on the audit trail, write-once audit storage | CIS Google Cloud Foundations detections, Security Command Center, an IAM deny policy on the audit trail, retention-locked archives, auditor deny policies |
| Operable | Workbooks and runbooks, CODEOWNERS by blast radius, twelve named roles, TODO: and @optional: tags, one priced switch file per concern | CODEOWNERS by blast radius, twelve named roles as Entra groups, TODO: and @optional: tags, network.hcl and security.hcl with the price beside each switch | CODEOWNERS by blast radius, twelve named roles as Google groups, TODO: and @optional: tags, network.hcl, security.hcl and identity.hcl |
How to read the pillar pages
Every pillar page has the same three parts: what the pillar means, how each edition delivers it, and how you verify it in your own environment without changing anything. The architecture overview gives the map the pillar pages assume, and the security posture summary condenses the Secure and Compliant pillars for a reviewer. The public overviews of the AWS, Azure and GCP Enterprise Baselines introduce each edition.