Pricing
Seats are free on every plan. You pay for how far back you can see, and for how much you build. Both are numbers you already know.
Free
$0
- 14 days of full build traces
- 1 year of trends and cache history
- 1,000 builds a month, up to 50 a day
- Unlimited members
Team
$5per 1,000 builds
- 1 year of full build traces
- 3 years of trends and cache history
- $5 per 1,000, less as you grow
- No base fee and no minimum
- Unlimited members
Enterprise
Talk to us
- Run in your own cloud, managed by us
- Retention set by your policy
- Build volume by agreement
- SSO, audit log, an SLA
- Annual
What it would cost you
| Up to 100,000 | $5.00 per 1,000 |
|---|---|
| 100,000 to 400,000 | $2.50 per 1,000 |
| 400,000 to 1,000,000 | $1.25 per 1,000 |
| Above 1,000,000 | talk to us |
Two kinds of history
A trace is one build in full detail — every instruction, every timing. A trend is their shape over time: how long builds take, what the cache is doing. Trends are kept longer, so you can still date a regression to the week it landed after the build itself has gone.
What counts as a build
One run of kaniko, however many instructions it has. A Dockerfile with sixty lines costs the same as one with six, because the length of your Dockerfile is not something you should be billed on.
How the rates add up
Each band charges only the builds that fall inside it, the way a tax bracket works — not every build at the rate of the band you reached. One extra build costs one extra build.
Open source
Tell us about your open-source project and we'll set you up with Team retention at no cost, plus a discount on builds.
Where your data sits
In the EU, in Frankfurt. On Enterprise it sits wherever your account does, and we operate it there without holding a copy.
Paying
Prices are in US dollars. Cards in most currencies work, and annual plans can go on an invoice.
Leaving
Export every build you have sent us, as the OpenTelemetry traces they arrived as. No format of ours to get stuck in.