Shared responsibility model
Three parties are responsible for a BuiltForProd deployment. Your cloud provider (AWS, Microsoft or Google) runs the cloud. BuiltForProd customizes, deploys and hands over the platform, and operates it only if you buy Managed. Your organization owns the cloud organization, the identities, the repositories and the operation from the moment of handover. The line does not move unless you move it with a Managed engagement.
The three parties
Responsibility by area
| Area | Cloud provider | BuiltForProd (delivery) | Your organization |
|---|---|---|---|
| The cloud itself | Regions, availability zones, hardware, the managed services (Kubernetes control planes, databases, key services and the rest) | Chooses the services and how they are configured | Chooses home region, address plan and which paid switches are on |
| The organization structure | The hierarchy, its policies and quotas as a service | Creates the structure as code: on AWS the Organization, OUs, 14 member accounts, SCPs and tag policy; on Azure the management groups, the 15 subscriptions or their adoption, and Azure Policy; on GCP the folders, 14 projects beside the seed project, and the organization policies | Owns the top of the hierarchy. On AWS: the management account and its root credentials, the root mailbox every account's plus-addressed email lands in, the account quota increase. On Azure: the Microsoft Entra tenant, a billing scope or 15 pre-created subscriptions, the Entra ID licenses. On GCP: the organization, the billing account and its project quota, the Cloud Identity or Workspace domain |
| Identity | The identity service (IAM Identity Center, Microsoft Entra ID, Cloud Identity) | Maps groups to access as code: permission sets on AWS, Azure RBAC role assignments on Azure, IAM bindings on GCP | Creates the groups (ACME_* in Identity Center or Entra ID, acme-*@company.com Google groups) or lets the code create them, adds and removes people, enforces MFA, reviews access regularly |
| Repositories | GitHub is not your cloud provider | Forks and customizes the repositories, sets every TODO: value, hands them over in your GitHub organization | Owns the GitHub organization, teams, Environments and reviewers; every change after handover |
| Pipelines | Token exchange for federated identities | Creates the keyless trust and the workflows: the OIDC provider and the per-stage CI roles on AWS, a federated managed identity per repository and stage on Azure, the Workload Identity Federation pool and the per-stage CI service accounts on GCP | Holds the trust: your GitHub organization is the only identity the pipeline identities accept; you approve prod applies |
| Deployment | Applies changes | Executes the initial deployment of the Baseline and any purchased blueprints, in every deployment option | Every apply after handover runs from your pipelines under your approvals |
| Security services | Runs the detection services | Wires them in and sets the defaults: GuardDuty, Security Hub and AWS Config delegated to the security account; Microsoft Defender for Cloud plans and Azure Policy initiatives; Security Command Center and the log-based detections | Triages findings, decides which paid services and frameworks to switch on, receives the alerts |
| Secrets | The key and secret stores (KMS and Parameter Store; Key Vault; Cloud KMS and Secret Manager) | Creates the per-stage keys and the sync workflow | Owns every secret value; edits them through pull requests to the secrets repository |
| Data | Storage and encryption at rest | Nothing: BuiltForProd never holds customer data | All application and customer data, backups and their restore tests |
| Documentation | The provider's documentation | The workbooks and this site | Keeping your fork's documentation in step with your changes |
The prerequisites page lists what your organization provides before the deployment starts.
After handover
At handover the BuiltForProd team has deployed the environment and handed over the customized repositories and the documentation. From then on:
- Human access exists only through your groups, and only your administrators grant or revoke membership. On AWS that is IAM Identity Center; on Azure, Microsoft Entra groups mapped to Azure RBAC, with an Azure Policy that denies role assignments to individual users; on GCP, Google groups bound to IAM roles.
- Pipeline access exists only through federation from your GitHub organization: GitHub OIDC on AWS, federated managed identities on Azure, Workload Identity Federation on GCP. No key was ever created for a person or a pipeline.
- BuiltForProd holds no credentials for your cloud. The privacy and data handling page states the same from the data side.
Your team operates the platform with the roles, code ownership and runbooks described on the Operable page: Platform Leads own the landing zone and approve production changes, DevOps Leads own the pipelines and command incidents, application and data teams own their blueprint repositories, and security auditors hold read-only access (on AWS with an explicit deny on data).
Under a Managed engagement
BuiltForProd Managed moves part of the operating responsibility back to BuiltForProd, by option:
| Option | What BuiltForProd takes on |
|---|---|
| On-Demand | Consultation and support when you ask, by the hour; your team keeps operating |
| Support SLA | The same, under a response commitment defined in your agreement |
| Team Augmentation | Dedicated engineers embedded in your team, part-time or full-time, working inside your repositories, your reviews and your approvals |
Managed engineers work as members of your organization: they sign in through the groups you grant, they change the platform through pull requests under your CODEOWNERS rules, and they apply through your pipelines. Access ends when you remove them from the group. What does not move under any option: ownership of the cloud organization, the root mailbox or tenant, the repositories, the data, and the final approval on production changes.
What your cloud provider is responsible for
Your cloud provider is responsible for the security of the cloud: the physical infrastructure, the regions and zones, and the managed services the platform builds on. The platform configures those services (encryption, logging, network boundaries, access) and that configuration is what this documentation describes. The Baseline product page lists what BuiltForProd delivers; the security posture summary lists the controls that configuration puts in place.