Pricing

Stated before launch, on purpose. Two principles decide every line below — and they are the same principles that decide the architecture.

The trust boundary is the billing boundary.

Everything that touches your content — proxy, ledger, detectors, guard, routing mechanism, dashboard — is Apache-2.0 and runs on your machine, free forever. Money only ever attaches to what crosses the machine boundary: sync, team visibility, org policy, refreshed intelligence.

Open mechanism, commercial intelligence.

The engine is open; the continuously re-verified knowledge that feeds it is the paid product. Policy packs are signed data — never code — verified against evals within days of every model release and repricing. A fork gets a snapshot; subscribers get the refresh rate. No closed code in the data path, ever.

Free / Open source

$0 forever · Apache-2.0

Repo public in August

The full local loop. Not a trial, not crippleware — CCR-parity routing or better, standalone.

✓ Wire-truth proxy + content-free evidence ledger
✓ CLI metrics, statusline, local dashboard, desktop app
✓ Cache economics: hit rates, cold restarts, bust forensics
✓ Deterministic detectors & recommendations with receipts
✓ Guard: budget caps, runaway-session detector, cache-anomaly & model-mismatch alarms
✓ Routing: buckets, rules, cache-safe stickiness
✓ Weekly savings & waste report, exactness-labeled

This list is a commitment, not a teaser. Nothing on it ever moves behind a paywall.

Pro — routing intelligence

~$12 /month · planned

After launch, once verification can honestly back it

The subscription is a refresh rate: every model release reprices your workflow; Pro re-verifies your routes within days.

✓ Live, signed, eval-verified policy packs
✓ Counterfactual savings attribution: “$0.84 vs $2.10 baseline”, exportable
✓ What-if replay: your last 30 days under any pack or price sheet
✓ Informed guard: learned baselines, provider-behavior advisories, phone/Slack alerts

You are never unsafe for being free — you are better-informed and reachable for paying.

Team

$29 /seat/month · every seat includes Pro

Founding design partners: Q4 2026

For the person who got the cost email from finance. Attribution, budgets, and policy — across people.

✓ Shared ledger & team dashboard
✓ Per-dev, per-repo, per-task attribution
✓ Budgets & alerts across people
✓ Policy distribution: routing and guard defaults pushed to every dev
✓ Weekly team savings digest

Founding partners: $299/mo flat, up to 15 seats, 3–5 slots. Guarantee: verified savings below fees in a quarter → we credit the difference.

Enterprise

Custom self-hosted control plane

Built with design partners, never speculatively

Governance for regulated and gateway environments.

✓ Self-host control plane
✓ SSO/SAML/SCIM, RBAC, audit exports
✓ Enterprise gateway integrations & cost reconciliation
✓ Support & SLA

The math we sell against

A 10-dev team averaging $300/dev/mo spends $3,000/mo on models. The evidence-backed reduction band for cache-aware metering plus verified routing is 20–40% (Coinbase reported −50% at company scale; Devin Fusion −35–41%; cache reads cost 10% of input price). Take the conservative edge: 20% → $600/mo saved. Legroom Team costs $290. Worst-case ROI ≈ 2×, typical 3–5× — and the savings number is computed by your own ledger, exactness-labeled, not by our marketing team.

the math, worst case [ 10-dev team ]

model spend       10 × $300      $3,000 /mo   exact
reduction band    cache + routing   20–40%    evidence
taken here        conservative edge   −20%    on purpose
saved                            −$600 /mo    estimated
legroom team      flat           +$290 /mo    exact

worst-case roi    ≈ 2×           typical 3–5×

What we will never do

✕ No token markup or resale — zero margin on inference, we sit on your side of the meter
✕ No %-of-savings billing — flat, predictable, no incentive to inflate baselines
✕ No subscription-limit arbitrage or OAuth tricks — ToS-clean by design
✕ No telemetry by default, ever
✕ No closed code in the data path — paid intelligence is signed data, executed by the open engine
✕ No silent feature removals from the open core — rug-pulls are the one unforgivable move

Questions about the split? The FAQ on the home page covers the free/paid line; the security page covers what crosses the machine boundary. Security