Skip to main content
A placement determines which cloud account and region your agents run in.

​
Platform and customer placements

Every tenant starts with platform placements — preconfigured by Murmur, available immediately, no setup required. Your workspace references one by name and agents run on Murmur-managed infrastructure. Customer placements are optional. You create one when you need agents running in your own GCP project or AWS account — for VPC-internal access to databases and APIs, data residency requirements, or compliance policies that require compute in your cloud. The customer placements guide walks through the full setup. Both kinds work the same way once configured. The difference is who owns the cloud account the VMs run in.

​
How placements connect to other resources

A workspace references one placement and one environment. The placement controls where — cloud account, region, network. The environment controls what size — machine type and disk. These are independent: you can reuse the same environment across multiple placements of the same cloud provider. Images are bound to placements. A VM image baked in one GCP project or AWS account is not visible from another. When you create a customer placement, you re-bake your recipes against it so the resulting images exist in your cloud account.