$49/mo
Portkey's Production tier: flat, predictable, and cheaper than percentage fees above ~$900/mo of spend
Blog
Portkey alternatives: control plane, gateway, or neither
Portkey sells visibility: logs, guardrails, retries, compliance, at a flat fee. People shop for alternatives from two directions, cheaper control or less apparatus, and the right answer depends on which direction you came from.
Skip the read: get a measured recommendation in a few quick questions. Run the Stack Finder
100k
logged requests included at that tier; $9 per extra 100k. The meter is observability, not tokens
2 paths
out: self-host the same function (LiteLLM) or decide observability was never your real problem
The main Portkey alternatives in 2026 are LiteLLM (free, self-hosted, open source), OpenRouter (5.5% fee on credit purchases), Requesty (5% token markup), and Pareto (a blended model billed at cost). Portkey itself charges a flat $49/month for its control plane and does not mark up token prices.
What Portkey actually charges for
Portkey does not mark up tokens; your providers bill you directly. The $49/month buys the control plane: request logs, guardrails, retries, fallbacks, prompt management, compliance features. That is why comparing it to token-fee gateways confuses people: it is priced on observability volume (100k logged requests included, $9 per additional 100k), not on spend.
Want this priced against your own workload? Run the Stack Finder or start with $100 in credits.
The alternatives, by direction
You want the same function, cheaper: LiteLLM
Portkey's gateway is open source, and LiteLLM is the fully open alternative: self-host either and the flat fee becomes ops time. Right when infrastructure is already your team's job; see our honest math on what free costs before assuming it is a saving.
You wanted a simpler gateway all along: OpenRouter or Requesty
If you adopted Portkey for multi-provider access rather than governance, a catalog gateway is less machinery: OpenRouter (5.5% on credits, 400+ models) or Requesty (5% markup, caching and EU residency included). The trade: percentage fees scale with spend, and above roughly $900/month Portkey's flat fee is cheaper than either; the full crossover math is in our gateway comparison.
Your actual problem is the bill: Pareto
Observability tells you where the money went. It does not make tasks cheaper. If the line item you are staring at is token spend, the lever is not a better dashboard, it is not paying list prices: Pareto auto-routes each request to the optimal model and bills at cost, with the receipts on the model card (7/7 benchmarks matched or beaten vs Opus 4.8 at 1 to 45 cents on the dollar per task).
Honest cases to stay on Portkey
- Compliance is load-bearing. If audit trails, PII guardrails, and access controls are contractual requirements, a purpose-built control plane at $49/month is one of the cheapest line items in your stack.
- You spend real money. Above ~$900/month, every percentage-fee alternative costs more than Portkey does.
- Multi-team governance. Rate limits and budgets per team are exactly the apparatus you cannot get from a bare gateway.
Common questions
Is Portkey worth $49 a month?
If you spend more than about $900/month on LLMs, yes by arithmetic alone: every percentage-fee gateway costs more at that point. Below that, you are paying for governance features, and whether those are worth $49 depends on whether anyone would notice if the logs disappeared.
Is there a free Portkey alternative?
Portkey's own gateway is open source, and LiteLLM is fully open. Free means self-hosted: the license costs nothing and the ops time does not. Portkey also has a free developer tier (10k logged requests) that covers real prototyping.
Does Portkey mark up token prices?
No. Providers bill you directly at their rates; Portkey charges the flat platform fee. That structure is exactly why it wins on cost at higher spend versus percentage-fee gateways.
Can Portkey lower my LLM bill?
Indirectly at best: caching and fallbacks trim waste, and visibility helps you find expensive traffic. It does not change what a token costs. If the bill itself is the problem, that is a routing-and-pricing question, not an observability one.
Not sure which model fits?
The Stack Finder asks a few quick questions about your workload and gives you a straight recommendation. No account required.
Cut the bill itself. $100 to verify.
Buy Pareto API credits