Murmur usage is billed in Murmur credits under usage-based pricing. One credit = $0.01. Credits are pre-purchased and burn down as agents consume the components below:

Component	What it charges for	How it’s billed	Rate
CPU Compute	The agent VM’s machine shape	Per VM-second, while the VM is running	Varies by machine type — see rates
NAT IP	The VM’s public IPv4 address	Per VM-second, while the VM is running	$0.0055 / hour
Storage	Boot disk, sleep memory images, and baked images	Boot disk & memory image: per VM-second while those bytes exist. Baked image: hourly.	Varies by disk type — see rates; baked images $0.000077 / GiB-hour
LLM Inference	Tokens served on a Murmur-provided model credential	Per model call	Published per-token rates plus 10% markup
Historical Session Storage	An agent’s retained session transcript	Daily, until the agent is deleted	$0.00022 / decimal MB-month

On a platform placement, the rates above and in the appendix are the final prices Murmur charges: multiply one by your usage and that is the amount billed, with nothing further added at billing time. LLM Inference is the one exception, because its per-model rates are not published here — that section states separately what is added to the provider’s rates. Rates are quoted in USD, so multiply a dollar rate by 100 to get credits: the $0.0055 per hour NAT IP rate is 0.55 credits per hour. Your billing dashboard in Settings → Usage → Billing → Murmur Usage Detail breaks down the cost components for each of your workspaces, owners, and tags, by billing period. See the appendix below for more details.

​

Appendix

​

CPU Compute

The CPU Compute rate is the machine type’s hourly rate. Costs accrue per VM-second while the VM is running, and stop when the VM stops or sleeps. Each rate below is the CPU Compute rate for one running VM-hour, in every region the built-in prices — us-central1, us-east1, and us-west1 on GCP, us-east-1 and us-west-2 on AWS. A built-in carries the same rate in each of them. NAT IP and Storage are separate components on top.

​

GCP machine types

Catalog name	Machine type	Billed rate/hour	vCPUs	Memory	Sleep
murmur-e2-medium	e2-medium	$0.03685	2 shared-core	4 GiB	Warm
murmur-n2-standard-2	n2-standard-2	$0.10681	2	8 GiB	Warm
murmur-n2-standard-4	n2-standard-4	$0.21362	4	16 GiB	Warm
murmur-n2-standard-8	n2-standard-8	$0.42735	8	32 GiB	Warm
murmur-n2-standard-16	n2-standard-16	$0.85459	16	64 GiB	Warm
murmur-n2-standard-32	n2-standard-32	$1.70929	32	128 GiB	Warm
murmur-n2-standard-64	n2-standard-64	$3.41858	64	256 GiB	Cold
murmur-n2d-standard-2	n2d-standard-2	$0.09295	2	8 GiB	Warm
murmur-n2d-standard-4	n2d-standard-4	$0.18590	4	16 GiB	Warm
murmur-n2d-standard-8	n2d-standard-8	$0.37180	8	32 GiB	Warm
murmur-n2d-standard-16	n2d-standard-16	$0.74349	16	64 GiB	Warm
murmur-n2d-standard-32	n2d-standard-32	$1.48709	32	128 GiB	Warm
murmur-n2d-standard-48	n2d-standard-48	$2.23058	48	192 GiB	Warm
murmur-n2d-standard-64	n2d-standard-64	$2.97407	64	256 GiB	Cold
murmur-t2d-standard-2	t2d-standard-2	$0.09295	2	8 GiB	Warm
murmur-t2d-standard-4	t2d-standard-4	$0.18590	4	16 GiB	Warm
murmur-t2d-standard-8	t2d-standard-8	$0.37180	8	32 GiB	Warm
murmur-t2d-standard-16	t2d-standard-16	$0.74349	16	64 GiB	Warm
murmur-t2d-standard-32	t2d-standard-32	$1.48709	32	128 GiB	Warm
murmur-t2d-standard-48	t2d-standard-48	$2.23058	48	192 GiB	Warm
murmur-t2d-standard-60	t2d-standard-60	$2.78828	60	240 GiB	Cold
murmur-c3-standard-44	c3-standard-44	$2.43947	44	176 GiB	Warm

​

AWS machine types

Catalog name	Machine type	Billed rate/hour	vCPUs	Memory	Sleep
murmur-m5-large	m5.large	$0.10560	2	8 GiB	Warm
murmur-m5-xlarge	m5.xlarge	$0.21120	4	16 GiB	Warm
murmur-m5-2xlarge	m5.2xlarge	$0.42240	8	32 GiB	Warm
murmur-m5-4xlarge	m5.4xlarge	$0.84480	16	64 GiB	Warm
murmur-m5-8xlarge	m5.8xlarge	$1.68960	32	128 GiB	Warm
murmur-m5-16xlarge	m5.16xlarge	$3.37920	64	256 GiB	Cold
murmur-c5-large	c5.large	$0.09350	2	4 GiB	Warm
murmur-c5-9xlarge	c5.9xlarge	$1.68300	36	72 GiB	Warm

​

NAT IP

The VM’s public IPv4 address is billed at $0.0055 per hour, accrued per VM-second while the VM is running, and stops when the VM stops or sleeps.

​

Storage

Storage costs cover three separate parts, combined into one Storage line item. Boot disk and sleep memory image are priced from the disk type; baked images have their own rate.

Component	Charged while	Rate
Boot disk	The VM’s disk exists, whether the VM runs or sleeps	Disk type rate × provisioned GiB
Sleep memory image	A machine type that preserves memory on sleep holds one	Disk type rate × machine RAM
Baked image	You keep a custom VM image	Per stored GiB-hour

​

Boot disk

The boot disk is the VM’s root filesystem. It accrues per VM-second from VM creation until the disk is deleted, whether the VM is running or sleeping.

​

Sleep memory image

The sleep memory image holds the machine’s RAM so a warm VM can resume with memory intact. It is sized to the machine’s RAM, and behavior differs by cloud:

• AWS — a memory-image volume of the selected disk type exists for the VM’s full lifetime, whether the VM is running or sleeping.
• GCP — a memory snapshot exists only while the VM is suspended.

Machine types marked Cold preserve no memory and incur no sleep-memory charge.

​

Baked images

Baked images are billed at $0.000077 per stored GiB-hour, based on the image’s stored size (the compressed archive or EBS snapshot, not the nominal size of the source disk), so one GiB kept for a 730-hour month costs $0.05621. Deleting an unused image stops the charge.

​

Disk type rates

Disk type rates price the boot disk and sleep memory image. The disk-type reference lists the built-in entries. These rates are quoted per GiB-month and metered by the second, prorated by 730 hours per month: one GiB of murmur-pd-balanced held for six hours costs $0.1100 / 730 × 6, or $0.0009.

Catalog name	Disk type	Priced regions	Billed rate
murmur-pd-standard	GCP pd-standard	us-central1, us-east1, us-west1	$0.0440 per GiB-month
murmur-pd-balanced	GCP pd-balanced	us-central1, us-east1, us-west1	$0.1100 per GiB-month
murmur-pd-ssd	GCP pd-ssd	us-central1, us-east1, us-west1	$0.1870 per GiB-month
murmur-gp3	AWS gp3	us-east-1, us-west-2	$0.0880 per GiB-month

​

Machine and disk types you define

When an admin sets up a customer-managed placement in a region the built-ins do not price, they add their own machine-type and disk-type entries. VMs allocated from those entries are priced from the rates those entries carry for the VM’s region:

• cost_per_hour on the machine type
• cost_per_gib_month on the disk type
• performance_cost_per_month on the disk type — a flat per-disk charge that does not scale with size, and applies to the boot disk only

Price every region your placements use in both entries. Enter the rate your cloud provider charges you. Because the placement is customer-managed, Murmur bills 10% of the total these rates produce, and your cloud provider bills you for the VM itself.

​

LLM Inference

An agent runs on a Murmur-provided model credential if it has no credentials of its own. These LLM Inference calls are billed on four token counts, valued at the published per-token rates for the model that served the call:

• uncached input tokens
• cache-read tokens
• cache-write tokens
• output tokens

Those per-token rates are the one place this page does not quote a final price. The charge is that token subtotal plus a 10% markup. Per-model rates are not listed on this page — the rate page carries a figure for each of the four counts above, model by model.

​

Historical Session Storage

Each agent execution with a persisted session keeps one JSONL transcript in Murmur-managed session storage:

• The coding backend’s conversation state, used to restore or resurrect the execution.
• Downloadable from the agent view.
• Separate from the dashboard’s timeline and event history.
• Survives the execution finishing, sleeping, being killed, or losing its VM.

Stored bytes are metered once a day at $0.00022 per decimal MB-month — approximately $0.2362 per GiB-month — prorated for the fraction of your billing period the transcript existed. To stop future accrual, permanently purge the stopped agent with murmur delete — this covers every execution and descendant agent, and every version of their transcripts. Preview the scope with murmur delete --dry-run <slug>, and murmur kill first if anything in the subtree is still running.