Pricing
Free during the beta, and here is why
Outcap has no paying customer to date. Publishing a four-tier grid in that state would mean guessing what the product is worth on your traffic, when the whole point of it is to measure. So: two lines, and what will be charged later written down now.
No card, no commitment, no trial that quietly turns into a subscription. If the beta ends, you get thirty days' notice, and your metadata exports to CSV.
| When | Price | What it opens | Status |
|---|---|---|---|
| Beta, today | $0 | The whole product, on your own provider keys: hard budgets, margin per end customer, routing, learned output cap, cache, alerts, OpenTelemetry export, input guardrails. | live |
| After the beta | monthly subscription | The same product. A flat price and an included request volume, announced thirty days before the first invoice. Accounts opened during the beta keep a free month. | planned |
Two lines, because a four-tier grid with two tiers nobody ever bought tells the reader nothing.
The contract
What will be charged, and what never will
A pricing model reads as a commitment about how a vendor makes a living. Here is ours, before you have to guess it.
Charged, later
A monthly subscription
A flat price and an included request volume, published on this page. You will know what you pay before routing the first request.
Volume, not value
Above the included volume, a higher tier. What grows with your usage is our CPU and our database: that is what gets charged, and nothing else.
Nothing at all if you host it
The compose file and the install guide are public. An Outcap running on your machines owes us nothing and sends us nothing.
Never charged
A percentage of the savings
That number is our own estimate, produced by our code from our own percentiles. Being paid on it would mean being paid to stay optimistic, and you would have no way to audit the invoice.
A percentage of your LLM bill
It crosses our machines, it is not ours. Your keys stay with you, the spend goes straight to the provider, and we have no business being interested in how large it gets.
A seat per person
A bill that runs away gets looked at by several people. Charging per pair of eyes would push your team out of the dashboard, which is exactly where the decisions happen.
The reason
Why it is free right now
The product measures money leaving. Selling it before having measured anything on real traffic would contradict what it claims to do. A price set today would be one more estimate, and this page already rules several of those out.
So what the beta earns us is not money: it is an account plugged in observation mode, changing no request, and a message when a number on the dashboard does not match what you see at your provider. That is the only way to write an honest price afterwards.
What trying costs you: the time to change one base URL, and the time to change it back.
Run it yourself
A Docker compose file and an install guide. The dashboard deliberately has no database access at all: it only reads the proxy's admin API. One warning is written inside the compose file itself, and it applies to our own deployment too.
Read the documentationNever go to two instances until the counters are shared: they live in memory in a single process, and real spend could reach the limit multiplied by the number of instances.
Plug it in observation mode, decide afterwards
The default mode changes no request. You see what Outcap would have done on your traffic, then you turn on what you want, route by route.