Thirty days to find out what you're overpaying.
Roundhouse is a flat monthly subscription, banded by the AI spend it manages for you. No per-request fees, no per-token markup, no percentage of your savings. Your token bills stay exactly what they are — paid by you, to your providers, on your own accounts, at your own rates. The subscription pays for the control plane. Start with the whole thing for 30 days: if the savings don't clear the fee, you'll know before you pay it.
Plans and prices
| Plan | Spend under management | Price | Get started |
|---|---|---|---|
| 30-day trial | the whole product, on your own accounts | $0 | Start the trial |
| route | up to $75,000 / mo | $1,500 / mo | Start the trial |
| scale | up to $300,000 / mo | $4,500 / mo | Start the trial |
| enterprise | up to $1,000,000 / mo | $9,000 / mo | Talk to us |
| above $1M | — | negotiated | Talk to us |
In plain words
The trial — 30 days, $0
The whole product on your own accounts: routing on, budgets enforced, every job metered — cloud calls at the prices on your bill, local runs at the cloud price they displaced.
You end the month with a number computed on your own traffic, not our claim about someone else's. If it doesn't clear the fee, don't subscribe. We would rather you found that out in 30 days than in a procurement cycle.
route — $1,500/mo
The router, on. Every job placed on the cheapest executor that meets its deadline — your machines at $0 first, your cloud accounts only when they must. Budget caps enforced by policy. Every decision recorded and explained.
scale and enterprise
The same software. The band is the width of the spend it manages, not a feature gate — a bigger book of spend means more riding on every routing decision, and the fee scales down as a share of it (2% of ceiling at route, 0.9% at enterprise). enterprise is also where procurement reality lives: security review, invoicing, and the self-hosted option below.
"Spend under management," for someone who has never heard the term
Add up, over a month, every job Roundhouse handled: cloud-executed jobs at the actual provider cost on your own bill, plus jobs that ran on your own hardware at the published list price of the cloud model that would otherwise have run them. That total is your spend under management — the money the router is responsible for.
Note the second half, because it's the honest part: work we route onto your machines counts at the cloud price it displaced, not the $0 it cost you. Any other definition would mean that the better the router does its job, the smaller our meter reads — and you'd be right not to trust a meter built that way.
The number is computed from the same per-job metering rows you can read yourself, at published prices you can check against the provider's own pricing page. Your dashboard shows month-to-date spend under management and the headroom to your band's ceiling at all times — a band change is never a surprise.
The three that exist
Self-hosted / air-gapped: +25%
You run the control plane on your own infrastructure; we support software we can't see or reach. The premium is the honest cost of that, not a punishment for wanting it.
Annual prepay: −15%
Paid up front for the year.
No mid-month overage — ever
Cross your band's ceiling in a good month and nothing happens to your bill and nothing happens to your jobs. We'll invite you to the next band at renewal. Crossing a ceiling means the product is working; we're not going to fine you for it.
Why "beta pricing"? Because it is. These are the launch bands. Our first ten customers keep their tier price for 12 months past general availability, written into their agreement rather than promised on a web page. Access is invitation-gated while we’re in beta — the price isn’t.
Questions buyers ask
Why a flat fee and not per-request or per-token?
Per-request pricing would give your bill a second variable on top of the one you came here to control — you'd need a meter to watch our meter. And a percentage of savings sounds aligned right up until the invoice becomes an argument about the baseline. A flat band means the fee is known on the first of the month, the savings number stays a report instead of a negotiation, and our incentive is simply that you renew.
Do you resell tokens or touch my provider bill?
No. You bring your own provider keys; jobs run on your accounts; your provider bills arrive as they always did, at whatever rates you've negotiated. We never buy a token to resell and we never hold a credit balance of yours.
What exactly counts toward spend under management?
Every job routed in the billing month: cloud-executed jobs at actual provider cost, locally-executed jobs at the published list price of the capable cloud model they displaced. "Published list" means the model provider's first-party public price for the model that ran — pinned in your contract, so a price difference between provider rails can never silently move your number. Every line reconciles to a metering row you can read.
What happens when I cross my ceiling?
Nothing, mid-month. At renewal we'll invite you to the next band. No surcharge, no throttle, no held jobs.
What happens when the trial ends?
Routing stops; your jobs don't. They keep running on your own cloud account at your own rates — exactly as they would if you'd never integrated with us — so nothing in your application breaks and no job is ever held waiting for a subscription. What stops is the optimization: we no longer send work to the cheapest executor that can finish it on time. Metering and reporting keep running, so you can still see what you're spending and what routing would have saved. That's the argument for subscribing, and switching it off would delete the only reason to come back.
Are my provider keys safe with you?
Keys live in a dedicated cloud secrets store with per-organization access control — never in our application database, never in logs. You can verify a key before any job uses it, and revoke it at any time; a revoked key degrades your org to local-only routing rather than failing your jobs.
What if a payment fails or I cancel?
The same state a finished trial lands in: routing stops, your jobs carry on running against your own cloud account, and metering and reporting continue. A billing problem never stops your work — not the jobs already running, and not the ones you send afterwards. That promise is load-bearing around here.
Why does self-hosted cost more, not less?
Because you're not buying our hosting — you're buying support for software running where we can't see it. That's genuinely more expensive to do well, so it costs more. We'd rather price it honestly than hide it in an "enterprise uplift" nobody explains.
Take the 30 days and see the number
The whole product, on your own accounts, computing savings from your own traffic. If the number isn't worth the subscription, you'll know before you pay anything.
Invitation-gated during beta. The price isn't.