GCP Enterprise Baseline
The BuiltForProd GCP Enterprise Baseline is the Google Cloud landing zone your workloads run on: 15 projects in three folders under your organization, a Shared VPC, organization policies, security and audit services, and the pipelines that change all of it. It is engineered around the Google Cloud Architecture Framework and deployed as code into your own Google Cloud organization.
It is one of three editions of the BuiltForProd Baseline, alongside the AWS and Azure Enterprise Baselines. Every edition solves the same problem, a foundation that is secure, repeatable and owned by the team that runs on it, using the native mechanisms of its cloud.
What it deploys
| Area | What the code creates |
|---|---|
| Organization | The folders core, plat and backup, ten core projects that run the landing zone (root, audit, security, identity, network, DNS, artifacts, automation, corporate and public), the backup project with the protected backup vaults and the stages' Cloud SQL and Compute Engine backup plans, and four platform projects where workloads live, one per stage: acme-plat-sandbox, acme-plat-dev, acme-plat-staging and acme-plat-prod |
| Guardrails | Organization policies, Resource Manager tags, label constraints and an Identity and Access Management (IAM) deny policy that protects the audit trail |
| Identity | Groups mapped to IAM roles on the organization, the folders and the stage projects, with Privileged Access Manager entitlements for the admin roles. Pipelines sign in from GitHub Actions through Workload Identity Federation, so no service account key exists |
| Network | The network project as the Shared VPC host of hub, prod and nonprod VPC networks, hierarchical firewall policies at the organization, Cloud NAT, private DNS and Identity-Aware Proxy (IAP) TCP forwarding for engineers. Every address range comes from one address plan, network_map.yaml |
| Security | Security Command Center, Artifact Analysis vulnerability scanning, Cloud KMS key rings, the Center for Internet Security (CIS) log-based alerts, and a Cloud Armor rule template the blueprints build their edge policies from |
| Audit | Aggregated organization log sinks into a central log bucket and an archive bucket in the audit project, encrypted with a customer-managed key, with Data Access audit logs on |
| Workload contract | Parameter Manager parameters in each platform project that publish the landing-zone values blueprints read at plan time: the VPC and its subnets, DNS zones and the Artifact Registry path |
| Delivery | Artifact Registry for images and plan, apply and drift-detection workflows |
The home region is us-west1, and regional resource names carry its short slug, usw1. Both are chosen before the first deployment, as are the namespace and the project IDs, which Google Cloud never lets you reuse.
Built to the BuiltForProd Standard
Every edition is measured against the same eight properties: Secure, Reliable, Observable, Scalable, Automated, Recoverable, Compliant and Operable. The BuiltForProd Standard defines each one. The bar is the same on every cloud. What differs between editions is which Google Cloud mechanism meets it.
Delivered as code
The Baseline is Terragrunt over OpenTofu: reusable modules, and one small unit per piece of infrastructure that says which module to use, in which project and region, with which inputs. Every change is proposed as a pull request, planned and reviewed there, and applied on merge, with a required approval before production. Nothing is clicked together in a console. Infrastructure as code explains the approach, and landing zones explains why the project is the unit of isolation.
Set up by us, owned by you
The BuiltForProd team customizes the Baseline to your organization and deploys it. At handover you receive the repositories, the infrastructure code and the documentation, and from then on the foundation is yours to run and change. The Baseline product page describes the deployment options and what a handover includes.
In this overview
- Architecture overview: the projects, the network, identity, guardrails and delivery on one page.
- What you receive: the repository, the documentation, the deployed environment and the handover.
- Service inventory: every Google Cloud service the Baseline configures, and whether it is on by default.
- Versions: the tool, provider and GitHub Actions versions the Baseline pins.
The complete GCP Enterprise Baseline documentation is available to customers who hold it. Read the documentation overview for the concepts behind the Baseline, then sign in from the navigation bar, or contact BuiltForProd to discuss your Google Cloud estate.