Pricing
Runner rates, add-on pricing, and how Monk CI compute is billed.
Monk CI is billed pay-as-you-go: per compute minute for runners, plus usage-based add-ons like Docker layer caching. There are no monthly minimums.
Pay-as-you-go billing - $0.004 / min
New organizations start on a Trial with included free minutes; billing begins only after the free allowance is exhausted. To track your own consumption against these rates, see the Usage & Billing workspace.
Runner Pricing
Compute minutes are billed per runner configuration. Larger runners consume your allowance and billable minutes at a higher multiplier than smaller ones.
| Runner | vCPU | Multiplier | Effective Rate | Typical Workloads |
|---|---|---|---|---|
monkci-ubuntu-24.04-2 | 2 | 1× | $0.004 / min | Linting, unit tests, small builds |
monkci-ubuntu-24.04-4 | 4 | 2× | $0.008 / min | Integration tests, moderate builds |
monkci-ubuntu-24.04-8 | 8 | 4× | $0.016 / min | End-to-end tests, Docker image builds |
monkci-ubuntu-24.04-16 | 16 | 8× | $0.032 / min | Heavy compilation, monorepo builds |
monkci-ubuntu-24.04-32 | 32 | 16× | $0.064 / min | Your one-size-fits-all powerhouse |
monkci-ubuntu-latest | 32 | 16× | $0.064 / min | Always maps to the highest-performance tier |
Add-On Pricing
Add-ons are billed separately from runner minutes, based on the resources they consume.
Docker Layer Caching - $0.50 / GB-month
Persistent, per-repository Docker layer cache co-located with your runners on local NVMe. Billed on the storage your cache occupies, prorated monthly. See the Docker Builds guide for setup.
Add-on charges appear as Billable usage in the Usage & Billing workspace alongside your runner minutes.
Common Use Cases
Estimating the cost of a workflow
Multiply the expected runtime by the effective rate of the runner it uses, then add any add-ons (e.g. Docker cache storage) it depends on.
Choosing a runner size
Start with the smallest runner that fits your workload's typical use case above, and check the Usage & Billing workspace after a few runs to see if a larger tier would meaningfully cut runtime.
Budgeting for Docker caching
Cache size scales with your image's dependency layers, not your repo size. A typical service image lands well under a few GB, putting monthly cache cost at a few dollars.