Pricing

machine.dev bills per minute in US dollars. You only pay for runtime — provisioning and teardown are free. There are no credits, no commitments, and the only thing you pay for is the seconds your runner is up plus the storage it uses.

Prices below are sourced from the canonical pricing API and represent the best rate across all regions. Spot rates fluctuate; the live pricing page is always authoritative.

How billing works

• Per-minute, USD. Your bill is runtime in minutes × per-minute rate for compute, plus prorated EBS storage charges.
• Pay-as-you-go is the default. No subscription required.
• Subscription plans bundle a discount (see below).
• Spot rates change with AWS market. You’re charged the rate at job start.
• No charge for provisioning. Cold start takes ~1 minute and is free.
• No charge for failed provisioning. If we can’t get you a runner, you pay nothing.
• Spot interruptions are billed up to the moment of interruption, then stop.
• The dashboard shows dollars by default. You can toggle to credit-style accounting in Settings if you prefer.

Free tier

New accounts receive $10 of free compute on signup. At spot rates that’s roughly:

• ~58 hours of T4G GPU time
• ~30 hours of L4 GPU time
• ~265 hours of CPU time (4-vCPU ARM)

Sign up to claim it.

CPU runners

X64 (Intel/AMD)

ARM64 (Graviton)

GPU runners

Each NVIDIA GPU is offered in 3 vCPU/RAM configurations. Pick a higher-vCPU config if your workflow does heavy CPU-side preprocessing.

AWS AI accelerators

EBS storage pricing

Storage is billed separately from compute and prorated to your job’s runtime. All runners use gp3 EBS volumes.

Costs are prorated per minute of runtime. The default 6,000 IOPS and 250 MB/s throughput are included at no additional charge — only IOPS and throughput above those defaults incur extra charges.

Default storage configuration:

• Volume size: 100 GB
• IOPS: 6,000
• Throughput: 250 MB/s

Example: default storage on a 30-minute job

• Storage: 100 GB × $0.08 / 43,200 min × 30 min = $0.006
• IOPS surcharge: none (default)
• Throughput surcharge: none (default)
• Total EBS cost: ~$0.006

Example: 500 GB / 10,000 IOPS / 750 MB/s on a 60-minute job

• Storage: 500 × $0.08 / 43,200 × 60 = $0.056
• IOPS surcharge: (10,000 − 6,000) × $0.005 / 43,200 × 60 = $0.028
• Throughput surcharge: (750 − 250) × $0.04 / 43,200 × 60 = $0.028
• Total EBS cost: ~$0.112

Use the disk_size, disk_iops, disk_throughput labels to customize per job.

Subscription plans

Plans are an optional bonus on top of pay-as-you-go. Each tier gives you more dollar value than you put in. All compute is still billed per-minute in USD — the plan just gives you a balance of bonus dollars to draw down.

Pick a plan in the machine.dev dashboard or contact sales for enterprise pricing.

FAQ

What happened to credits?

machine.dev now bills in US dollars instead of credits. If you had a credit balance before the cutover, it was automatically converted to a dollar balance at the same rate ($0.005 per credit). Your existing balance, monthly subscription, and billing all carry over — there’s nothing you need to do.

Are there volume discounts?

Yes — contact hello@machine.dev for enterprise pricing and volume tiers.

Can I see my spend in the dashboard?

Yes. The machine.dev dashboard shows per-job cost in dollars by default, plus daily and monthly aggregates. You can toggle to a credit-style view in Settings if you prefer.

Do I pay for provisioning time?

No. You only pay for the time your job is actually running. Provisioning and teardown are free.

What happens if a spot instance is interrupted?

You’re billed up to the moment of interruption, then billing stops. Implement checkpointing in your workflow to handle interruptions gracefully — see Cost Optimization.

Are storage charges separate from compute?

Yes. Compute is billed per minute based on the runner type. Storage (EBS) is billed prorated based on volume size, IOPS, and throughput. Defaults are minimal (~$0.006 for a 30-minute job at 100 GB / 6,000 IOPS / 250 MB/s).

Next steps

• Cost Optimization — strategies to lower your bill
• GPU Runners — pick the right GPU
• CPU Runners — pick the right CPU
• FAQ — billing, technical, and troubleshooting questions