# LiteLLM vs RouterPlus (slim)

> LiteLLM scores 62.4 (B) to RouterPlus's 50.3 (D) for model routing. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/litellm-vs-routerplus.md (~6,200 tokens) · this version ~3,630 tokens · JSON https://www.anchorterminal.com/compare/litellm-vs-routerplus.json · canonical https://www.anchorterminal.com/compare/litellm-vs-routerplus
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

LiteLLM scores 62.4 (B) on agent readiness against RouterPlus's 50.3 (D), and leads in every scored category. Both do model routing.

- LiteLLM: B 62.4, rank #559 of 1510 · https://www.anchorterminal.com/tools/litellm.min.md
- RouterPlus: D 50.3, rank #1071 of 1510 · https://www.anchorterminal.com/tools/routerplus.min.md
- LiteLLM, good for Teams that want one OpenAI-compatible endpoint over many providers on their own infrastructure, with per-key budgets, model allowlists and an MCP gateway. Ahead on Reliability, 70 against 42; Schema & documentation, 91 against 59; Agent ergonomics, 79 against 71; Security & auth, 72 against 59; Payments & pricing, 60 against 40; Maintenance & community, 82 against 44; Transparency & trust, 63 against 41. Also Open source.
- RouterPlus, good for Teams that call Claude, GPT and open-weight models from one key and want the cost of every call in the response, with their own provider keys where they have them. Also A hosted endpoint, with nothing to install.

| Category | LiteLLM | RouterPlus |
| --- | --- | --- |
| Reliability (16%) | 70 | 42 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 91 | 59 |
| Agent ergonomics (13%) | 79 | 71 |
| Security & auth (14%) | 72 | 59 |
| Payments & pricing (10%) | 60 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 82 | 44 |
| Transparency & trust (7%) | 63 | 41 |

| Fact (where they differ) | LiteLLM | RouterPlus |
| --- | --- | --- |
| Vendor | BerriAI | RouterPlus |
| Hosted endpoint | no (local only) | `https://api.routerplus.com/v1` |
| Pricing | Freemium | Pay per use |
| Licence | MIT, except the enterprise/ directory, which is under its own licence and needs an Enterprise licence key | Closed service. No terms of service for the gateway were found on routerplus.com or app.routerplus.com on 13 October 2026. The only terms on the site govern the capacity request form and name EVO HQ Inc, a Delaware corporation (https://routerplus.com/capacity/terms/). |
| Last release | 2026-11-05 | none |
| Privacy policy last updated | no date given | no document linked |
| Popularity | 63k stars, 22.5M PyPI/wk | none |

Why the edge:
- Maintenance & community, LiteLLM +38: LiteLLM 82 (v1.108.1 tagged on 5 November 2026, v1.108.0 and v1.106.7 on 3 and 4 November (30). 125 tags between 8 August and 6 November, stable, patch, release-candidate and dev builds, with patch releases for four minor lines at once (20). Reply times not measured. On the issues page 7 of the 15 newest had a reply on the day, workflows auto-close duplicates and label issues, and Discord is the listed community channel (12 of 25). The package is the official SDK, current, with OpenAI and Anthropic SDKs working against the gateway (12 of 15). Dependency and image scanning (OSV, zizmor, Scorecard, grype) run in CI, with pass state unchecked (8 of 10).); RouterPlus 44 (Router, read on the model lines. No changelog or release notes found. The blog, re-read on 4 November 2026, dates the launch of ScaleDown's extract-1 and summarize-1 on chat completions and classify-1 on the decisions API to 13 October 2026, and the catalogue now lists 105 chat models against 19 on 13 October, so the API changed within the last 30 days (30). The docs also date a console change on 17 October 2026 (keys can be copied again), which isn't counted, since it changes the console and not the API. Models carry a `deprecation_date` that delists them automatically, with no notice period stated (3 of 12). `POST /v1/signup` and the magic-link route were removed and Optimize is paused, none with a date we could find (3 of 8). No public changelog. Support is reached through the console and an email address, and wasn't tested (3 of 15). No public issue tracker for the gateway (0 of 10). No official SDK. The docs rely on the OpenAI and Anthropic SDKs and give client setups (5 of 15). No package or public repository to check (0 of 10).)
- Schema & documentation, LiteLLM +32: LiteLLM 91 (Every gateway serves Swagger at /, ReDoc at /redoc and the raw schema at /openapi.json, and the docs host a public Swagger explorer (25). llms.txt, llms-full.txt and a Markdown twin of every page via `.md` (10). Pages say what a feature is for and where its limits are, and the key-auth page explains how permissions are inherited and where they aren't, but the reference is very large for a model to navigate (16 of 20). OpenAI-shaped request schemas from Pydantic models, with `metadata`, `litellm_params` and config blocks left as free-form objects (10 of 15). A full error reference with the envelope, every status, response headers and how to tell gateway limits from provider limits, plus examples on every page (15). Release notes per version with dates, newest v1.108.0 and v1.106.7 on 4 November 2026 (15).); RouterPlus 59 (Router, scored on the API lines. No OpenAPI or other machine-readable contract for the gateway was found. It follows the OpenAI and Anthropic wire formats, which this checklist doesn't credit to a reseller, the same reading as Antseed (0 of 25). llms.txt, llms-full.txt and a Markdown copy of every page (10). Each route page says what it is for, what isn't available, and which route to use for which model, and the agent integration guide lists what not to build on (18 of 20). Request fields follow the upstream formats, and the wire compatibility page tables which fields pass, translate, drop or fail with a typed 400 (12 of 15). Curl, Python and TypeScript examples on every page, and an error reference with a class, status and remedy for each error (15). Routes are versioned under /v1 and the wire compatibility page says changing it needs a recorded decision, but no changelog or dated release notes were found, re-read on 4 November 2026 (4 of 15).)
- Reliability, LiteLLM +28: LiteLLM 70 (Read with the local-software lines, since the gateway runs on the operator's hardware and BerriAI hosts nothing an agent calls. litellm on PyPI states Python 3.10 to 3.14, and the gateway ships as a Docker image, a Helm chart and Terraform modules, with GHCR images signed by cosign (20). 51 GitHub Actions workflows plus a CircleCI config cover unit, proxy-database, end-to-end, chaos, mutation and UI tests. The GitHub API was rate-limited for our reader on 6 November and Actions pages refused it on 6 October, so we couldn't confirm main is passing (15 of 25). The issue tracker showed 1,674 open issues on 6 November, with eight bug reports among the 15 newest, seven of them with a reply, against a project that tags several releases a day (10 of 25, down from an unchecked 12). Release notes carry breaking-change bullets, but breaking changes land in weekly minor releases on the 1.x line, so version numbers don't signal them (10 of 15). 1.108.1, past 1.0 (15).); RouterPlus 42 (Hosted reading. No status page found. Model pages show each provider's uptime over the last 24 hours and no incident history, and status.routerplus.com failed at our proxy again on 4 November 2026 (0). No readable incident history (5). The limits page, re-read on 4 November 2026, gives 20 requests a minute until the organisation's first purchase, then 300 per console key and 60 for the managed Playground key, with token-per-minute and in-flight limits per organisation and key (15). Rate-limit 429s carry `retry-after` from 1 to 59 seconds and `metadata.retry_at`, the errors page gives a retry or no-retry rule for each error class, and the docs say a retry is a new billed request because there is no idempotency key. That is safe-retry guidance without keys on the billed call, the value this run settled for routers such as ramp-router (12, 15 before). The homepage says "Production-grade SLAs", but no SLA terms were found, and the only terms on the site say a stated response time is not a service level (0). The chat and messages surfaces carry no beta label. The Responses API is a preview for non-OpenAI models and Optimize is paused, neither of which is the main surface (10). 0 + 5 + 15 + 12 + 0 + 10 = 42.)
- Transparency & trust, LiteLLM +22: LiteLLM 63 (MIT for everything outside enterprise/, which has its own licence (25 of 30). The data security page (updated 6 November 2026) and security.md agree that a self-hosted gateway sends no data or telemetry to BerriAI, and the gateway stores prompts and spend in the operator's own Postgres. We found no terms of service or privacy policy on litellm.ai for its site, trial or Enterprise licence (20 of 30). A version support policy since 29 June 2026 (four stable minor lines), deprecated pages labelled in the docs, and release notes with breaking-change bullets (15 of 20). Usage telemetry, new in v1.107.0, is off by default, lists every field it can send and goes only to a table or endpoint the operator sets. A main-branch commit of 23 October 2026 made the Admin UI chat post a hashed user id to chat-telemetry.litellm.ai, and it was removed on 24 October before any tagged release contained it, so it isn't deducted. The start-up fetch of the price map from GitHub is documented with an opt-out (17 of 20).); RouterPlus 41 (Closed service with no terms of service found. The only terms on the site govern the capacity request form, under EVO HQ Inc (0 of 30). The data policy page is detailed, lists what is stored and why, and gives a 30-day period for request logs and each provider's retention flag. Its 4 November 2026 text, which logs request content by default, no longer agrees with the homepage FAQ; that contradiction is charged once as a misleading claim under negative events, not on this line. There is no privacy policy, no DPA and no retention period for account data such as email addresses (14 of 30, held). Model retirement by `deprecation_date` is documented with no notice period, and no dated deprecation notices were found (4 of 20). The docs name Clerk, Resend and an AWS bucket, and say RouterPlus's own GPUs run in the United States. The form's terms name Supabase, Cloudflare and Resend. No complete subprocessor list or gateway hosting location was found (8 of 20).)
- Payments & pricing, LiteLLM +20: LiteLLM 60 (Read with the self-hosted rule, since an agent uses the free gateway and Enterprise is a sales-led licence for the same software. No x402, MPP or L402 (0). MIT with no account and no card, so 20, 20 and 20 on the last three lines. Model calls cost what the operator's provider keys cost.); RouterPlus 40 (No machine payment protocol found in llms-full.txt. Calls draw on a prepaid balance (0). Per-token prices for every model are public in the docs catalogue and on the model pages with no login, re-read on 4 November 2026 (20). Signup adds no free credit, but inference through the caller's own provider keys carries no RouterPlus charge and needs no credit, the reading Cloudflare AI Gateway's dossier took for the same arrangement. We did not sign up to confirm that no card is asked for (20). A person signs up in the browser through Clerk with email verification, and the programmatic signup route was removed (0).)
- Security & auth, LiteLLM +13: LiteLLM 72 (Read with the tool checklist for self-hosted software. Virtual keys are hashed, revocable and blockable, with model, route, MCP server, budget, rate and expiry limits, and a `proxy_admin_viewer` read-only role exists. Rotation with a grace period is Enterprise only, so 25, less 10 because the docs pass a key as `?key=` on `/key/info` and on the Claude Code marketplace manifest (15 of 30). `allowed_routes`, MCP permissions by key and team, an approval queue for submitted MCP servers and stdio MCP servers off by default from 1.104.0 (15 of 20). Guardrails can run before a model call and on MCP tool results, and an OWASP LLM Top 10 page maps each risk to a control, but prompt-injection detectors such as Lakera need an Enterprise licence and all of it is off by default (12 of 15). Request and spend logs per key in the open-source build; audit logs of admin actions are Enterprise only (12 of 15). security.md with GitHub private reporting, a bug bounty from $500 to $3,000 for P0 and P1 reports, a security announcements list, SOC 2 Type II per the data security page, CodeQL, OSV and Scorecard workflows, and advisories published on GitHub. No security.txt, and reports without a video are closed unread (18 of 20).); RouterPlus 59 (Router, read on the model lines. `tm_vk_` keys are stored as SHA-256 hashes and revocable, each bound to a workspace and principal, with per-key RPM and monthly spend caps. Since 17 October 2026 the console also keeps an encrypted copy so an owner or admin can copy a key again, and an organisation can ask for copying to be turned off. Inference keys have no management rights. There are no permission scopes on a key and no SSO or SCIM (24 of 30). RouterPlus says it does not train on request logs and does not share them, and deletes them after 30 days. Most Claude and GPT routes are marked `prompt_logging: retained` with no ZDR, so retention and training upstream rest on each provider's API terms, while DeepInfra's open models, Perplexity, Cloudflare Workers AI, Fastino and RouterPlus's own models declare `none` (12 of 20, held). The data policy re-read on 4 November 2026 says requests and responses to non-dedicated endpoints are now logged by default for up to 30 days for debugging, with recognised keys removed. On 13 October it said content was kept only for hackathon accounts. Opting out takes a request to support, dedicated endpoints are excluded, and the `zdr` and `data_collection: deny` filters still remove every marketplace route, so they work only on the caller's own provider keys. Cloudflare AI Gateway, with default logging and a per-request header to switch it off, has 11 here (7 of 15, 10 before). `GET /v1/generation` lists every attempt behind a request with provider, tokens and cost, and the console has usage and logs (14 of 15). No security.txt (404 on both hosts on 4 November 2026), disclosure policy, bug bounty or certification found. The footer's Security link is an email to founders@evo-hq.com (2 of 20). 24 + 12 + 7 + 14 + 2 = 59.)