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 that Murmur preconfigures and makes available without setup. Your workspace references one by name, and agents run on Murmur-managed infrastructure. Customer placements are optional. Create one when agents need to run in your own GCP project or AWS account for VPC-internal access, data residency, or compliance requirements. The customer placements guide covers the 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 the cloud account, region, and network. The environment controls the machine type and disk. You can reuse the same environment across multiple placements for 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.