Product Open Source Pricing Docs Blog
Read the docs Request access
BYO keys · per-run metering

Priced per run, not per token.

Keep your provider accounts and pay your providers directly for inference. Unhardcoded charges for the managed host: routing, traces, failover, history, uptime, and provider modules. A flow counts as one billable run up to 5 nodes.

your provider accounts stay yours no token markup a flow = one billable run up to 5 nodes every run traced
unhardcoded · per-run meter req_8f41
Baseline your current model, same floor $0.063/run
On unhardcoded cheapest model that passes $0.018/run
savings measured per run  ·  cheapest that meets the rules ↓71%
Illustrative. Real per-run figures appear in your dashboard from day one, against your own baseline.
$$Plans

One line item: runs.

Start free and keep your own provider keys. You pay providers directly for inference. You pay Unhardcoded to run and maintain the host you would otherwise build yourself. A flow counts as one billable run up to 5 nodes.

Monthly Annual Save 2 months

WHAT COUNTS AS A RUN?

One chat-completion request is one billable run. One flow is one billable run up to 5 nodes. Larger flows are available on Scale and Enterprise.

Free
For trying a policy on real traffic.
$0/mo
$0.00 / run
10K runs / month
  • 1 policy, BYO keys
  • Full replayable traces
  • 7-day trace history
  • Community support
Request free access
Scale
For teams with high-volume AI traffic.
$199/mobilled annually
then $0.12 / 1K runs
1.5M runs / month included
  • Everything in Pro
  • Roles, SSO & audit log
  • Shared policy library
  • 1-year trace history
  • Priority support
Request Scale access
Enterprise
For compliance, scale, and deployment control.
Custom
volume run rate
Unlimited runs
  • Audit-ready trace export
  • Custom trace retention
  • Self-hosted open-source router
  • Dedicated routing & support
  • Named solutions engineer
Talk to us

All figures illustrative · priced per run, not per token · a flow = one billable run up to 5 nodes · keep your provider accounts

Why per run

Why per run, not per token.

There are three things in the bill. None of them is inference resold to you at a markup.

No token margin your provider accounts stay yours

You bring your provider keys and pay providers directly at their prices. Unhardcoded never resells tokens or adds a spread between you and the model.

Predictable and attributable per-run cost

One run is one metered routing event: policy execution, trace, fallback path, and history record. Finance can attribute cost to a decision, and engineering can replay why a model was chosen.

You pay for the managed host maintained for you

The fee covers what you would otherwise build and operate yourself: provider modules, live catalog data, policy validation, traces, history, failover, uptime, and support.

See how this compares to config-based gateways and token-resale proxies. Read the comparison →

=Compare every run to your baseline

Your current model is the baseline.

Each routed run shows what it cost, what your baseline model would have cost, and the difference. The calculator adds that up across your traffic.

Same requirements. Lower spend.

Most production traffic does not need your most expensive model. It needs a model that passes your floor. Unhardcoded optimizes cost inside that floor, never around it.

live run: $0.018/run · ↓71% vs your baseline
Bill today
$40,000
On unhardcoded
$18,000
$22,000

kept per month — $264,000 a year

Illustrative. Real figures appear in your dashboard from day one, against your own baseline.

FAQbefore you wire it in

Pricing, answered plainly.

Are you reselling tokens?
No. You bring your provider accounts and pay providers directly for inference. Unhardcoded charges only for the managed routing host.
Does a flow count as multiple runs?
A flow counts as one billable run up to 5 nodes. Larger flow limits are available on Scale and Enterprise.
What if I exceed my plan?
You move to the overage rate for your plan. Pro overage is $0.20 per 1K runs. Scale overage is $0.12 per 1K runs.
Can I self-host instead?
Yes. Self-hosting the open source layer has no per-run fee, but you operate everything yourself: provider modules and their API changes, live catalog and pricing upkeep, key management, failover, uptime, and trace storage. Cloud runs all of that for you for the per-run price.
Why pay if the core is open source?
The open core gives you the policy language and interpreter. The hosted product gives you the maintained host: provider modules, key management, OAuth, live catalog data, traces, history, failover, uptime, and support.

One host. One line item.

Start free, keep your provider keys, and pay per run for the managed host you would otherwise build yourself. Every routing decision is traced and replayable.

No credit cardKeep your provider accountsPriced per run, not per token