Environments and placements are the two catalog resources that control the compute substrate for agent VMs. An environment defines what a VM looks like. A placement defines where it runs.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.
Environments
An environment (environment kind) specifies the VM configuration:
| Field | Description | Example |
|---|---|---|
substrate | Cloud provider type | GCP, AWS |
machine_type_ref | Reference to a machine-type resource | n2-standard-8 |
disk_size_gb | Root disk size (0 = image default) | 100 |
Placements
A placement (placement kind) specifies where VMs are provisioned:
| Field | Description |
|---|---|
platform | true = managed by Murmur (immutable to tenants), false = customer-managed |
target | Cloud-specific config: GCP (project, zones, subnet) or AWS (account, region, VPC, subnets) |
substrate | GCP or AWS |
service_account | Cloud identity for VMs |
Image families
Agent VMs use a two-layer image model:- Platform base — Debian 12, Git, Node.js, Claude Code, gh CLI (maintained by Murmur)
- Your toolchain — Go, Python, Docker, CUDA, internal SDKs (customized via recipes)
murmur bake. See the Custom VM Images guide.
Machine types
Machine types (machine-type kind) are pre-defined by the platform. List available ones: