BuiltForProd Baseline
BuiltForProd Baseline is a ready-to-deploy cloud foundation, delivered as infrastructure as code in three editions: the AWS, Azure and GCP Enterprise Baselines. The BuiltForProd team customizes it from the base repositories, deploys it into your own cloud environment, and hands over the repositories and the documentation. From that point it is yours: infrastructure as code in your own Git organization and your own cloud, ready for workloads and ready to grow to more isolation units, regions and environments.
What it is
The Baseline is the starting point for building production the right way, and the organization standard every later environment is based on. Every edition is one repository that defines the organization structure, the guardrails, the hub network, the security and audit services, identity for people and pipelines, the state backend and the plan, apply and drift-detection workflows.
| Edition | Repository | What it creates |
|---|---|---|
| AWS Enterprise Baseline | acme-aws-platform-baseline | The AWS Organization, two organizational units and 15 accounts with service control policies and a tag policy; IPAM, a hub VPC with centralized egress, a Transit Gateway with isolation domains and a spoke VPC per workload account; delegated security services, an organization CloudTrail and AWS Config conformance packs; IAM Identity Center and GitHub OIDC |
| Azure Enterprise Baseline | acme-azure-platform-baseline | Three management groups and 15 subscriptions with Azure Policy guardrails; a hub VNet with Azure Firewall and a spoke VNet per stage; Microsoft Defender for Cloud, Activity Log and Microsoft Entra logs in immutable audit storage; Entra groups mapped to Azure RBAC; federated managed identities per repository and stage |
| GCP Enterprise Baseline | acme-gcp-platform-baseline | Three folders and 15 projects with organization policies and an IAM deny policy; a Shared VPC host with a hub VPC and isolated prod and nonprod VPCs; Security Command Center and aggregated audit logs in acme-core-audit; Google groups bound to IAM roles; Workload Identity Federation for pipelines |
For the AWS edition, the offerings note lists the capabilities as a fully automated CI/CD GitOps workflow with self-hosted runners and OIDC federation; multi-region scaling with a hub-and-spoke VPC architecture, Transit Gateway routing and IPAM; centrally managed IAM Identity Center and Client VPN; compliance readiness for SOC 2, HIPAA, PCI DSS 4.0, CMMC, NIST CSF and the CIS AWS Foundations Benchmark; and centralized audit, logging, compliance monitoring and drift detection.
The Azure edition delivers GitOps pipelines with federated identities and self-hosted runners as an Azure Container Apps job; one address plan with /12 per region and Azure Firewall egress or a NAT gateway per spoke; Microsoft Entra groups, with Privileged Identity Management behind a switch and Conditional Access in report-only mode until you enforce it; and continuous evaluation by Azure Policy, with the Microsoft cloud security benchmark and a custom SOC 2 baseline initiative on and nine further built-in framework initiatives by switch, all of them evaluating compliance without blocking a deployment.
The GCP edition delivers GitOps pipelines through Workload Identity Federation with optional self-hosted runners; one address plan, one Cloud NAT per VPC and no external IP on any VM; Google groups with Privileged Access Manager for Owner; remote access through Identity-Aware Proxy, with no VPN to run; and continuous evaluation through 19 organization policy constraints, Security Command Center and 13 log-based detections, eight of them from the CIS Google Cloud Foundations Benchmark.
The architecture overview draws each edition; the AWS, Azure and GCP product pages list what each offering includes.
What a customer receives
| Deliverable | Contents |
|---|---|
| Repositories | The Baseline repositories, customized to your organization and delivered into your GitHub organization. On AWS they are customized with your namespace, domain, root emails, GitHub organization and SSO group ids; on Azure with your namespace, domain, tenant id, billing scope or subscription ids, group name prefix, GitHub organization and security mailbox; on GCP with your namespace, domain, organization, billing account and customer ids, GitHub organization and security mailbox. With Full Deployment with Blueprints, the blueprint repositories as well |
| A deployed environment | The foundation, applied by the BuiltForProd team and handed over working. On AWS that is the 15 accounts, on Azure the 15 subscriptions, on GCP the 15 projects, each with the network, the security services, identity and the pipelines |
| Documentation | Architecture decision records, how-to guides, troubleshooting manuals, FAQs and scaling best practices: the deployment workbooks, plus access to this site for your organization |
Every value that had to be set for your deployment carries a TODO: comment in the code and every optional choice an @optional: comment, so your team can find both at any time.
The three deployment options
| Option | What it includes |
|---|---|
| Standard Deployment | The complete multi-account environment set up by the BuiltForProd team; full handover of the customized repositories and infrastructure code; the extensive documentation handover |
| Full Deployment with Blueprints | Everything in Standard Deployment plus any two blueprints from the blueprint catalog, each deployed and working. The purpose is a tangible, working reference architecture that guides your teams' own workload deployments |
| Blueprint Deployment | For existing customers who already run the Baseline and want one or more additional blueprints deployed, chosen from the blueprint catalog |
Every option is fully executed by the BuiltForProd team. Blueprints are described on the blueprints page; purchase paths and the license are on purchasing and licensing.
Editions
The Baseline comes in three editions. Each is the same foundation, measured against the same BuiltForProd Standard, built with the native mechanisms of its cloud.
| Edition | What it is |
|---|---|
| AWS Enterprise Baseline | A production-ready AWS foundation engineered around the AWS Well-Architected Framework: 15 accounts in two organizational units, hub-and-spoke networking, delegated security services and 29 AWS Config conformance packs, with the SOC 2 pack on by default |
| Azure Enterprise Baseline | A production-ready Azure foundation engineered around the Azure Well-Architected Framework: 15 subscriptions under three management groups, hub-and-spoke networking with Azure Firewall, Azure Policy guardrails, Microsoft Defender for Cloud, and the Microsoft cloud security benchmark and a SOC 2 baseline initiative evaluated by Azure Policy, with nine further initiatives by switch |
| GCP Enterprise Baseline | A production-ready GCP foundation engineered around the Google Cloud Architecture Framework: 15 projects in three folders, a Shared VPC with isolated prod and nonprod networks, 19 organization policy constraints and an IAM deny policy, Security Command Center and aggregated audit logs |
Why a baseline rather than a build
Every engineering team eventually solves the same problems: how to structure cloud accounts, manage environments, secure access, deploy reliably, handle secrets, monitor everything, recover from failure and satisfy an audit. The Baseline is those answers, already made and already reviewed, measured against the BuiltForProd Standard. Your competitive advantage is your application, not your network design.