---
title: "Pricing, per second, quoted and capped before the run"
description: "Promigence usage rates by environment tier, plans, and an honest comparison."
url: "https://www.promigence.ai/pricing"
site: "Promigence"
---

# Promigence pricing

Metered per second at $0.0504 per vCPU-hour plus $0.0162 per GiB-hour, the market's standard list rate. Paused time is not billed, and the exact maximum cost of a run is quoted before it starts.

| Tier | Environment | Per hour | Per second | Typical workload |
|---|---|---|---|---|
| Small | 2 vCPU · 4 GiB | $0.17 | $0.000046 | A SWE-bench-class episode: clone, patch, run the failing test. Ten minutes costs about $0.03. |
| Medium | 4 vCPU · 16 GiB | $0.46 | $0.000128 | Monorepo typechecks and mid-size builds. |
| Large | 8 vCPU · 32 GiB | $0.92 | $0.000256 | Heavy builds and memory-hungry test suites. |

## Plans
### Free, $0 pay as you go
Start free, then pay only for the seconds you run.
- Usage: $50 of free credit included; then per second at list, only what you use
- $50 of free credit to start
- 20 sandboxes at once, sessions up to an hour
- Validity report on every run
- Quote and hard spend cap on every run

### Pro, $50 per month
For teams running agents, evals and CI every day.
- Usage: More usage than you pay for included; then per second past it
- Everything in Free, plus $50 of free credit
- More compute each month than the plan costs
- Up to 100 sandboxes at once
- Verified snapshot builds, failed builds free
- Harness adapters: Inspect, Harbor, SWE-bench
- Email support

### Max, $500 per month
For large eval fleets, RL and continuous agentic CI.
- Usage: About 10× the usage of Pro included; then below list, by commitment
- Everything in Pro, plus $50 of free credit
- About 10× the usage of Pro
- Up to 1,000 sandboxes at once
- Capacity held warm for your snapshots
- Shared Slack channel

### Custom, Custom volume pricing, set on one call
For vendors and labs running millions of episodes.
- Usage: Set on the call included; then volume rates
- Everything in Max, plus $50 of free credit
- Committed capacity contracts and reserved capacity
- Running it in your own cloud account: talk to us
- Custom environment shapes
- Direct line to engineering

## Other charges
- **Verified snapshot build**: $1 per build. A build that fails its own verify command is not charged.
- **Snapshot storage**: Included. Included in every plan.
- **Paused time**: Not billed. A paused environment accrues nothing, and nothing accrues before one is handed to you.
- **Egress**: Included. Registries and git hosts are not metered separately. The trial caps data out at 20 GB a month.

## A 10-minute episode, compared
| Option | Cost | What that buys |
|---|---|---|
| Self-hosted Docker, raw cloud compute | ~$0.014 | Before engineering time, image maintenance and burst orchestration, with unknown validity. |
| Typical managed sandbox, list | ~$0.03 | The same rate we charge. The difference is the 60 to 100 s of cold setup you pay for on every episode. |
| Premium managed sandbox, list | ~$0.06 | Roughly three times the typical per-vCPU rate. |
| Promigence, list | ~$0.03 | Warm verified fork, validity report, reproducible by hash, quoted and capped before the run. |

## Principles
### The same rate as the market, per second
$0.0504 per vCPU-hour and $0.0162 per GiB-hour, the market's standard list rate. A price nobody can compare against is worth very little, so we did not invent a new unit.

### You see the ceiling before the run
`promigence run quote` returns the exact maximum before a single environment starts. `--cap` refuses a run that would exceed it rather than stopping halfway and charging for the half.

### A faster run is a cheaper run
The meter runs from the moment an environment is handed to you until it ends. Starting warm instead of cold cuts 60 to 100 seconds off every episode, and that comes straight off the bill.

### Our failures are on us
A build that fails its own verify command is not charged. Neither is an episode the environment broke, when our side can show the failure was ours. We can only refuse to bill for that category because we measure it.