Home › Key concepts › Deploy in their cloud
Key concept · Walk (intermediate) · the same on every platform
Deploy in their cloud
The system runs in the customer's account, under their rules, from day one.
What it is
Customers keep data in their own cloud for security and compliance. Deploying there means their identity system, their network rules, their approval process. Infrastructure as code and ports-and-adapters make it repeatable.
Why it matters
A prototype that only runs in your account is not a delivery.
An example
The same agent is deployed into the customer's Azure subscription with their Entra ID groups and private networking.
The common mistake
Discovering their security review in the last week.
Where you meet it on each platform
The idea stays the same; only the product name changes.
| Job | AWS | Azure | Google Cloud | Databricks | Open source |
|---|---|---|---|---|---|
| Infrastructure as codethe whole setup in files you can review and re-create | Terraform or AWS CDK | Bicep or Terraform | Terraform | Declarative Automation Bundles (Asset Bundles) | Docker Compose |
| Identity and secretswho is calling, what they may do, where keys live | IAM + Secrets Manager | Entra ID + Key Vault | IAM + Secret Manager | Unity Catalog grants + secrets | Keycloak + sops |
Related ideas
Where it shows up
Part of the Walk level on these paths: Forward Deployed Engineering (deliver).