Stay on LiteLLM if you already run it, can patch it quickly and want no gateway fee. Look at Portkey for a hosted control plane with logs, at OpenRouter for one bill and no servers, and at Orq.ai if EU hosting by default matters. On October 15, 2026, a gateway fee at 1,000,000 requests and $10,000 of model spend a month listed at $130 on Portkey Production, $550 on OpenRouter Standard and $450 on Orq.ai, against no license fee for open-source LiteLLM on your own servers.
- LiteLLM's code is MIT licensed except the enterprise/ directory, and that directory needs a paid subscription with seats for production use.
- LiteLLM does not publish an Enterprise price (as of October 15, 2026); a 30-day trial key is available by email.
- A self-run LiteLLM proxy needs PostgreSQL for virtual keys, a pod of 1 vCPU and 4 Gi of memory, and Redis 7.0 or newer once you run more than one instance.
- Hosted gateways charge a percentage of credits (OpenRouter 5.5 percent, Orq.ai 4.5 percent) or per recorded log (Portkey, $49 for 100,000 logs).
- Portkey belongs to Palo Alto Networks since May 29, 2026, and its Terms of Service page holds no contract text, only the site footer.
On October 15, 2026 I read 34 vendor pages: LiteLLM's license files, production guide, cost-tracking and key documentation, Enterprise page and security notices, then the pricing pages, terms and data documentation of Portkey, OpenRouter, Orq.ai and Dataiku. 7 products sit in the gateway niche of our directory. I kept four as alternatives and left two out, for reasons given in the last section.
The page does not rank the four. LiteLLM is the reference, and the question is what you give up and what you pay when you leave it. For the broader claim check on gateways, including the outages and the LiteLLM incident, see LLM gateways: what they add, what they cost and where they become a risk. Here the starting point is LiteLLM itself.
Shortlist: which LiteLLM alternative fits which situation
Portkey (Prisma AIRS AI Gateway)A match for teams that want a hosted gateway with logs, guardrails and prompt management and accept that Palo Alto Networks now owns the vendor. Production lists at $49 a month for 100,000 recorded logs, and the open-source gateway is MIT licensed.
OpenRouterSuits teams that want one API and one bill for 500+ models without running servers. Standard adds 5.5 percent on credit purchases, and with your own provider keys the first $25,000 of list-price usage a month carries no fee.
Orq.aiFits teams that need an EU-built, EU-hosted gateway with an OpenAI-compatible endpoint, per-team budgets and PII redaction. Pay-as-you-go has no base fee and a 4.5 percent fee on Orq.ai credits.
DataikuOnly worth a look if you already run Dataiku for data and ML work. Its LLM Mesh puts quotas and cost controls on model access inside the platform, and the vendor publishes no price.
What a gateway costs at 100,000 and 1,000,000 requests a month
The vendors do not bill the same thing. LiteLLM's open-source code costs nothing to license and moves the bill to your servers. Portkey bills recorded logs, OpenRouter and Orq.ai bill a percentage of credits, and Dataiku sells a platform. So I fixed one reference: 100,000 requests with $1,000 of model spend a month, then ten times that, and applied each vendor's listed rule.
Running LiteLLM yourself is not free of effort. The production guide asks for a pod of 1 vCPU and 4 Gi of memory as requests and limits, PostgreSQL for virtual keys, and Redis 7.0 or newer once more than one instance runs. If the database goes down, keys already in the cache keep working for 60 seconds by default and uncached key lookups fail. The vendor publishes no server cost, so I cannot give you a number for that part.
What this means for you: at these volumes a hosted fee is between $49 and $800 a month, which is often less than the time of one engineer who patches and monitors a proxy. It is more than $0, though, and it grows with spend for the percentage vendors. Put your own request count and spend into the table before you decide.
List prices, read October 15, 2026
Gateway fee for the same traffic
Reference traffic: 100,000 requests and $1,000 of model spend a month, then 1,000,000 requests and $10,000. One request is assumed to be one recorded log. Sort by any column. Model costs themselves are the same everywhere, so only the gateway fee is shown.
| Dataiku LLM Mesh | Platform subscription | Price not published by the vendor (as of October 15, 2026) | Same as at 100,000 requests | Dataiku Cloud (the only option I checked) |
| LiteLLM Enterprise | Subscription with seats | Not published by the vendor (as of October 15, 2026) | Same as at 100,000 requests | Your own infrastructure |
| LiteLLM open source | No license fee outside enterprise/ | $0 license; servers, Postgres and Redis are yours | $0 license; servers, Postgres and Redis are yours | Your own infrastructure |
| OpenRouter Business | 8 percent on credit purchases | $80 | $800 | Vendor cloud, EU and US routing |
| OpenRouter Standard | 5.5 percent on credit purchases | $55 | $550 | Vendor cloud |
| OpenRouter, own provider keys | No fee up to $25,000 of list-price usage a month, then 5 percent | $0 | $0 | Vendor cloud |
| Orq.ai pay-as-you-go | 4.5 percent on Orq.ai credits; spans beyond 100,000 cost 7 euros per 100,000 | $45 | $450 | Vendor cloud, EU by default |
| Orq.ai, own provider keys | Free up to 1 million requests a month, then 4 percent | $0 | $0 | Vendor cloud, EU by default |
| Portkey Production | $49 a month with 100,000 logs, $9 per further 100,000 up to 3 million | $49 | $130 ($49 plus 9 blocks of $9) | Portkey cloud, or the MIT gateway on your servers |
Source: vendor pricing pages, read October 15, 2026; list prices without tax. Percentages are applied to the model spend shown, my calculation.
Stay or switch: license, features and who runs it
Not everyone should leave. LiteLLM's repository had 61,283 stars when I pulled the GitHub record on October 15, 2026, and its latest release, v1.105.1, came out on October 14. The project is active, and its LICENSE file puts everything outside the enterprise/ directory under MIT.
License. The enterprise/ directory has its own license. It lets you copy and modify the software for development and testing without a subscription, and it forbids production use without a valid subscription for the right number of seats. Teams that switched on SSO or audit logs from that directory during a trial and kept it running should treat this as the first reason to act.
Features. Two LiteLLM pages disagree. The Enterprise page lists virtual keys with budgets under its governance features, while the home page lists virtual keys, budgets and teams in the free tier, and the key documentation I read marks key rotation as an Enterprise feature. SSO, SCIM, JWT authentication, audit logs and RBAC are Enterprise on both vendor pages. Test your exact feature set against the 30-day trial key before you pay or leave.
Operations. A gateway holds every provider key, and LiteLLM's own security notices show what that costs to run. The box below lists them with dates. The vendor names the affected versions, which is a point in its favor.
What this means for you: if nobody owns patching and version pinning, a hosted gateway moves that job to a vendor, and the price table shows the cost. If you must keep prompts and logs on your own servers, leaving may cost more than it saves.
Try it
Stay on LiteLLM or switch?
Three yes or no questions. The result is a starting point, not a purchase recommendation and not legal advice.
Do you run the enterprise/ features of LiteLLM in production, such as SSO or audit logs, without a paid subscription?
Dated notices on LiteLLM's security index and the Portkey owner change (read October 15, 2026):
- March 18, 2026: guardrail logging exposed secret headers in spend logs and traces
- March 24, 2026: suspected supply chain incident, versions 1.82.7 and 1.82.8 on PyPIThe vendor says they were live for about 40 minutes. Users of the official Docker image with pinned dependencies and of LiteLLM Cloud were not affected. Versions from 1.83.0 are clean.
- April 21 and April 29, 2026: CVE-2026-30623 (command injection via an MCP SDK) and CVE-2026-42208 (LiteLLM Proxy)
- June 1, 2026: authentication bypass through Host header injection, fixed in 1.84.0 and later
- September 8, 2026: updated SOC 2 Type 2 report available
- April 30 and May 29, 2026: Palo Alto Networks announces and completes the acquisition of Portkey
The four alternatives, and who each one is not for
Portkey sells a hosted gateway with logs, guardrails, prompt management and role-based access. Developer is free with 10,000 recorded logs and 3 days of log retention, and Portkey marks it not suitable for production. Production is $49 a month, keeps logs 30 days and metrics 90 days, and its overage rule runs up to 3 million logs. SSO, a private cloud and data export sit in Enterprise. Portkey's website now reads Prisma AIRS AI Gateway after the acquisition, and the press release promises continued support for customers without mentioning the open-source gateway. That repository is MIT licensed, and its last push was on May 25, 2026. If you chose Portkey for its independence, that changed on May 29, 2026.
OpenRouter is the opposite of LiteLLM. You run nothing, and one API reaches 500+ models from 80+ providers. The FAQ says it passes provider prices through without markup on inference, and the fee is on credit purchases. By default it does not store prompts or responses, and logging is opt-in. EU and US routing exist only on Business and Enterprise, and it fails closed if no provider in the region serves the model. It is not for teams that need per-team spend controls inside their own network, or SSO on the Standard plan.
Orq.ai is built in Amsterdam and hosted in the EU by default. Its gateway offers an OpenAI-compatible endpoint to 500+ models from 30+ providers, budgets per user and team, and PII redaction. The pricing page lists SOC 2 Type II and ISO 27001. Orq.ai deletes observability data after 14 days on Free and 30 days on pay-as-you-go. Teams that want to keep every trace for a year need a custom plan, and teams that only want a proxy will pay for more platform than they use.
Dataiku is a data and ML platform, and its LLM Mesh is a gateway layer inside it. The product page lists quotas, budget enforcement and usage tracking, and the documentation index shows an OpenAI-compatible API section. I read only the index, not the details. It is for companies that already pay for Dataiku. A team that just wants to replace a proxy should look at the other three.
What this means for you: a hosted control plane points to Portkey, one bill and no servers to OpenRouter, EU hosting by default to Orq.ai, and an existing data platform to Dataiku.
Sources: [3][17][18][16][19][4][5][20][21][6][22][23][7][24]
What leaving costs: terms, cancellation, export, deletion
Because LiteLLM is software you run, leaving it is mostly configuration. The model list lives in config.yaml, optionally also in the database. Spend is stored per key, user and team in a SpendLogs table, and the /spend/logs/v2 endpoint pages through up to 1,000 rows at a time. Clients that already speak the OpenAI format change a base URL and a model name.
The harder part is the contract with the next vendor. I read each one's terms on October 15, 2026. OpenRouter lets you terminate any time but refunds unused credits only within 24 hours, expires them after 365 days, and does not refund platform fees. Orq.ai ends a subscription at the end of the term without partial refunds and asks for two months of written notice to switch providers. Portkey's terms page contains no contract text, so I cannot state its term or notice period. Dataiku's addendum names deletion after termination without a deadline.
What this means for you: the notice period is rarely the expensive part. Paying two gateways during the parallel run, re-issuing keys and rebuilding fallbacks cost more. Keep credits on pay-as-you-go vendors low so expiry hurts little, and ask Portkey for its contract before you sign.
What each vendor's own documents say about leaving (read October 15, 2026):
- LiteLLM open source: no contract, you delete your own database and keysEnterprise terms are not published by the vendor (as of October 15, 2026); production use of enterprise/ needs a subscription with the right number of seats.
- Portkey: the Terms of Service page shows no contract text, only the site footerDeveloper logs are kept 3 days and Production logs 30 days. The Enterprise plan lists data export. Term, notice and deletion rules are not published on that page (as of October 15, 2026).
- OpenRouter: terminate any time, but refunds for unused credits only within 24 hours of purchasePlatform fees are not refundable and credits expire 365 days after purchase. On account termination the remaining credits are refunded within 30 days. Terms updated August 31, 2026.
- Orq.ai: cancel at the end of the current term, no refund for partial periodsThe terms ask for two months of written notice to switch providers, offer a final data extract in a portable format, and erase customer materials the day after a 30-day retrieval window. Backups are overwritten within a month.
- Dataiku: the data processing addendum says personal data is deleted after terminationNo deadline is stated in the addendum, and I did not read the Cloud terms it refers to.
Checklist before you move off LiteLLM
Your progress stays saved in this browser.
Sources: [25][26][27][9][28][29][30][31][32][33][34][35][36]
Corrections, disagreements and what I left out
I updated one value from our own data. Our LiteLLM profile quoted about 59,800 GitHub stars from September 28; the GitHub record on October 15 shows 61,283. The other entries I checked, such as Portkey's $49 plan, OpenRouter's 5.5 percent fee and Orq.ai's 4.5 percent fee, matched the vendors' pages.
Sources disagreed in two places. LiteLLM's documentation says 100+ LLMs while its home page says 140+ providers, and its Enterprise page and home page place virtual keys in different tiers. Portkey's repository shows 13,191 stars through the GitHub record, while its site footer says 10.2K.
I left out Msty, a desktop client for language models, and Artificial Analysis, a benchmark site. Neither routes production traffic. I also left out review-site opinions and Reddit threads, because they are not primary sources, and I did not cost Portkey's Enterprise plan, which has no public price.
Sources
- LiteLLM docs: Production setup
- LiteLLM Enterprise page
- Portkey pricing page
- OpenRouter pricing page
- OpenRouter docs: FAQ
- Orq.ai pricing page
- Dataiku: Generative AI and LLM Mesh
- LiteLLM LICENSE file
- LiteLLM enterprise/LICENSE.md
- LiteLLM website
- LiteLLM docs: Virtual keys
- LiteLLM repository on GitHub (API record)
- LiteLLM latest release (API record)
- LiteLLM security posts (index)
- LiteLLM: Suspected supply chain incident (March 24, 2026)
- Palo Alto Networks: acquisition of Portkey completed (May 29, 2026)
- Portkey website
- Palo Alto Networks: plan to acquire Portkey (April 30, 2026)
- Portkey gateway repository (API record)
- OpenRouter docs: Data collection
- OpenRouter docs: In-region routing
- Orq.ai AI gateway page
- Orq.ai docs: Data retention
- Dataiku docs: Generative AI
- LiteLLM docs: config.yaml
- LiteLLM docs: Cost tracking
- LiteLLM docs: Overview
- Portkey Terms of Service page
- Portkey docs: Logs
- Portkey docs: Chat completions API
- OpenRouter Terms of Service
- OpenRouter Privacy Policy
- OpenRouter docs: Quickstart
- Orq.ai Terms of Service
- Orq.ai Privacy Policy
- Dataiku Cloud Data Processing Addendum


