Redline vs self-hosted LiteLLM
LiteLLM Proxy is the build-it-yourself version of what Redline sells: an open-source, OpenAI-compatible gateway with virtual keys and budgets. If you want full control and no margin, self-hosting wins. What it costs you is the ops and the upstream keys.
Facts checked September 2026 against self-hosted LiteLLM’s own site, docs and policies.
| Redline | self-hosted LiteLLM | |
|---|---|---|
| What it is | Hosted gateway reselling the OpenRouter catalogue at upstream price plus 15%. | An open-source (MIT) OpenAI-compatible proxy you run yourself, in front of your own provider keys, with virtual keys and budgets. |
| Pricing | Pay as you go, upstream price + 15%, $10 minimum top-up, no subscription. | Free and open source. You pay your upstream providers directly at their list price, no gateway margin. Some enterprise features (SSO, audit logs) are paid. |
| OpenAI-compatible | Yes | Yes |
| Anthropic-compatible | Yes, /v1/messages (verified with Claude Code) | Yes, an Anthropic-format pass-through is available |
| Uncensored / abliterated | 7 uncensored, 0 abliterated today (resold from OpenRouter) | None by itself: you point it at whatever upstreams you configure, so the uncensored catalogue is on you to source |
| Prompt retention | No prompt or completion stored; model, tokens and cost kept 90 days; signed prompt-hash receipt | Your server, your rules: logging is configurable and off unless you wire a logging callback; nothing leaves your control except to the upstreams you choose |
| Per-key spend caps | Lifetime and monthly per-key caps, enforced by reserving the worst case and clamping max_tokens | Per-virtual-key max_budget with a budget_duration reset window, plus rate limits; worst-case budget reservation is on by default |
Where self-hosted LiteLLM is the better choice
- No margin and full privacy: it is free, and prompts go only to the upstreams you configure, from a server you control. Nothing passes through a third-party gateway.
- Total control and real budgets: your own key policies, routing, logging and model list, with virtual-key budgets that reserve the worst case before the call, on by default. Its spend controls are as capable as Redline’s or more.
Where Redline is different
- You run it: hosting, upgrades, uptime, secrets and the upstream provider contracts are all yours, and you must source uncensored models yourself. Redline is that work already done, with the uncensored catalogue included.
- Both reserve the worst-case cost, but Redline shrinks max_tokens to fit the cap instead of rejecting the request, does it as a hosted service, and signs a prompt-hash receipt on every call. LiteLLM gives you the mechanism; Redline gives you the running system.
Worth knowing LiteLLM is also how you would consume Redline in a larger stack: point the LiteLLM Proxy at Redline as one OpenAI-compatible upstream. See the LiteLLM integration guide.