By default, agents run on platform-managed infrastructure. If you need agents in your own cloud — for compliance, data residency, or VPC-internal access — you can create a customer placement.Documentation Index
Fetch the complete documentation index at: https://docs.murmur.dev/llms.txt
Use this file to discover all available pages before exploring further.
This is an advanced, optional feature. Most teams don’t need it. Platform-managed placements work out of the box with no cloud setup.
When to use customer placements
- Compliance: Your security team requires compute in your own account
- Data residency: Regulatory requirements for specific regions
- VPC-internal access: Agents need to reach internal services (databases, APIs) inside your VPC
- Custom networking: Specific firewall rules, proxy configuration, or VPN requirements
How it works
- You run a Terraform module in your cloud account that creates a trust relationship
- Murmur authenticates to your cloud via OIDC token exchange (Workload Identity Federation)
- The trust is scoped to exactly your tenant — no other Murmur tenant can use your resources
- You create a placement catalog resource pointing to your infrastructure
- Your workspace references this placement
GCP setup
1. Apply the Terraform module
In your GCP project:- A Workload Identity Federation pool with OIDC provider
- A service account for Murmur VMs
- IAM bindings scoped to your project
- Firewall rules for SSH via IAP
2. Create the placement
3. Update your workspace
AWS setup
1. Apply the Terraform module
In your AWS account:- An OIDC provider with
StringEqualstrust policy (scoped to your tenant) - An IAM role for Murmur VM operations
- Security group for agent VMs
2. Create the placement
Cryptographic isolation
The key security property: your OIDC trust policy usesStringEquals on the sub claim, scoped to exactly your tenant ID. This means:
- Only Murmur can assume your IAM role (OIDC issuer validation)
- Only your tenant’s agents can use your placement (sub claim matching)
- No other Murmur tenant can ever access your cloud resources
Platform vs customer placements
| Aspect | Platform placement | Customer placement |
|---|---|---|
| Who manages | Murmur | You |
platform field | true | false |
| Cloud account | Murmur’s | Yours |
| Setup required | None | Terraform + placement resource |
| Networking | Platform-managed | You configure VPC/subnets |
| IAM isolation | Multi-tenant (platform-level) | Single-tenant (your IAM policy) |