A Portkey alternative with access and billing built in
Portkey is an AI gateway and LLM ops control plane — observability, guardrails, prompt management — built around an open-source gateway core, now part of Palo Alto Networks. It is BYOK-first: you bring your own provider API keys and it routes and observes your calls. Router One starts from the other side: a fully managed, OpenAI-compatible gateway where upstream model access, billing, smart routing, and per-request cost traces come built in — one key and one prepaid wallet for 40+ supported models, reachable globally and from Mainland China.
TL;DR · Pick Portkey if you already hold provider accounts and want enterprise LLM ops — guardrails, prompt management, self-hosted deployment — layered on top of them. Pick Router One if you want zero provider accounts to manage: one key and one prepaid wallet cover model access, billing, and routing, reachable from Mainland China.
Two different starting points
| Feature | Router One | Portkey |
|---|---|---|
| Product focus | Managed gateway: access, billing, routing, traces in one | AI gateway + LLM ops control plane: observability, guardrails, prompt management |
| Smart routing & fallback | EWMA latency + posted cost + 5xx rate, managed | Fallbacks, retries, load balancing, conditional routing across your own keys |
| Per-request observability | Traces: final model/provider, tokens, cost, latency, status | Deep logging, tracing, 21+ metrics, OpenTelemetry-compliant |
| OpenAI-compatible API | Yes — Chat Completions, drop-in base URL | Yes — one API across 250+ models via your provider keys |
| Provider access & billing | Upstream access included through one key and wallet | BYOK — separate accounts and billing with each provider |
| Accessible from Mainland China | China-reachable endpoint with published latency benchmark | No documented China endpoint; BYOK still needs reachable provider accounts |
| Payment methods | Card or Alipay in one checkout, USDT/USDC on 6 chains | Platform billed by card; model usage billed by each provider |
Where the managed gateway helps
No provider accounts to manage
Portkey's BYOK model means you still open, fund, and reconcile an account with every provider you call. Router One includes upstream access through one key and one prepaid wallet — no per-provider invoices to reconcile.
Pay for tokens, not logs
Portkey charges for the platform per recorded log while your model usage is billed separately by each provider. Router One has no separate platform fee: you prepay one wallet and pay per token for the models themselves.
Reachable worldwide, including Mainland China
A BYOK gateway can't change where your provider accounts are reachable from. Router One's endpoint serves distributed teams everywhere, including Mainland China, with model access bundled in. Based on the China latency benchmark last updated 2026-05-15, Router One measured 110-130ms p50 across Beijing, Shanghai, and Shenzhen; individual networks may vary.
Switch with one base URL change
Router One speaks the OpenAI Chat Completions API, so anything pointed at Portkey's OpenAI-compatible gateway moves over with a base URL and key change — and stops needing per-provider keys at all.
# Point your client at Router One export OPENAI_BASE_URL=https://api.router.one/v1 export OPENAI_API_KEY=sk-your-router-one-key
FAQ
Does Portkey give me access to models, or do I need my own API keys?
Portkey is BYOK: you bring your own OpenAI, Anthropic, or other provider API keys and it proxies, routes, and observes your calls. It does not sell model access. Router One is the opposite model — one key and one prepaid wallet cover upstream model access and billing, with no provider accounts needed.
Is Portkey open source?
Yes. The gateway core is open source and self-hostable, and in March 2026 Portkey open-sourced its formerly SaaS-only governance and observability features. Router One is a fully managed service rather than a self-host product.
Who owns Portkey now?
Palo Alto Networks completed its acquisition of Portkey in late May 2026, and Portkey is becoming the AI gateway inside Palo Alto's Prisma AIRS security platform. The open-source gateway remains available.
When is Portkey the better fit?
If your team already holds provider accounts or contracts and wants governance on top — self-hosted or VPC deployment, guardrails, prompt management, OpenTelemetry tracing, SSO, and compliance certifications like SOC 2 and HIPAA — Portkey's LLM ops tooling goes far deeper than a gateway's built-in traces. Security-led organizations already on Palo Alto's stack are a natural fit too.
Can I migrate from a Portkey-proxied setup?
Yes. Both speak the OpenAI-compatible Chat Completions shape, so most integrations move with a base URL and API key change. After the switch you no longer need per-provider keys — upstream access is included.
Can I use Portkey from mainland China?
Portkey documents no China endpoint or local payment options, and because it is BYOK you still need reachable accounts with upstream providers — several of which, like OpenAI and Anthropic, do not serve mainland China. Router One provides a China-reachable endpoint with bundled model access and local payment rails: card or Alipay in one hosted checkout, plus USDT/USDC on six chains.
More comparisons
- OpenRouter alternative
- LiteLLM alternative
- Vercel AI Gateway alternative
- Helicone alternative
- Cloudflare AI Gateway alternative
- Inference host alternative
- LLM observability
Want model access, billing, and traces behind one key?
Get your API key