Alternative

A LiteLLM alternative, compared honestly

LiteLLM is self-hosted and open source; Vigil is a hosted service and is not. If you are leaving LiteLLM because you do not want to run a gateway, read on; if you need to keep your traffic in your own cloud, Vigil is not the answer. If you are looking at alternatives to LiteLLM, this page puts Vigil beside it without flattering either. Every LiteLLM fact was read on LiteLLM's own pages on 2026-10-09, its pricing and status again on 2026-11-16, and links to its source. Vigil does less than LiteLLM in several places, listed plainly below; what it does differently is a proxy that creates prompt-cache hits and prices every call with its provenance shown.

What LiteLLM is, and what Vigil is

LiteLLM, in its own words: “The AI Gateway for platform teams. One API for 100+ LLMs, with spend tracking, auth, and guardrails.”litellm.ai. Both: a Python SDK in your process, or a self-hosted proxy your OpenAI client points at (base_url http://0.0.0.0:4000).

Vigil is a proxy for AI API calls. Change one base URL, add one header, and every call is logged with its cost, tokens, latency, errors and agent, then forwarded unchanged unless you switch on an optimisation. Prompt caching, where the provider supports it, never changes answers. History trimming and model routing can change answers: both are opt-in, run in Shadow first, and stop automatically if errors, cut-off answers or failed answers rise. It stores no prompt text and caches no responses.

  • LiteLLM says: enterprise pricing is "never per token".litellm.ai
  • LiteLLM says: "Free forever · self-hosted"; no hosted cloud tier appears on the pricing page.litellm.ai

Feature by feature

The LiteLLM column was read on LiteLLM's own pages on 2026-10-09, and the cells marked “re-read” again on 2026-11-16; each cell links to the page. “Not stated” means the pages read do not mention it, which is not the same as “no”. The Vigil column is read from Vigil's code and docs.

FeatureLiteLLMVigil
IntegrationSDK (from litellm import completion) or proxy: run litellm, point the OpenAI SDK at it.github.comProxy. Change the base URL and add the X-Vigil-Key header; no SDK.
Open sourceMIT, except the enterprise/ directory under the BerriAI Enterprise license.raw.githubusercontent.comNo. Vigil is not open source.
HostingSelf-host only: "It runs in your cloud, so prompts and responses never leave your environment."docs.litellm.aiCloud only: a Cloudflare Worker in front of the provider, a dashboard on Vercel, data in Supabase (Frankfurt, EU).
Cost per callYes: an x-litellm-response-cost header, a spend-logs table, spend by key, user and team.docs.litellm.aiYes: cost, tokens, latency, status and agent on every call, from a rate registry where every rate carries its source, date and provenance; a dash where no rate is published.
ProvidersThe homepage says "100+ LLMs", "140+ LLM providers" and "1,800+ models" in different places.litellm.ai17 providers routed by segment.
Prompt cachingPasses your markers through and translates them for Bedrock and Vertex; can also inject cache_control at configured points ("automatically cache system messages").docs.litellm.aiCreates cache hits: Anthropic, Google Vertex, Mistral get cache markers placed by Vigil when optimisation is on; AWS Bedrock when the request carries an API key rather than a SigV4 signature. On other providers Vigil records the provider’s own caching.
Response cachingYes: Redis, semantic (Redis, Valkey, Qdrant), S3, GCS, local and disk back ends.docs.litellm.aiNo. Vigil does not cache responses.
Routing and fallbacksRouting strategies (shuffle, usage, latency, least-busy, cost), fallbacks, retries with backoff, cooldowns.docs.litellm.aiModel routing is in beta: Sends a call to a cheaper model from the same provider — one tier down — when its answer is closed-form and checkable (a label, JSON or other data, a number, code to a named function or test, or a request with tools), its prompt is at most about 16,000 tokens, its opening's size and tools are in a band the agent's routing level covers and the cheaper model can take the request. Open-ended work without tools — writing, summaries, reviews, explanations, chat — stays on the original model, and once a call of a conversation stays there, the later ones do too; a later call the cheaper model can't take stays on the original model. Routing can change answers, so it runs in Shadow first. No provider fallbacks or load balancing.
Prompt managementThrough integrations (.prompt files, Langfuse, Humanloop); no versioning of its own.docs.litellm.aiNo prompt management or versioning.
EvalsNot stated on the pages read.No evaluations. A score can be sent for a call through the feedback endpoint.
TracingExports to Langfuse, Arize Phoenix, LangSmith and OpenTelemetry; no trace UI of its own claimed.litellm.aiOne record per call. No spans or traces.
AlertsBudget, slow and failed calls, model outage; Slack, Discord, Microsoft Teams. Region-outage alerting is an enterprise feature.docs.litellm.aiCost spikes, failures and findings are flagged in the dashboard. Nothing is sent by email, Slack or push.
Prompt injection and PIIThrough guardrail integrations: "PII masking and prompt-injection guardrails (Presidio, Lakera, and more)"; several require an enterprise license.docs.litellm.aiFlags likely prompt injections and personal data in prompts, on every plan. Nothing is blocked or redacted.
Budgets and rate limitsmax_budget and budget_duration per key, user and team; requests and tokens per minute. Per-model key budgets need an enterprise license.docs.litellm.aiNo spend caps or rate limits on your provider traffic. Optimisation can be switched off per agent.
SeatsOrganisations, teams and user roles; organisation and team admin roles are premium features.docs.litellm.aiSeats per plan: 1 on Free, 3 on Plus, unlimited from Pro. Teammates are invited; there are no role tiers.
Compliance"LiteLLM is SOC 2 Type II audited"; ISO 27001 on the enterprise page.docs.litellm.aiNo SOC 2 or ISO 27001 report. A DPA is published.
Data residencySelf-hosted in your own cloud or air-gapped; no vendor region.docs.litellm.aiAccount and telemetry stored in the EU (Supabase, Frankfurt). The proxy runs on Cloudflare’s edge. No prompt text or responses are stored.

Where LiteLLM is stronger

  • Open source under MIT, self-hosted in your own cloud, so prompts never leave it.
  • The widest routing: strategies, fallbacks, retries, cooldowns, and a response cache with many back ends.
  • Budgets and rate limits per key, user and team, and alerts to Slack, Discord and Teams.
  • Prompt-cache injection at configured points, plus translation of markers for Bedrock and Vertex.

Where Vigil differs

  • It creates prompt-cache hits rather than reporting them, on the providers whose caching lets a proxy place markers, and measures what caching would have saved on the others.
  • Every rate it prices with carries its source, its retrieval date and a provenance label, and a cost it cannot stand behind is a dash, not a number.
  • Monitoring is not gated by plan: every agent, every provider, on Free. Paid plans switch optimisation on.
  • It does less: no response cache, no evals, no prompt management, no traces, no alerts outside the dashboard.

Pricing, side by side

LiteLLMlitellm.ai read 2026-11-16

  • Open Source $0: self-hosted, no caps stated: 100+ providers, virtual keys, teams, spend tracking, budgets, fallbacks
  • Enterprise Annual, by usage: "sized to your annual gateway request capacity"; SSO, SCIM, audit logs, 24/7 support with SLAs; no figure published

Tiers re-read 2026-11-16: unchanged.

Vigil vigil.tools/pricing

  • Free $0: every agent monitored; 10,000 logged calls a month, 7 days of history; every optimisation On until $30 saved, once ever, then a 30-day grace, then Shadow only
  • Plus $29/mo: every optimisation On up to $100 saved a billing month, then a 30-day grace, then Shadow; 500,000 logged calls, 30 days
  • Pro $99/mo: every optimisation On up to $500 saved a billing month, then a 30-day grace, then Shadow; 2,000,000 logged calls, 90 days
  • Supreme $299/mo: every optimisation On up to $2,000 saved a billing month, then a 30-day grace, then Shadow; Unlimited logged calls, 365 days
  • Enterprise Custom: by contract

Monthly, excl. VAT. Monitoring is free on every plan; what a paid plan buys is a higher limit on the money Vigil saves you per billing period before optimisations go to Shadow (after a 30-day grace).

Moving from LiteLLM: what changes and what you keep

Vigil is a base-URL change and one header, so there is nothing to uninstall and nothing to instrument: the SDK you already use keeps its code. Your provider keys stay where they are. If you depend on LiteLLM for a response cache, routing, prompt management or traces, Vigil does not replace those; the table above says which. Vigil is not open source and runs only as a hosted service, so a self-hosting requirement rules it out.

What you gain is a proxy that can place prompt-cache markers for you on the providers that allow it, a cost on every call with its provenance shown, and monitoring that is free on every plan. Start on Free and compare your own numbers before switching anything off.

Questions

Is LiteLLM free?
The open-source gateway is: its pricing page says "Free forever · self-hosted" and lists no hosted tier, and Enterprise is priced annually, "sized to your annual gateway request capacity", "never per token" (litellm.ai/pricing, read 2026-10-09, tiers re-read 2026-11-16). You run it yourself, so its running cost is your own infrastructure.
Does LiteLLM track cost per call?
Yes: an x-litellm-response-cost header on each response, a spend-logs table, and spend by key, user and team (docs.litellm.ai, read 2026-10-09). What Vigil adds is not cost tracking itself but the per-agent view across the providers you call directly, with the source of every price shown beside it.
Does Vigil replace LiteLLM?
Only for a team that wants the cost view without running a gateway. Vigil is hosted and closed; LiteLLM is MIT-licensed and runs in your own cloud. Its response cache, routing strategies, fallbacks, per-key budgets and guardrail integrations have no Vigil equivalent, and the table above says so row by row. If traffic must stay in your cloud, LiteLLM is the one that does that.

Also: Helicone alternative · Portkey alternative · Langfuse alternative · OpenRouter alternative