Skip to main content

BuiltForProd documentation

This site documents the three BuiltForProd offerings: the Baseline (a production-ready cloud foundation, in AWS, Azure and GCP editions), the Blueprints (production-ready reference architectures deployed on the Baseline) and Managed (engineers who operate and evolve the result). The Overview set you are reading is public. The set for each Baseline edition and each blueprint opens to customers who hold that product.

What the documentation covers​

SetWhat it holdsWho can read it
PlatformThe BuiltForProd Standard, key concepts, the products, the service explainers, the glossary, support and trust pagesEveryone
AWS Enterprise BaselineThe landing zone: 15 accounts, hub-and-spoke network, security services, identity, delivery pipelineOverview public; the rest needs sign-in and the AWS Enterprise Baseline
Azure Enterprise BaselineThe landing zone: 15 subscriptions under one management-group tree, hub-and-spoke network with Azure Firewall, security, identity, delivery pipelineOverview public; the rest needs sign-in and the Azure Enterprise Baseline
GCP Enterprise BaselineThe landing zone: 15 projects in three folders, a Shared VPC, organization policies, security, identity, delivery pipelineOverview public; the rest needs sign-in and the GCP Enterprise Baseline
BlueprintsProduction-ready reference architectures for specific workloads, deployed on the Baseline. The catalog lists every blueprintEach overview public; the rest needs sign-in and that blueprint

The editions​

The Baseline comes in three editions, one per cloud: the AWS, Azure and GCP Enterprise Baselines. Every edition is measured against the same BuiltForProd Standard. Blueprints are built for a specific cloud, and the blueprint catalog lists each one with the cloud it runs on. The Baseline product page compares the editions.

How to navigate​

  • The navigation bar switches between the Overview pages and the documentation for each cloud and blueprint.
  • Every page ends with What's next and Related topics. Follow them and you read the set in a sensible order.
  • Sample values such as acme, company.com, the home regions us-west-2, eastus2 and us-west1, the AWS account ids 111111111111 to 151515151515 and 171717171717, the Microsoft Entra tenant id aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa, the Azure subscription ids such as 11111111-1111-1111-1111-111111111111 and the GCP organization id 161616161616 are placeholders. When you sign in and your organization profile is filled in, the pages show your own values. How to use these docs explains the mechanism.
  • Search is split by set, so a query on a Baseline page searches that edition's set first.

Where to start by role​

You areStart here
Deciding whether to buyWhat is BuiltForProd, then the products and purchasing and licensing
An architectArchitecture overview, then the BuiltForProd Standard
A platform or DevOps engineerKey concepts, then Terragrunt units and stacks
A developer or data engineerKey concepts, then the blueprints
A security reviewer or auditorSecurity posture summary, then Compliant
An operatorOperable, then support options

The full ordered lists are on reading paths by role.

The standard behind every page​

Everything BuiltForProd ships is measured against eight properties: Secure, Reliable, Observable, Scalable, Automated, Recoverable, Compliant and Operable. The BuiltForProd Standard defines each one and names the mechanism in the code that delivers it. The prerequisites page lists what your organization needs in place before a deployment is handed over.