Every Feature on Every Plan: No Fee, No Gate
Guardrails, audit trails, budgets, evals, A/B tests and prompt management are on every nRouter plan, and the one plan on sale is pay as you go at a 0% platform fee. Nothing is gated and nothing is marked up — here is the reasoning and what the bet costs us.

Direct answer: Why nRouter unlocks every governance feature on pay as you go at a 0% platform fee — with transparent pricing and the honest cost.
The position: every nRouter account carries every feature. Guardrails, audit trails, per-team budgets, evals, A/B tests, prompt management and fallback chains are included from your first request. nRouter sells one plan, pay as you go, at a 0% platform fee: a credit purchase charges exactly the credits bought ($5 costs $5.00, $100 costs $100.00), nRouter absorbs card processing, and usage settles at the served model's exact list price (0% markup).
The industry norm is the opposite, and the norm has a good argument behind it.
Figure 1: With a 0% platform fee, every dollar you pay becomes inference value — versus resellers that skim 4–20% off the top.
So this post takes that argument seriously, shows the math on both sides, states what our choice costs you, and names the buyers for whom our pricing is genuinely the wrong shape.
The position
There is no entitlement matrix here. There is no "available on Enterprise" column, no feature flag keyed to a plan, and no upgrade prompt attached to a capability. If a control exists in the product, it is on your account from your first request.
What the model delivers is transparent pricing and direct access:
Pay as you go every feature ✓ 0% platform fee charges exact credits bought exact list price settlement
Enterprise every feature ✓ custom terms custom procurement custom limitsA credit purchase charges exactly the credits bought: $100 of credits is charged $100.00, and the full $100 lands on your balance at a 0% platform fee. nRouter absorbs the card-processing cost. Usage settles at the served model's exact list price with 0% markup — that mechanism is markup-free credits, and it is the foundation of this position.
What we were asked for instead
Put the strongest version of the counter-argument up front, because a position argued against a weak version of the ask persuades nobody.
"Gate the enterprise features. It is the standard model, and it works."
- It funds the product. SSO, audit export, advanced RBAC and compliance features are disproportionately expensive to build and are wanted by disproportionately well-funded buyers. Charging those buyers for those features is how the rest of the product gets built and stays cheap for everyone else.
- It lets small teams pay less. A stripped entry plan can be priced near zero precisely because it is stripped. Bundling the whole AI governance surface into every plan means the entry plan has to carry some of that cost.
- It matches how buying actually happens. An enterprise buyer expects a line item and a negotiation. A tier is a legible artifact for procurement in a way that "everyone gets everything" is not.
- It creates a natural expansion path. Land small, expand when the customer needs the next capability. That is a well-understood, well-behaved revenue motion.
Every one of those is true. We are not claiming the standard model is stupid; we are claiming it produces one specific outcome we are unwilling to ship.
What that would cost you
The outcome is this: the customers with the least margin for an incident are the ones priced out of the controls that prevent incidents.
Look at what typically sits above the gate, and who needs it most:
| Gated capability | Who is usually on the entry plan | What the gap costs them |
|---|---|---|
| PII redaction in logs | A three-person team shipping fast | Personal data in a log store nobody audits |
| Audit trail of admin actions | The team with no dedicated security hire | No answer to "who changed that key" |
| Hard spend caps | The team with the smallest runway | A runaway loop that empties the account |
| Per-key rate limits | The team with one shared key | One bad deploy exhausting everyone's quota |
| Guardrails on output | The team with no review process | A prompt-injected response reaching a user |
A large company that hits the gate writes a check. A four-person startup that hits the gate ships without the control, tells itself it will revisit at Series A, and does not. The gate does not convert that customer; it just removes their seatbelt.
Money makes it concrete. A single runaway agent loop costing $2,000 in a weekend dwarfs the price difference between any two plans — and a hard spend cap is precisely the feature most likely to be sitting behind one. The protection is worth more than the tier that hides it, to the customer who cannot afford either.
What the plans actually change
Here is every difference, with nothing omitted:
| Pay as you go | Enterprise | |
|---|---|---|
| Monthly subscription | $0 | Custom |
| Platform fee | 0% (exact credits charged) | Custom terms |
| Model usage settlement | Exact provider list price (0% markup) | Exact provider list price |
| Card processing | Absorbed by nRouter | Custom |
| Guardrails, budgets, RBAC, audit | Included | Included |
| A/B tests, prompt management, evals | Included | Included |
| Fallback chains, routing controls | Included | Included |
| Minimum credit purchase | $5 | Custom |
No subscription plan is sold (existing subscribers keep theirs). Every governance feature is included on every account without gating. The canonical version of this table is pricing, and if this post ever disagrees with it, the page is right and the post is a defect.
The pricing, worked
Because there is no feature gating, you can compute what you will pay instead of guessing at it. With a 0% platform fee, a credit purchase charges exactly the credits bought, nRouter absorbs the card-processing cost, and usage settles at the served model's exact list price (0% markup):
| Monthly provider spend | Platform fee (0%) | Charged for those credits |
|---|---|---|
| $250 | $0.00 | $250.00 |
| $750 | $0.00 | $750.00 |
| $2,500 | $0.00 | $2,500.00 |
| $10,000 | $0.00 | $10,000.00 |
Every dollar of credits buys a dollar of model inference. No subscription plan is sold (existing subscribers keep theirs). The cost calculator runs this against your own numbers.
What we do instead
Every control is live from your first request. Concretely, what "included" means:
- Guardrails on every request, pre-call and post-call, not as an add-on: Inline LLM Guardrails: Redact, Block, or Flag Every Request and the guardrails guide.
- Budgets at org, team and key scope, with a hard refusal rather than an alert after the fact: how to set hard spend limits.
- Rate limits per key, team and org so one workload cannot starve another: RPM and TPM limiting.
- PII redaction in logs without losing the ability to debug: redacting PII from LLM logs.
- An audit trail of administrative actions, from day one: building a tamper-evident audit trail and the audit log guide.
- Team-scoped keys, budgets and guardrails so the org chart is expressible: org, team, member scoping.
- A/B tests and prompt management as first-class surfaces rather than enterprise extras: deterministic A/B testing and server-side prompt templates.
That list is the product. It is not the top tier of the product.
The trade we are making
The honest accounting, because this bet is not free.
We leave revenue on the table, deliberately. A vendor that bundles SSO and audit export into a negotiated enterprise contract books more per large customer than we can, because we already handed those capabilities to that customer on the entry plan. That is not a rounding error; it is the single most reliable expansion lever in B2B software and we do not have it.
We take 0% markup and a 0% platform fee. A customer who optimizes their prompts pays less for model inference. We think that is the correct alignment — our value comes from the gateway being genuinely worth using, and it is why cutting your costs is something we write about rather than quietly discourage.
Our entry plan is not free. Signup is card-required and takes a real $5 minimum charge (charging exactly $5.00 for $5.00 of credits, at a 0% platform fee). A competitor with a stripped free tier will always be able to say a shorter word than we can.
Procurement sometimes wants a gate. More than once, a buyer has asked what they get for moving up and been unsatisfied by "an allowance and higher limits." The absence of a feature ladder can read as a missing enterprise story, and we have to argue our way through that rather than pointing at a tier chart.
Who this is wrong for
Choose a differently-shaped vendor if:
- You want a genuinely free plan and do not need governance. If your usage is a hobby project and controls are not the point, a vendor with a free observability tier will serve you better than our $5 floor. We are not competitive on "costs nothing".
- Your spend is very large and very steady, and you want a bespoke contract shaped around specific capabilities. Our answer is custom terms and custom limits via enterprise — but if your procurement process needs a capability-by-capability negotiation, our uniform feature set makes that conversation shorter than you may want it to be.
- You need exactly one narrow capability and nothing else. If all you want is request logging, a focused observability tool priced for that one job may cost less than a gateway that includes eleven things you will not use. Our bundle is only a bargain if you use the bundle.
- You must run on your own infrastructure. Different axis, same honesty: see Managed LLM Gateway vs Self-Hosted: Why We Carry the Pager.
How you can hold us to it
This position is unusually easy to falsify, which is the point:
- Open the pricing page. Pricing is the source of truth for the 0% platform fee, pay as you go, and the $5 minimum. If it ever grows a feature column that differs by plan, we broke this promise and you can point at it.
- Try a governance feature on the entry plan. Set a budget, enable a guardrail, create a second team, export an audit log — on pay as you go. If any of it prompts you to upgrade, that is a bug and we want the screenshot.
- Check your credit charge. A credit purchase charges exactly the credits bought ($5 costs $5.00, $100 costs $100.00) at a 0% platform fee, with nRouter absorbing card-processing costs. Compare the amount that lands on your balance with the amount you paid: the credits arrive in full, and usage settles at the served model's exact list price with 0% markup. That is markup-free credits as an arithmetic claim rather than a slogan.
- Reconcile the ledger. Every movement is a row: how to read your credit ledger. A fee that appears anywhere other than where we say it appears is visible there.
- Compare the model price to the provider's. The rate you are charged for a model should be the provider's list rate — open OpenAI's or Azure OpenAI Service's page next to your ledger row and check the per-million-token figure yourself. The rest of the rate cards are in Sources and the catalog is on models.
- Read the comparisons. Our head-to-head posts state, with dated links to each vendor's own pricing page, which capabilities sit behind which tier elsewhere — for example Helicone and Portkey. If we have misrepresented anyone, the link is right there to check us with.
Try it
Test the claim on the cheapest plan, which is where a gate would show up if there were one. Load the $5 minimum, then set a budget and a guardrail before you send a single production request:
# 1. a real call, on pay as you go
curl https://api.nrouter.ai/v1/chat/completions \
-H "Authorization: Bearer $NROUTER_API_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"MODEL_FROM_YOUR_CATALOG","messages":[{"role":"user","content":"ping"}]}' \
-i | grep -i '^x-nr-'
# 2. now go set a hard cap and a guardrail in the dashboard,
# on the same plan, with no upgrade in the way.Then walk budget controls, guardrails and API key management and confirm none of them asks you for a plan change. Signup takes a real $5 minimum charge (charging exactly $5.00 for $5.00 of credits, at a 0% platform fee). Start at signup, price it on the cost calculator, or bring the sceptical version of this argument to the community.
See also
- Markup-free LLM credits — why model usage settles at exact provider list prices with zero markup.
- Inline LLM Guardrails: Redact, Block, or Flag Every Request — the single feature this position is most often tested against.
- How to set hard spend limits — the control a gated plan most commonly withholds from the customer who needs it most.
- Pay as you go or a subscription: which LLM gateway plan is cheaper? — how pay as you go compares to grandfathered subscriptions.
- Managed LLM Gateway vs Self-Hosted: Why We Carry the Pager — the operational case for a managed gateway without platform fees.
- Cost honesty — the same stance applied to a single number: an unpriceable call is unpriced, never zero.
- Pricing — the 0% platform fee, pay as you go, and the $5 minimum purchase; this post defers to it.
Sources
Verified 2026-08-23. Corrections to hello@nrouter.ai and we will update.
Competitor names appearing above are trademarks of their owners. nRouter is not affiliated with or endorsed by them. This post makes no new claim about any other vendor's tier contents — the vendor-by-vendor gating claims live in the comparison posts linked in the previous section, each carrying its own dated link to that vendor's public pricing page. The nRouter figures here (0% platform fee, pay as you go charging exact credits bought, $5 minimum purchase) are authoritative on our pricing page rather than in this post. The provider rate cards are listed because they are what the "model price is the provider's price" check in the previous section compares against.
- nRouter pricing: nrouter.ai/pricing
- nRouter model catalog: nrouter.ai/models
- Anthropic pricing: anthropic.com/pricing
- OpenAI API pricing: OpenAI rate card
- AWS Bedrock pricing: aws.amazon.com/bedrock/pricing
- Google Vertex AI generative-AI pricing: cloud.google.com/vertex-ai/generative-ai/pricing
- OpenAI pricing, developer-docs copy: platform.openai.com/docs/pricing — the per-million-token rates check 5 compares a ledger row against.
- Azure OpenAI Service pricing: azure.microsoft.com — the same check for a model served through Azure.
OpenAI, Anthropic, AWS, Microsoft and Google are trademarks of their respective owners. nRouter is not affiliated with or endorsed by them.
Frequently asked questions
Why was nRouter built beyond basic model routing?
There is no entitlement matrix here. There is no "available on Enterprise" column, no feature flag keyed to a plan, and no upgrade prompt attached to a capability.
Why is a thin routing library not enough for production?
Put the strongest version of the counter-argument up front, because a position argued against a weak version of the ask persuades nobody.
What does a thin routing library leave your team to operate?
The outcome is this: the customers with the least margin for an incident are the ones priced out of the controls that prevent incidents.
The team building nRouter.
More from Company
All posts →
Four Outcomes That Get an LLM Gateway Funded
Build the internal business case for an LLM gateway on four quantifiable outcomes: total spend reduction, cost per call, tail latency, and developer speed.

Managed LLM Gateway vs Self-Hosted: Why We Carry the Pager
Why nRouter is a managed LLM gateway rather than self-hosted software: the operational burden of proxy hosting, and when running your own infra still wins.

Cost Honesty: Unpriced Is Never $0 on Your LLM Bill
Why nRouter reads the settled LLM cost directly from providers instead of guessing, and why unknown model costs are reported as unpriced rather than as $0.