Every source behind the read

59 sources in Teams and technical leaders, with product documentation Showing all 137 sources

1. No opinion stated

   PsychologicalFlan877, Reddit commenter

   Comment on: LiteLLM Compromised again - 1.107.0. PyPI Installs a Credential Stealer and BackdoorReddit comment, r/devops

   The team holds every new package version for 72 hours in CI, with a fast lane only for CVE fixes, a soak window that would have caught both LiteLLM compromises, and hash-pins its lockfile because a republished tag slips past version pins.

   Published Oct 22, 2026self-described: A team whose CI gates new package versions on release age

   Not counted

   Its author's ties to the vendor have not been checked. Kept in the record; it takes part in no figure.

   Published on

   Developer Communities

   Who

   Product or platform team

   Evidence

   Reported

   Applies to

   Current

   Observed on

   Python dependencies including LiteLLM, installed through uv with hash pins

2. No opinion stated

   PerfectStephen, Reddit commenter

   Comment on: LLM gateway - pass through Vs unifiedReddit comment, r/mlops

   The team spent two days debugging wrong outputs before finding that LiteLLM silently stripped model-specific parameters, and now prefers a pass-through gateway with a thin governance layer.

   Published Oct 11, 2026self-described: A team running a unified-schema gateway in front of several model providers

   Not counted

   Its author's ties to the vendor have not been checked. Kept in the record; it takes part in no figure.

   Published on

   Developer Communities

   Who

   Product or platform team

   Evidence

   Reported

   Applies to

   Current

   Observed on

   LiteLLM as a unified-schema gateway

3. No opinion stated

   DevWorkflowBuilder, Reddit commenter

   Comment on: How do you set LLM budgets per team?Reddit comment, r/devops

   After one weekend script ate half the month's budget, put LiteLLM in front with a US$40-a-day hard stop on each team key and alerts at 70%, so the author is paged only when a team wants its ceiling raised.

   Published Sep 29, 2026self-described: A team whose weekend test script ate half a month's model budget

   Not counted

   Its author's ties to the vendor have not been checked. Kept in the record; it takes part in no figure.

   Published on

   Developer Communities

   Who

   Small product team

   Evidence

   Reported

   Applies to

   Current

   Observed on

   LiteLLM with per-team keys and daily hard stops

4. Positive

   mpyne, On a team that adopted LiteLLM (as stated)

   Comment on: Litelm: LiteLLM Without the BloatHacker News comment

   Their organization chose LiteLLM after internal discussion; its added latency has not been noticeable to users and it has behaved as the team expected.

   Published Sep 12, 2026self-described: Organization rolling out AI with LiteLLM as its gateway

   Counts toward

   • Overall signal
   • Performance at Scale: Discussed without concern
   • One gateway for the organization
   • Is LiteLLM ready to be the production gateway in front of every model call?: Runs it in production
   • When practitioners weigh LiteLLM against another gateway, which do they keep?: Chose or kept LiteLLM

   Published on

   Developer Communities

   Who

   Product or platform team

   Evidence

   Reported

   Applies to

   Current

   Observed on

   LiteLLM gateway

5. Mixed

   phenethol, LLM infrastructure intern at the Ruđer Bošković Institute

   litellm-ops: operations toolkit and proxy-versus-direct latency benchmarkIndependent benchmark, GitHub repository

   Built against the Ruđer Bošković Institute's LiteLLM proxy, the toolkit's benchmark finds the proxy adds about 30 ms and is no bottleneck up to 8 concurrent requests. In places, the admin UI does not match what the API does.

   Published Sep 12, 2026self-described: The Ruđer Bošković Institute's self-hosted LiteLLM proxy, with users, budgets, and rate limits

   Counts toward

   • Overall signal
   • Performance at Scale: Discussed without concern
   • Operational Burden: Raised as a concern
   • One gateway for the organization
   • Is LiteLLM ready to be the production gateway in front of every model call?: Runs it in production

   Published on

   Engineering Blogs & Reviews

   Who

   Organization-wide

   Evidence

   Measured

   Applies to

   Current

6. Positive

   9dev, Hacker News commenter

   Comment on: Litelm: LiteLLM Without the BloatHacker News comment

   Deploying LiteLLM in their platform for its reliable per-customer token spend tracking across services, the features slimmer forks remove.

   Published Sep 11, 2026self-described: Platform tracking token spend per customer

   Counts toward

   • Overall signal
   • Virtual Keys, Budgets & Spend Tracking: Positive

   Published on

   Developer Communities

   Who

   Small product team

   Evidence

   Reported

   Applies to

   Current

7. Mixed

   Bartosz Ocytko, Executive Principal Engineer, Zalando

   Agentic Engineering at Zalando: a snapshotEngineering blog post, Zalando Engineering Blog

   Zalando likes LiteLLM for its extensibility, using call hooks for anonymized cost tracking and client version checks. Stability and memory leaks force a restart every 20,000 requests, and the proxy serves 2,000 monthly users on six small pods.

   "…our ML platform team deployed in January 2024 a LiteLLM based API proxy with access to models from different providers (now: OpenAI, AWS Bedrock, and Google Vertex)."

   Published Aug 14, 2026Zalando's company-wide LLM proxy, run by its ML platform team since January 2024

   Counts toward

   • Overall signal
   • Virtual Keys, Budgets & Spend Tracking: Positive
   • Self-Hosted Control: Positive
   • Stability & Code Quality: Raised as a concern
   • One gateway for the organization
   • Is LiteLLM ready to be the production gateway in front of every model call?: Runs it in production

   Published on

   Engineering Blogs & Reviews

   Who

   Technical leadership

   Evidence

   Reported

   Applies to

   Current

   Observed on

   LiteLLM proxy in front of OpenAI, AWS Bedrock, and Google Vertex for about 2,000 monthly users

8. Positive

   827a, Engineer at a startup (as stated)

   Comment on: Managing AI Coding Costs at ScaleHacker News comment

   Their startup routes US$150,000 of Azure credits through a LiteLLM gateway and OpenCode, with engineers spending US$20 to US$200 a day on tokens.

   Published Aug 8, 2026self-described: Startup engineering team using Azure credits

   Counts toward

   • Overall signal
   • One gateway for the organization
   • Coding tools go through the gateway

   Published on

   Developer Communities

   Who

   Small product team

   Evidence

   Reported

   Applies to

   Current

   Observed on

   LiteLLM gateway with OpenCode on Azure

9. Mixed

   Arseny Zinchenko, DevOps engineer and author of the RTFM blog

   LiteLLM: OpenRouter Integration and Fallbacks ConfigurationEngineering blog post, RTFM

   Added OpenRouter behind the team's existing LiteLLM gateway so services changed nothing. OpenRouter returned 429 errors in test production, so the team configured fallbacks to OpenAI in LiteLLM, keeping failover out of client code.

   Published Jul 31, 2026self-described: A company LiteLLM gateway that already handles requests from all of the team's services, with OpenRouter added behind it

   Counts toward

   • Overall signal
   • Routing, Fallbacks & Load Balancing: Positive
   • One gateway for the organization
   • Stay provider-neutral

   Published on

   Engineering Blogs & Reviews

   Who

   Product or platform team

   Evidence

   Reported

   Applies to

   Current

   Observed on

   LiteLLM in front of OpenRouter, with direct OpenAI fallbacks

10. Negative

    yryzhan-vitech, GitHub user running the Noma guardrail on a LiteLLM proxy

    [Bug]: Noma v2 guardrail ignores streaming_end_of_stream_only and streaming_sampling_rateGitHub issue, BerriAI/litellm

    Two streaming settings for the Noma guardrail had no effect: post-call scans ran per chunk at the hard-coded default sampling rate of 5 whatever the config said, with no error or warning, so the misconfiguration stayed invisible.

    "Setting either in config.yaml has no effect: streaming post-call scans always run per chunk at the hard-coded default sampling rate of 5. There is no error and no warning, so the misconfiguration is invisible."

    Published Jul 28, 2026self-described: A LiteLLM proxy with the Noma v2 guardrail scanning streamed responses

    Counts toward

    • Overall signal
    • Stability & Code Quality: Raised as a concern

    Published on

    Developer Communities

    Who

    Product or platform team

    Evidence

    Reported

    Applies to

    Current

    Observed on

    LiteLLM proxy with the Noma v2 guardrail

11. Positive

    lbreakjai, At a company that rolled out LiteLLM (as stated)

    Comment on: Kimi K2.7 Code is generally available in GitHub CopilotHacker News comment

    Their company canceled everyone's individual AI plans and rolled LiteLLM out internally instead.

    Published Jul 2, 2026self-described: Company-wide rollout replacing per-seat AI plans

    Counts toward

    • Overall signal
    • Virtual Keys, Budgets & Spend Tracking: Positive
    • One gateway for the organization
    • When practitioners weigh LiteLLM against another gateway, which do they keep?: Chose or kept LiteLLM

    Published on

    Developer Communities

    Who

    Technical leadership

    Evidence

    Reported

    Applies to

    Current

12. No opinion stated

    Own_Anywhere9206, Reddit commenter

    Comment on: TrueFoundry vs LiteLLM vs Portkey for Internal LLM Access?Reddit comment, r/devops

    Ran LiteLLM internally for a few months: setup was fine, but per-team usage tracking got messy past a handful of teams and the spend views felt bolted on, so the team fell back on hard spend limits per key.

    Published Jun 18, 2026self-described: A company that ran LiteLLM internally for several teams for a few months

    Not counted

    Its author's ties to the vendor have not been checked. Kept in the record; it takes part in no figure.

    Published on

    Developer Communities

    Who

    Product or platform team

    Evidence

    Reported

    Applies to

    Current

    Observed on

    LiteLLM virtual keys and spend views

13. No opinion stated

    Jony_Dony, Reddit commenter

    Comment on: TrueFoundry vs LiteLLM vs Portkey for Internal LLM Access?Reddit comment, r/devops

    Virtual keys work for a handful of teams, but enforcing different model access per team, such as keeping production and development apart, breaks down; Portkey's config-based routing handles it more cleanly, though authorization still has to be layered on top.

    Published Jun 18, 2026self-described: Teams enforcing different model access per environment through one gateway

    Not counted

    Its author's ties to the vendor have not been checked. Kept in the record; it takes part in no figure.

    Published on

    Developer Communities

    Who

    Product or platform team

    Evidence

    Reported

    Applies to

    Current

    Observed on

    LiteLLM virtual keys at multi-team scale

14. No opinion stated

    theexplorer1997, Reddit commenter

    Comment on: TrueFoundry vs LiteLLM vs Portkey for Internal LLM Access?Reddit comment, r/devops

    Ran LiteLLM for internal playgrounds and early trials, where it works well enough; the pain arrived later, when people asked who burned which budget and clean team keys mattered.

    Published Jun 18, 2026self-described: An internal playground and trial setup on LiteLLM

    Not counted

    Its author's ties to the vendor have not been checked. Kept in the record; it takes part in no figure.

    Published on

    Developer Communities

    Who

    Product or platform team

    Evidence

    Reported

    Applies to

    Current

    Observed on

    LiteLLM proxy for internal playgrounds

15. Mixed

    Jack Wildman, Senior Software Engineer, FutureSearch

    LiteLLM made us accidentally make our product free for a weekEngineering blog post, FutureSearch blog

    A LiteLLM upgrade began stripping caller tags without an error, so FutureSearch billed no usage for 6.5 days. It calls the default-on change a footgun, added alerts, and stayed on LiteLLM at v1.86.4.

    "A routine LiteLLM version bump turned off our usage billing for six and a half days. We had many alerts for runaway spend, but not for spend dropping to zero."

    Published Jun 10, 2026FutureSearch's research-agent platform, which bills users from LiteLLM spend logs

    Counts toward

    • Overall signal
    • Virtual Keys, Budgets & Spend Tracking: Mixed or negative
    • Stability & Code Quality: Raised as a concern
    • When practitioners weigh LiteLLM against another gateway, which do they keep?: Chose or kept LiteLLM

    Published on

    Engineering Blogs & Reviews

    Who

    Product or platform team

    Evidence

    Measured

    Applies to

    Current

    Observed on

    LiteLLM Proxy request_tags feeding usage billing, v1.80 to v1.86

16. Positive

    kgeist, Hacker News commenter

    Comment on: LLMCap - A proxy that hard-stops LLM API calls when you hit a dollar capHacker News comment

    Their team self-hosts LiteLLM for free and sets budgets per day or week.

    Published May 19, 2026self-described: Self-hosted gateway at work

    Counts toward

    • Overall signal
    • Virtual Keys, Budgets & Spend Tracking: Positive
    • Self-Hosted Control: Positive

    Published on

    Developer Communities

    Who

    Small product team

    Evidence

    Reported

    Applies to

    Current

    Observed on

    Self-hosted LiteLLM Proxy

17. Positive

    intothemild, Hacker News commenter

    Comment on: AI subscriptions are a ticking time bomb for enterpriseHacker News comment

    Put self-hosted Qwen, Gemma, and DeepSeek behind LiteLLM to watch token use and bring inference cost in-house, and the company is rolling it out more widely.

    Published May 17, 2026self-described: Company pilot: self-hosted Qwen, Gemma, and DeepSeek behind LiteLLM

    Counts toward

    • Overall signal
    • Virtual Keys, Budgets & Spend Tracking: Positive
    • Self-Hosted Control: Positive
    • One gateway for the organization

    Published on

    Developer Communities

    Who

    Small product team

    Evidence

    Reported

    Applies to

    Current

18. Mixed

    Sanady, GitHub user at a firm running LiteLLM on Kubernetes

    Heavy RAM usage over some timeGitHub issue

    A firm running LiteLLM on two 4 GB Kubernetes pods sees memory fill within a day or two until the pods crash, after earlier fixes for the same leak.

    Published May 14, 2026self-described: Two-pod Kubernetes deployment with Redis caching and 4 GB pods

    Counts toward, pending a recheck

    • Overall signal
    • Stability & Code Quality: Raised as a concern
    • Performance at Scale: Raised as a concern

    Published on

    Developer Communities

    Who

    Product or platform team

    Evidence

    Reported

    Applies to

    Needs a recheck

19. Mixed

    lin0703, GitHub user

    [Bug]: Budget enforcement bypassed in v1.82.3 for key/user max_budget despite spend exceeding max_budgetGitHub issue

    On a fresh v1.82.3 deployment, key and user max_budget were stored and spend tracked, but requests were not blocked once spend passed the budget.

    Published Apr 28, 2026self-described: Fresh v1.82.3 deployment compared with v1.81.0

    Counts toward

    • Overall signal
    • Virtual Keys, Budgets & Spend Tracking: Mixed or negative
    • Stability & Code Quality: Raised as a concern

    Published on

    Developer Communities

    Who

    Small product team

    Evidence

    Reported

    Applies to

    Current

    Observed on

    v1.82.3

20. Mixed

    escon1004, GitHub user

    [Feature]: unlimited SSO Login with Standard PlanGitHub issue

    Their company is considering LiteLLM, but the 5-user SSO limit without a license blocks a realistic multi-team evaluation and pushes teams to OAuth2 Proxy workarounds.

    Published Apr 15, 2026self-described: Company evaluating LiteLLM

    Counts toward

    • Overall signal
    • Enterprise-Gated Features: Raised as a concern

    Published on

    Developer Communities

    Who

    Small product team

    Evidence

    Reported

    Applies to

    Current

21. Positive

    Thoughtworks delivery teams, Technology Radar

    LiteLLM (Technology Radar, Languages & Frameworks)Technology Radar entry, Thoughtworks

    Thoughtworks teams increasingly adopt LiteLLM as a sensible default gateway for retries, failover, load balancing, and budgets. Provider-specific features still need provider-specific parameters, and drop_params silently discards unsupported ones.

    Published Apr 15, 2026self-described: Thoughtworks client teams that run LiteLLM as the AI gateway for enterprise applications

    Counts toward

    • Overall signal
    • One API Across Providers: Mixed or negative
    • Virtual Keys, Budgets & Spend Tracking: Positive
    • Routing, Fallbacks & Load Balancing: Positive
    • One gateway for the organization
    • Is LiteLLM ready to be the production gateway in front of every model call?: Runs it in production

    Published on

    Engineering Blogs & Reviews

    Who

    Product or platform team

    Evidence

    Reported

    Applies to

    Current

    Observed on

    LiteLLM gateway, kept in the Trial ring since October 2024

22. Mixed

    sacrelege, Running a small inference provider (as stated)

    Comment on: N-Day-Bench - Can LLMs find real vulnerabilities in real codebases?Hacker News comment

    Their new inference service uses LiteLLM as the load balancer in front of its GPU servers, which they are replacing with a custom Rust implementation.

    Published Apr 14, 2026self-described: Small private datacenter serving inference customers

    Counts toward

    • Overall signal
    • Routing, Fallbacks & Load Balancing: Positive
    • Some replace it or build their own

    Published on

    Developer Communities

    Who

    Small product team

    Evidence

    Reported

    Applies to

    Current

    Observed on

    LiteLLM as load balancer

23. Mixed

    ruettiger, GitHub user running LiteLLM on GKE

    Sync convert_url_to_base64() blocks asyncio event loop, causing pod health check failures and mass restartsGitHub issue

    In a 16-replica GKE production deployment, one unreachable image URL blocked LiteLLM's event loop for minutes, failed health checks, and left only 1 pod available.

    Published Mar 30, 2026self-described: GKE Autopilot production deployment with 16 replicas

    Counts toward, pending a recheck

    • Overall signal
    • Stability & Code Quality: Raised as a concern
    • Performance at Scale: Raised as a concern

    Published on

    Developer Communities

    Who

    Product or platform team

    Evidence

    Measured

    Applies to

    Needs a recheck

24. Mixed

    Matteo Dora and David Berenstein, Giskard

    LiteLLM supply chain compromise: what happened, impact on Giskard, and lessons learnedEngineering blog post, Giskard blog

    Giskard's own services were safe because LiteLLM was pinned, but its open-source packages could pull in the bad releases. It traces the compromise to LiteLLM's CI pipeline, which gave Trivy every secret and published with a long-lived PyPI token.

    Published Mar 25, 2026self-described: Giskard, AI red-teaming company whose services and open-source packages depend on LiteLLM

    Counts toward

    • Overall signal
    • Security & Supply Chain: Raised as a concern

    Published on

    Engineering Blogs & Reviews

    Who

    Product or platform team

    Evidence

    Reported

    Applies to

    Current

    Observed on

    LiteLLM pinned in Giskard services; transitive dependency of giskard[llm]

25. Negative

    Daniel Hnyk, FutureSearch

    LiteLLM Hack: Were You One of the 47,000?Engineering blog post, FutureSearch blog

    FutureSearch counted 46,996 downloads of the two compromised LiteLLM releases in the 46 minutes they were live and found 88% of the 2,337 dependent packages allowed them.

    Published Mar 25, 2026Analysis of PyPI download logs and the 2,337 packages that depend on LiteLLM

    Counts toward

    • Overall signal
    • Security & Supply Chain: Raised as a concern

    Published on

    Engineering Blogs & Reviews

    Who

    Product or platform team

    Evidence

    Measured

    Applies to

    Current

26. Negative

    santiagobasulto, Leading a team of developers (as stated)

    Comment on: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromisedHacker News comment

    Advised a team of less senior developers against LiteLLM and LangChain, citing supply-chain and vulnerability risk, and to call provider APIs directly.

    Published Mar 24, 2026self-described: Team of less senior developers

    Counts toward

    • Overall signal
    • Security & Supply Chain: Raised as a concern
    • Some replace it or build their own
    • When practitioners weigh LiteLLM against another gateway, which do they keep?: Chose another tool

    Published on

    Developer Communities

    Who

    Technical leadership

    Evidence

    Reported

    Applies to

    Current

27. Mixed

    kingreflex, Hacker News commenter

    Comment on: Malicious litellm_init.pth in litellm 1.82.8 PyPI package - credential stealerHacker News comment

    During the March 2026 PyPI compromise, asked whether the team's Helm-deployed LiteLLM images on pinned stable tags were affected.

    Published Mar 24, 2026self-described: Team running LiteLLM Proxy from Helm charts

    Counts toward

    • Overall signal
    • Self-Hosted Control: Positive
    • Security & Supply Chain: Discussed without concern

    Published on

    Developer Communities

    Who

    Small product team

    Evidence

    Reported

    Applies to

    Current

    Observed on

    Helm chart, main-v1.81.12-stable.2

28. Mixed

    ddp26, Leading the FutureSearch team (as stated)

    Comment on: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromisedHacker News comment

    Their FutureSearch team was first hit by the compromised release: uvx pulled the unpinned latest LiteLLM and Cursor started the local MCP server automatically.

    Published Mar 24, 2026self-described: FutureSearch, research product using LiteLLM

    Counts toward

    • Overall signal
    • Security & Supply Chain: Raised as a concern

    Published on

    Developer Communities

    Who

    Technical leadership

    Evidence

    Reported

    Applies to

    Current

    Observed on

    Transitive dependency of an MCP server

29. Mixed

    Callum McMahon, Research Scientist at FutureSearch

    litellm 1.82.8 Supply Chain Attack on PyPI (March 2026)Engineering blog post, FutureSearch blog

    FutureSearch, which uses LiteLLM to balance quality, speed and cost across providers, caught the 1.82.8 credential stealer when an MCP plugin pulled it in; damage was minimal.

    "We discovered it when the package was pulled in as a transitive dependency by an MCP plugin running inside Cursor."

    Published Mar 24, 2026self-described: FutureSearch, research product that uses LiteLLM across model providers

    Counts toward

    • Overall signal
    • One API Across Providers: Positive
    • Security & Supply Chain: Raised as a concern
    • Stay provider-neutral

    Published on

    Engineering Blogs & Reviews

    Who

    Product or platform team

    Evidence

    Reported

    Applies to

    Current

    Observed on

    Python SDK, transitive dependency of an MCP server

30. Mixed

    Nimrod Lahav, Comet engineering (author of Comet's incident write-up)

    LiteLLM Supply Chain Attack: What Happened, Who's Affected, and What You Should Do Right NowEngineering blog post, Comet blog

    Comet audited 50+ repositories and every developer machine after the compromise, found two CI workflows exposed with test credentials only, and production safe on pinned images.

    "We identified two CI workflows that installed compromised versions during the exposure window. In both cases, the exposed secrets were limited to CI test credentials."

    Published Mar 24, 2026self-described: Comet, whose Opik product depends on LiteLLM; audit of 50+ repositories and every developer machine

    Not counted

    Comet's Opik takes LiteLLM as a direct dependency, as the post's own table shows. Kept in the record; it takes part in no figure.

    Published on

    Engineering Blogs & Reviews

    Who

    Product or platform team

    Evidence

    Reported

    Applies to

    Current

    Observed on

    Python SDK dependency of Opik

31. Negative

    omrimaya, Hacker News commenter

    Comment on: Show HN: key-carousel - Key rotation for LLM agentsHacker News comment

    Their team ran LiteLLM for a week, then removed it because the operational surface was not worth it for what amounted to a retry loop with state.

    Published Mar 7, 2026self-described: Team that built key rotation for LLM agents

    Counts toward

    • Overall signal
    • Operational Burden: Raised as a concern
    • Some replace it or build their own
    • When practitioners weigh LiteLLM against another gateway, which do they keep?: Chose another tool

    Published on

    Developer Communities

    Who

    Small product team

    Evidence

    Reported

    Applies to

    Current

32. No opinion stated

    Dennis Henry, Productivity Architect, Okta

    How Okta Deploys and Secures AI for Its EmployeesEngineering blog post, Okta blog

    Okta runs a LiteLLM-powered gateway in its private cloud as the single entry point for every AI call, from code-generation APIs to its internal web UI, and logs every interaction to its security operations team for auditing.

    "Our gateway is a resilient, scalable service powered by LiteLLM, deployed within Okta's secure private cloud. It functions as a secure proxy and a single point of entry for every AI interaction, from a developer calling a code-generation API to an employee using our internal webUI."

    Published Feb 26, 2026self-described: Okta's company-wide AI gateway, run in its private cloud for developers calling model APIs and employees using an internal web UI

    Not counted

    Its author's ties to the vendor have not been checked. Kept in the record; it takes part in no figure.

    Published on

    Engineering Blogs & Reviews

    Who

    Organization-wide

    Evidence

    Reported

    Applies to

    Current

    Observed on

    LiteLLM gateway in Okta's private cloud, logging every interaction to its Defensive Cyber Operations team

33. Mixed

    jklinkenberg, GitHub user

    [Performance] LiteLLM Overhead and Performance in ProductionGitHub issue

    Benchmarked GPT-OSS-120B: about 16 requests per second direct versus about 9 requests per second through the LiteLLM proxy at 500 concurrent requests, even with spend logs disabled.

    Published Feb 12, 2026self-described: Proxy in front of self-hosted GPU models, 4 vCPU and 8 GB VM

    Counts toward

    • Overall signal
    • Performance at Scale: Raised as a concern

    Published on

    Developer Communities

    Who

    Small product team

    Evidence

    Measured

    Applies to

    Current

    Observed on

    v1.80.15 with vLLM

34. Mixed

    phanisarman, GitHub user

    [Bug]: Significant performance regression after upgrading from 1.80.5 to 1.81.x (UI + API slowness)GitHub issue

    Upgrading from 1.80.5 to 1.81.x made the UI and API consistently slower on the same infrastructure for a 50-user, 200-model gateway.

    Published Jan 28, 2026self-described: Gateway for 50 internal users and 200 models at about 10 RPS, with Postgres and Langfuse OTel callbacks

    Counts toward

    • Overall signal
    • Stability & Code Quality: Raised as a concern
    • Performance at Scale: Raised as a concern

    Published on

    Developer Communities

    Who

    Small product team

    Evidence

    Reported

    Applies to

    Current

    Observed on

    v1.80.5 to v1.81.3

35. Mixed

    Alina Dallmann, Speaker at PyData Berlin 2025

    One API to Rule Them All? LiteLLM in ProductionConference talk, PyData Berlin 2025 (PyData YouTube channel)

    Ran LiteLLM's proxy for a university chatbot with cost tracking, budgets and load balancing, but hit custom-budget limits, slow new-model support and bugs in new features.

    "…deploying the the proxy server we already get an admin user interface delivered as well. Um this is a screenshot um of one example of it. Um here we can do most of the process I just described earlier to assign budgets…"

    Published Nov 23, 2025self-described: Privacy-preserving university RAG chatbot for students and employees

    Counts toward

    • Overall signal
    • Virtual Keys, Budgets & Spend Tracking: Positive
    • Routing, Fallbacks & Load Balancing: Positive
    • Provider & Model Coverage: Mixed or negative
    • Stability & Code Quality: Raised as a concern
    • Is LiteLLM ready to be the production gateway in front of every model call?: Runs it in production

    Published on

    Podcasts, Talks & Videos

    Who

    Product or platform team

    Evidence

    Reported

    Applies to

    Still applicable

    Observed on

    LiteLLM Proxy with PostgreSQL

36. Negative

    sothatsit, Hacker News commenter

    Comment on: Control LLM Spend and Access with any-LLM-gatewayHacker News comment

    Their team calls LiteLLM a dumpster fire of enterprise features and bugs: key budget edits and old-log cleanup gated as Enterprise, and a UI that flooded itself with retries.

    Published Nov 19, 2025self-described: Team running LiteLLM, looking to switch

    Counts toward, pending a recheck

    • Overall signal
    • Stability & Code Quality: Raised as a concern
    • Enterprise-Gated Features: Raised as a concern
    • Is LiteLLM ready to be the production gateway in front of every model call?: Not production-grade
    • When practitioners weigh LiteLLM against another gateway, which do they keep?: Chose another tool

    Published on

    Developer Communities

    Who

    Small product team

    Evidence

    Reported

    Applies to

    Needs a recheck

    Observed on

    LiteLLM Proxy

37. Negative

    smcleod, Hacker News commenter

    Comment on: Control LLM Spend and Access with any-LLM-gatewayHacker News comment

    After deploying LiteLLM Proxy in several places, plans to swap it for Bifrost: budget limits not enforced, parameter bugs, latency, and slow responses to reported fixes.

    Published Nov 19, 2025self-described: Deployed LiteLLM Proxy in a number of locations

    Counts toward

    • Overall signal
    • Virtual Keys, Budgets & Spend Tracking: Mixed or negative
    • Stability & Code Quality: Raised as a concern
    • Performance at Scale: Raised as a concern
    • Some replace it or build their own
    • Is LiteLLM ready to be the production gateway in front of every model call?: Not production-grade
    • When practitioners weigh LiteLLM against another gateway, which do they keep?: Chose another tool

    Published on

    Developer Communities

    Who

    Small product team

    Evidence

    Reported

    Applies to

    Still applicable

    Observed on

    LiteLLM Proxy

38. Mixed

    bjornjee, ML Ops team member (as stated)

    [Bug]: Litellm Proxy availability concerns. Cascading failures during high load to providersGitHub issue

    Under sustained provider 429s, new LiteLLM pods failed Kubernetes readiness probes, so all pods restarted and the gateway went down.

    Published Oct 14, 2025self-described: Kubernetes deployment, 2 to 5 replicas, about 60 QPS average and 500 QPS peak

    Counts toward

    • Overall signal
    • Routing, Fallbacks & Load Balancing: Mixed or negative
    • Performance at Scale: Raised as a concern
    • Is LiteLLM ready to be the production gateway in front of every model call?: Not production-grade

    Published on

    Developer Communities

    Who

    Product or platform team

    Evidence

    Reported

    Applies to

    Still applicable

    Observed on

    v1.77.7 on Kubernetes

39. Mixed

    AMeckes, Hacker News commenter, posting any-llm

    Comment on: Show HN: Any-LLM - Lightweight router to access any LLM ProviderHacker News comment

    Calls LiteLLM great but says the team needed something slightly different, so it built its own lightweight router.

    Published Jul 22, 2025self-described: Team that built its own lightweight LLM router

    Counts toward

    • Overall signal
    • Some replace it or build their own
    • When practitioners weigh LiteLLM against another gateway, which do they keep?: Chose another tool

    Published on

    Developer Communities

    Who

    Small product team

    Evidence

    Reported

    Applies to

    Still applicable

40. Mixed

    Nathan Brake, Mozilla.ai

    Introducing any-llm: A unified API to access any LLM providerEngineering blog post, Mozilla.ai blog

    Mozilla.ai credits LiteLLM's wide provider support, then built any-llm on the providers' own SDKs because LiteLLM's reimplemented interfaces can cause compatibility issues and changed behavior.

    Published Jul 22, 2025self-described: Mozilla.ai, which built its own provider library after reviewing LiteLLM

    Not counted

    Its authors at Mozilla.ai launch any-llm, a direct alternative to LiteLLM, and the post criticises LiteLLM. Kept in the record; it takes part in no figure.

    Published on

    Engineering Blogs & Reviews

    Who

    Product or platform team

    Evidence

    Reported

    Applies to

    Still applicable

41. Mixed

    TSJasonH, GitHub user

    [Bug]: Heavy RAM Usage over timeGitHub issue

    Their LiteLLM container's memory grows over days until monitoring alerts fire and a restart is needed, across stable releases.

    Published Jul 17, 2025self-described: Team testing an application through the proxy and pass-through routes

    Counts toward

    • Overall signal
    • Stability & Code Quality: Raised as a concern
    • Performance at Scale: Raised as a concern

    Published on

    Developer Communities

    Who

    Small product team

    Evidence

    Reported

    Applies to

    Still applicable

    Observed on

    LiteLLM Proxy in Docker

42. Negative

    meffmadd, member of a small TU Vienna team and author of the Aqueduct gateway

    Show HN: Aqueduct AI Gateway, a self-hostable AI gateway without the "taxes"Hacker News post (Show HN)

    The TU Vienna team rejected LiteLLM's proxy, Portkey, and Kong because each locked SSO, organization management, observability, or self-hosting behind enterprise plans, and built its own gateway on LiteLLM's Router SDK.

    "Every AI gateway we looked at (LiteLLM, Portkey, Kong, etc.) locked critical features like SSO, organization management, observability, or self-hosting behind enterprise plans."

    Published Jul 1, 2025self-described: A small TU Vienna team providing an OpenAI-compatible API to university researchers

    Not counted

    Its author built Aqueduct, a self-hostable AI gateway that competes with LiteLLM's proxy, and announced it in this post. Kept in the record; it takes part in no figure.

    Published on

    Developer Communities

    Who

    Small product team

    Evidence

    Reported

    Applies to

    Still applicable

    Observed on

    LiteLLM, Portkey, and Kong evaluated; Aqueduct built on the LiteLLM Router SDK

43. Positive

    bitdribble, Founder of DocRouter (as stated)

    Comment on: Launch HN: Reducto Studio (YC W24) - Build accurate document pipelines, fastHacker News comment

    Their document-processing startup runs on top of LiteLLM as a portability layer so it supports all major LLMs.

    Published Jun 25, 2025self-described: DocRouter, open-source document extraction product

    Counts toward

    • Overall signal
    • One API Across Providers: Positive
    • Stay provider-neutral
    • The library alone is enough for some

    Published on

    Developer Communities

    Who

    Technical leadership

    Evidence

    Reported

    Applies to

    Still applicable

    Observed on

    Python SDK

44. Mixed

    jbellis, Building the Brokk coding tool (as stated)

    Comment on: The unreasonable effectiveness of an LLM agent loop with tool useHacker News comment

    LiteLLM still does not support parallel tool calls with Gemini models, so the Brokk team wrote its own on top of structured output.

    Published May 15, 2025self-described: Brokk, AI coding product

    Counts toward, pending a recheck

    • Overall signal
    • One API Across Providers: Mixed or negative
    • Provider & Model Coverage: Mixed or negative

    Published on

    Developer Communities

    Who

    Small product team

    Evidence

    Reported

    Applies to

    Needs a recheck

45. Positive

    jbellis, Hacker News commenter, building Brokk

    Comment on: Hypermode Model Router Preview - OpenRouter AlternativeHacker News comment

    Brokk uses LiteLLM as one API over several models, but finds models not interchangeable for code, so routing to the fastest model does not appeal.

    Published May 8, 2025self-described: Brokk, an AI code tool

    Counts toward

    • Overall signal
    • One API Across Providers: Positive
    • When practitioners weigh LiteLLM against another gateway, which do they keep?: Chose or kept LiteLLM

    Published on

    Developer Communities

    Who

    Small product team

    Evidence

    Reported

    Applies to

    Still applicable

46. Mixed

    nicovank, Hacker News commenter, co-author of the project

    Comment on: AI Meets WinDBGHacker News comment

    Routes the project through LiteLLM, so other providers should work in theory, but in their experience only OpenAI's function calling works well.

    Published May 7, 2025self-described: Debugger assistant that relies on function calling

    Counts toward

    • Overall signal
    • One API Across Providers: Mixed or negative
    • Provider & Model Coverage: Mixed or negative

    Published on

    Developer Communities

    Who

    Small product team

    Evidence

    Reported

    Applies to

    Still applicable

47. Positive

    NetworkChuck (Chuck Keith), creator of the NetworkChuck YouTube channel

    I'm changing how I use AI (Open WebUI + LiteLLM)Video, YouTube

    Uses LiteLLM behind Open WebUI to reach ChatGPT, Claude, Gemini and Grok through one self-hosted gateway shared with a team and family under their own controls.

    Published Mar 13, 2025self-described: Shared AI hub for a team and family on Open WebUI

    Counts toward

    • Overall signal
    • One API Across Providers: Positive
    • Self-Hosted Control: Positive
    • One gateway for the organization

    Published on

    Podcasts, Talks & Videos

    Who

    Small product team

    Evidence

    Reported

    Applies to

    Still applicable

    Observed on

    LiteLLM Proxy with Open WebUI

48. No opinion stated

    anitamaxwynnn69, Reddit commenter

    Comment on: If you do, which ai gateway do you use and why?Reddit comment, r/LocalLLaMA

    Tried LiteLLM and found it too bloated for a local setup that only needed token tracking and one shared key, and settled on Bifrost after trying two other gateways.

    Published Oct 24, 2026self-described: Local AI setup that tracks token use and shares one key with a few people

    Not counted

    Its author's ties to the vendor have not been checked. Kept in the record; it takes part in no figure.

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

    Observed on

    LiteLLM, replaced by Bifrost

49. No opinion stated

    SamSausages, Reddit commenter

    Comment on: If you do, which ai gateway do you use and why?Reddit comment, r/LocalLLaMA

    Used LiteLLM for a while but stopped using it after its security lapses and has not turned it back on; now runs another proxy for switching between accounts.

    Published Oct 23, 2026self-described: Personal setup that switches between model accounts when usage limits run out

    Not counted

    Its author's ties to the vendor have not been checked. Kept in the record; it takes part in no figure.

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

    Observed on

    LiteLLM, replaced by CLIProxy

50. No opinion stated

    colin_colout, Reddit commenter

    Comment on: If you do, which ai gateway do you use and why?Reddit comment, r/LocalLLaMA

    Uses Bifrost and is happy with it, and tells others not to go anywhere near LiteLLM until its maintainers get their act together.

    Published Oct 23, 2026self-described: Personal local AI setup behind a gateway

    Not counted

    Its author's ties to the vendor have not been checked. Kept in the record; it takes part in no figure.

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

    Observed on

    Bifrost in place of LiteLLM

51. No opinion stated

    OneAnxiety2523, Reddit commenter

    Comment on: If you do, which ai gateway do you use and why?Reddit comment, r/LocalLLaMA

    Uses LiteLLM because it was the first gateway that worked without a fight, and its OpenAI-compatible endpoint plugs into everything else the author runs.

    Published Oct 23, 2026self-described: Personal projects tinkering with local and hosted models

    Not counted

    Its author's ties to the vendor have not been checked. Kept in the record; it takes part in no figure.

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

    Observed on

    LiteLLM's OpenAI-compatible endpoint

52. Mixed

    LidorMachluf, GitHub user who reported the compromise

    litellm 1.107.0 compromised: cook.pth credential stealer and sitecustomize RCE loaderGitHub issue

    All seven LiteLLM 1.107.0 wheels on PyPI carried a credential stealer and remote-code loader, and the latest Docker tags pointed to the same image until they were yanked.

    Published Oct 21, 2026self-described: Analysis of the 1.107.0 PyPI wheels and Docker images

    Counts toward

    • Overall signal
    • Security & Supply Chain: Raised as a concern

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Measured

    Applies to

    Current

    Observed on

    LiteLLM 1.107.0 PyPI wheels and Docker images

53. No opinion stated

    madsbergstroem, GitHub user

    MCP gateway DCR rejects Gemini app connectors: redirect_uris must be a list of 1 to 3 URIsGitHub issue, BerriAI/litellm

    The Gemini app's custom MCP connector could not register with LiteLLM's MCP gateway, which rejected Google's redirect URL list during client registration.

    Published Oct 15, 2026self-described: LiteLLM's MCP gateway serving a custom connector in the Gemini app

    Not counted

    Its author's ties to the vendor have not been checked. Kept in the record; it takes part in no figure.

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

    Observed on

    LiteLLM MCP gateway

54. Positive

    K0IN, Hacker News commenter

    Comment on: Ask HN: What do you run on a US$5 VPS that's worth keeping online 24/7?Hacker News comment

    Keeps LiteLLM running on a US$5 VPS as an AI bridge to monitor usage.

    Published Oct 9, 2026self-described: Personal VPS

    Counts toward

    • Overall signal
    • Virtual Keys, Budgets & Spend Tracking: Positive
    • Self-Hosted Control: Positive

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

    Observed on

    LiteLLM on a small VPS

55. Positive

    znpy, Hacker News commenter

    Comment on: Litelm: LiteLLM Without the BloatHacker News comment

    Runs LiteLLM at work, where nobody has cared about its 700 MB install size.

    Published Sep 12, 2026self-described: LiteLLM at work

    Counts toward

    • Overall signal
    • Operational Burden: Discussed without concern
    • Is LiteLLM ready to be the production gateway in front of every model call?: Runs it in production

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

56. Negative

    blazarquasar, Hacker News commenter

    Comment on: Litelm: LiteLLM Without the BloatHacker News comment

    After running LiteLLM and Bifrost for months, says LiteLLM adds a lot of latency and largely confirms Bifrost's published benchmark gap.

    Published Sep 12, 2026self-described: Ran LiteLLM and Bifrost side by side

    Counts toward

    • Overall signal
    • Performance at Scale: Raised as a concern

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

57. Negative

    santiagobasulto, Hacker News commenter

    Comment on: Litelm: LiteLLM Without the BloatHacker News comment

    Built their own minimal provider-agnostic router for an agent and calls LiteLLM and LangChain software to avoid at all costs.

    Published Sep 12, 2026self-described: Built own provider-agnostic agent layer

    Counts toward

    • Overall signal
    • Stability & Code Quality: Raised as a concern
    • Some replace it or build their own

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

58. Negative

    testycool, Hacker News commenter

    Comment on: Litelm: LiteLLM Without the BloatHacker News comment

    LiteLLM on a Hetzner server used 1 to 4 GB of memory for no reason they could find; Bifrost feels much lighter.

    Published Sep 11, 2026self-described: LiteLLM on a Hetzner server via Coolify

    Counts toward

    • Overall signal
    • Performance at Scale: Raised as a concern
    • When practitioners weigh LiteLLM against another gateway, which do they keep?: Chose another tool

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

    Observed on

    LiteLLM Proxy

59. Positive

    raphiki, Writer for Worldline's technology blog

    Building a Local-First AI Coding Agent with Open Tools and Adaptive RoutingEngineering blog post, Technology at Worldline (dev.to)

    Uses LiteLLM as the control plane for a local-first coding agent: spending limits, routing by complexity to hosted models, and logs that show what left the machine.

    "I selected LiteLLM, which we also use in production at work."

    Published Sep 9, 2026self-described: Laptop setup with Ollama, OpenCode and LiteLLM

    Counts toward

    • Overall signal
    • Virtual Keys, Budgets & Spend Tracking: Positive
    • Routing, Fallbacks & Load Balancing: Positive
    • Coding tools go through the gateway

    Published on

    Engineering Blogs & Reviews

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

    Observed on

    LiteLLM Proxy with OpenCode and Ollama

60. Negative

    CoralGarden52, GitHub user

    AnyLLM and LiteLLM return successful empty output for truncated responsesGitHub issue, openai/openai-agents-python

    Found that the Agents SDK's LiteLLM adapter treated an empty response the provider had cut off as a success, so the agent carried on with no output; the maintainer closed the issue without the proposed change, citing unconfirmed real-world impact.

    "For non-streaming Chat Completions responses, `AnyLLMModel` and `LitellmModel` treat an empty response truncated by the provider as a successful response."

    Published Sep 6, 2026self-described: OpenAI Agents SDK agents calling providers through the LiteLLM adapter

    Counts toward

    • Overall signal
    • Stability & Code Quality: Raised as a concern

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Still applicable

    Observed on

    LitellmModel in the OpenAI Agents SDK

61. No opinion stated

    franciscobispo, GitHub user

    [Bug]: Vertex AI Gemini + explicit context caching - usage.prompt_tokens intermittently reports only the fresh (non-cached) token countGitHub issue, BerriAI/litellm

    With context caching on Vertex AI Gemini through the proxy, the reported prompt token total intermittently dropped the cached portion, which breaks billing or reporting built on that field.

    "[Bug]: Vertex AI Gemini + explicit context caching - usage.prompt_tokens intermittently reports only the fresh (non-cached) token count instead of the total, when the request body is repeated identically ### What happened? When using explicit context caching (`cache_control: {"type": "ephemeral"}` on a system message) against a Vertex AI Gemini model through the proxy, `usage.prompt_tokens` on the chat completion response is **usually** correct (cached + fresh total), but **intermittently** comes back as just the fresh-content token count alone, silently dropping the cached portion from the total. `usage.prompt_tokens_details.cached_tokens` (and `usage.cache_read_input_tokens`) stay correct in both cases - only the top-level `prompt_tokens` is affected. This matters for anyone billing/reporting cost off `usage.prompt_tokens` (e.g. `prompt_tokens - cached_tokens` to get the fresh/billable remainder): on an anomalous response, that arithmetic double-subtracts the cached amount and under-reports cost. ### Reproduction - Model: `vertex_ai/gemini-2.5-flash`, added via the proxy's `/model/new` API (DB-backed model, not a static `config.yaml` entry). - Request: `cache: {"no-cache": true, "no-store": true}` explicitly set (to bypass LiteLLM's own Redis response cache, confirmed via distinct response `id`s between calls - these are genuinely separate calls, not replayed responses). - System message: ~2523-token static content, `cache_control: {"type": "ephemeral"}` on it. - User message: **the exact same text on every call** (e.g. `"Say OK."`). Ran two independent batches of 12 sequential calls each (identical body every time, ~5s apart): | Batch | Anomalies | Rate | |---|---|---| | 1 | 3/12 | 25% | | 2 | 1/12 | ~8% | Every anomalous response showed `prompt_tokens` equal to exactly the token count of the user message alone (e.g. `3` for `"Say OK."`), never a random/garbage value - always exactly the fresh-content count, with the cached portion silently missing from the total. `prompt_tokens_details.cached_tokens` remained correct (`2523`) on every single call, anomalous or not. **Control test**: ran the same setup but with a unique user-message body on every call (varying trial marker text), same cache reused each time. 0 anomalies across 15 calls in 3 separate batches. The anomaly only appeared when the exact request body was repeated. ### Relevant code (checked against the deployed tag) `litellm/llms/vertex_ai/gemini/vertex_and_google_ai_studio_gemini.py`, `_calculate_usage()`: ```python usage = Usage( prompt_tokens=usage_metadata.get("promptTokenCount", 0) + billable_tool_use_prompt_tokens, ... ) ``` This reads `promptTokenCount` straight from Vertex's own `usageMetadata` with no cache-token subtraction and no cross-call state - so the anomaly likely isn't in this mapping function itself. My guess (unconfirmed) is a caching/short-circuit path elsewhere in the proxy (possibly related to the `no-cache`/`no-store` handling, or a request-level token pre-estimate that occasionally gets returned instead of the real Vertex response's usage) that only triggers when the exact same request body has been seen before - but I haven't traced it further than this. ### Environment - LiteLLM version: `v1.98.0` (proxy, deployed via Helm/Kubernetes) - Provider: `vertex_ai` (Gemini 2.5 Flash) - Caching: explicit context caching via `cache_control` - Redis-backed response cache enabled at the proxy level (`litellm_settings.cache: true`), disabled per-request via `cache: {"no-cache": true, "no-store": true}` ### Are you a ML Ops Team? No ### What LiteLLM version are you on? v1.98.0…"

    Published Sep 1, 2026self-described: A LiteLLM proxy calling Vertex AI Gemini with explicit context caching, with cost reported from the usage fields

    Not counted

    Its author's ties to the vendor have not been checked. Kept in the record; it takes part in no figure.

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

    Observed on

    LiteLLM proxy to Vertex AI Gemini

62. Positive

    Paul Zuradzki, Developer

    LiteLLM AI Gateway: Routing, API Keys, Budgets, and Guardrails for Local and Cloud ModelsVideo, YouTube

    Runs LiteLLM in front of two local GPUs and cloud models, aiming for 80% local traffic, with scoped keys, budgets and simulated pricing for local models.

    "…model selection. My model picker, I've got all my local options, and then I've got a few API key-based ones for cloud. So personally, my goal is for like some of my personal projects would be like, if I can keep 80%…"

    Published Aug 26, 2026self-described: Self-hosted gateway in front of local GPUs and cloud models for a coding agent

    Counts toward

    • Overall signal
    • Virtual Keys, Budgets & Spend Tracking: Positive
    • Self-Hosted Control: Positive
    • Coding tools go through the gateway

    Published on

    Podcasts, Talks & Videos

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

    Observed on

    LiteLLM Proxy with llama.cpp

63. Positive

    geek_at, Hacker News commenter

    Comment on: Qwen 3.8-Flash-Next releasing tomorrow (125B a6B)Hacker News comment

    Self-hosts LiteLLM with aliases such as "coding", so a new model replaces the backend without changing keys or project config.

    Published Aug 25, 2026self-described: Self-hosted router with model aliases

    Counts toward

    • Overall signal
    • Routing, Fallbacks & Load Balancing: Positive
    • Stay provider-neutral

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

    Observed on

    Self-hosted LiteLLM Proxy

64. Negative

    Swapnoneel, Hacker News commenter

    Comment on: Is Hermes Agent unusable without a model router?Hacker News comment

    Tried LiteLLM to route an agent between a cheap and a strong model, saw significant routing delay, and moved to Bifrost.

    Published Aug 3, 2026self-described: Model router for the Hermes agent

    Counts toward

    • Overall signal
    • Performance at Scale: Raised as a concern
    • Some replace it or build their own
    • When practitioners weigh LiteLLM against another gateway, which do they keep?: Chose another tool

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

65. Mixed

    aftbit, Hacker News commenter

    Comment on: Kimi K3 Is Competitive with Fable; Kimi K3 and Fable Is SoTAHacker News comment

    Uses LiteLLM but finds it not trivial to run, and asks whether Bifrost can run from config files without a database.

    Published Jul 22, 2026self-described: Running LiteLLM

    Counts toward

    • Overall signal
    • Operational Burden: Raised as a concern

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

66. Mixed

    almogx3, GitHub user running a self-hosted proxy

    v3 rate limiter double-counts team per-model limits (model_per_team): effective RPM/TPM is half configuredGitHub issue

    Per-team, per-model rate limits in LiteLLM v1.83.14 were enforced at half the configured value because the limiter counted each request twice.

    Published Jul 21, 2026self-described: Self-hosted LiteLLM proxy with per-team model rate limits

    Counts toward, pending a recheck

    • Overall signal
    • Virtual Keys, Budgets & Spend Tracking: Mixed or negative
    • Stability & Code Quality: Raised as a concern

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Measured

    Applies to

    Needs a recheck

    Observed on

    v1.83.14-stable

67. Mixed

    endlessroad1991, Author of a budget-limited key gateway (as stated)

    Comment on: An LLM API gateway with budget-limited tokens for your LLM API keysHacker News comment

    Built a serverless budget-limited key gateway, then found LiteLLM virtual keys already do it with broader API coverage, though production LiteLLM needs compute, a database and a secret manager.

    Published Jul 20, 2026self-described: Personal serverless gateway on Cloudflare Workers

    Counts toward

    • Overall signal
    • Virtual Keys, Budgets & Spend Tracking: Positive
    • Operational Burden: Raised as a concern
    • Some replace it or build their own

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

68. Mixed

    Hanlin Xiang, Developer running an LLM gateway (as stated)

    5 Pitfalls I Hit Running LiteLLM Proxy in Production (with a 1-page survival map)dev.to article

    Six months running an 18-channel LiteLLM gateway: memory growth under concurrency, keys cached after reload, retry storms on 4xx errors, and thin Prometheus metrics.

    "A retry storm on a rate-limited provider can 3x your spend in 5 minutes."

    Published Jun 17, 2026self-described: 18-channel gateway with Redis and PostgreSQL serving agents and internal tools for six months

    Counts toward

    • Overall signal
    • Routing, Fallbacks & Load Balancing: Mixed or negative
    • Performance at Scale: Raised as a concern
    • Operational Burden: Raised as a concern
    • Is LiteLLM ready to be the production gateway in front of every model call?: Runs it in production

    Published on

    Engineering Blogs & Reviews

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

    Observed on

    LiteLLM Proxy with Redis and PostgreSQL

69. Mixed

    nobleach, Hacker News commenter

    Comment on: Kimi K2.7-Code: open-source coding model with better token efficiencyHacker News comment

    Their organization exposes Kimi 2.5 through LiteLLM, but it rarely works, so Claude and GPT remain their main tools at work.

    Published Jun 12, 2026self-described: Organization gateway offering Kimi

    Counts toward

    • Overall signal
    • Provider & Model Coverage: Mixed or negative

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

70. Positive

    jwbron, Hacker News commenter

    Comment on: Kimi K2.7-Code: open-source coding model with better token efficiencyHacker News comment

    Runs Claude Code through a patched LiteLLM proxy and OpenRouter to Qwen, Kimi and DeepSeek; everything except web fetch and search works.

    Published Jun 12, 2026self-described: Claude Code on open models

    Counts toward

    • Overall signal
    • Stay provider-neutral
    • Coding tools go through the gateway

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

    Observed on

    Patched LiteLLM Proxy with Claude Code

71. Positive

    msradam, Hacker News commenter

    Comment on: Running Claude Code Offline on an M3 Pro with Qwen3.6Hacker News comment

    At work runs Claude Code against internal models through a LiteLLM proxy, keeping the same Claude Code configuration across work and personal machines.

    Published Jun 11, 2026self-described: Internal models at work behind a LiteLLM proxy

    Counts toward

    • Overall signal
    • Coding tools go through the gateway

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

    Observed on

    LiteLLM Proxy with Claude Code

72. Mixed

    mmarian, Running the LibreThinker service (as stated)

    Comment on: Ask HN: How to manage AI APIs for SaaS application?Hacker News comment

    Uses LiteLLM for a 1,000-user service and finds it works okay-ish; vendors defaulting to MFA on API keys forced them to let some providers fail.

    Published May 20, 2026self-described: LibreThinker, a service with about 1,000 users

    Counts toward

    • Overall signal
    • Self-Hosted Control: Positive
    • Provider & Model Coverage: Mixed or negative

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

73. Negative

    lukewarm707, Hacker News commenter

    Comment on: LLMCap - A proxy that hard-stops LLM API calls when you hit a dollar capHacker News comment

    Self-hosted LiteLLM for privacy but found it buggy: the MCP page broke its Postgres and logging was truncated by default; moved off after the Trivy incident.

    Published May 19, 2026self-described: Self-hosted LiteLLM locally for privacy

    Counts toward

    • Overall signal
    • Stability & Code Quality: Raised as a concern
    • Security & Supply Chain: Raised as a concern
    • Some replace it or build their own
    • When practitioners weigh LiteLLM against another gateway, which do they keep?: Chose another tool

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

    Observed on

    Self-hosted LiteLLM Proxy

74. Mixed

    Zephyr0x, Hacker News commenter

    US$38k AWS Bedrock bill caused by a simple prompt caching missHacker News post

    A coding-agent workflow through LiteLLM to Claude Opus 4.6 on Bedrock billed US$37,901.73, mostly uncached input, because prompt caching silently underperformed and no hard cap stopped it.

    Published Apr 28, 2026self-described: Own coding-agent workflow: Droid to LiteLLM to Claude Opus 4.6 on Amazon Bedrock

    Counts toward

    • Overall signal
    • One API Across Providers: Mixed or negative
    • Coding tools go through the gateway

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Measured

    Applies to

    Current

    Observed on

    LiteLLM Proxy to Claude Opus 4.6 on Amazon Bedrock

75. Negative

    smcleod, Hacker News commenter

    Comment on: Show HN: GoModel - an open-source AI gateway in GoHacker News comment

    Calls LiteLLM proxy the worst-performing Python codebase they have used in a long time, riddled with serious bugs.

    Published Apr 21, 2026self-described: Has deployed LiteLLM Proxy in several places

    Counts toward

    • Overall signal
    • Stability & Code Quality: Raised as a concern
    • Performance at Scale: Raised as a concern
    • Is LiteLLM ready to be the production gateway in front of every model call?: Not production-grade

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

    Observed on

    LiteLLM Proxy

76. Positive

    Kamal Krishna Bhatt, Developer

    LiteLLM | Stop Over Spending on LLMs | Build Smart AI Gateway | Demo - LiteLLM & OpenCodeVideo, YouTube

    Connects OpenCode to several providers through LiteLLM and routes simple requests to cheaper models by complexity, tags and health.

    "…will integrate OpenCode with Light LLM. And basically, whenever a request comes in, Light LLM's router, the complexity router that is inbuilt inside Light LLM will decide whether a request that is incoming is simple, medium, or reasoning type. Then,…"

    Published Apr 18, 2026self-described: LiteLLM gateway routing OpenCode traffic across NVIDIA, OpenAI and Gemini

    Counts toward

    • Overall signal
    • Virtual Keys, Budgets & Spend Tracking: Positive
    • Routing, Fallbacks & Load Balancing: Positive
    • Coding tools go through the gateway

    Published on

    Podcasts, Talks & Videos

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

    Observed on

    LiteLLM Proxy with OpenCode

77. Positive

    therealpygon, Hacker News commenter

    Comment on: Reallocating US$100/Month Claude Code Spend to Zed and OpenRouterHacker News comment

    For internal chat, coding and agents, prefers a LiteLLM instance with one internal key per user, limits and logging over paying OpenRouter a per-token fee.

    Published Apr 9, 2026self-described: LiteLLM instance for internal users

    Counts toward

    • Overall signal
    • Virtual Keys, Budgets & Spend Tracking: Positive
    • Self-Hosted Control: Positive
    • One gateway for the organization
    • When practitioners weigh LiteLLM against another gateway, which do they keep?: Chose or kept LiteLLM

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

78. Negative

    cobertos, Hacker News commenter

    Comment on: Reallocating US$100/Month Claude Code Spend to Zed and OpenRouterHacker News comment

    Dropped LiteLLM after Anthropic models through its OpenAI-style API performed noticeably worse than the native API, and its MCP server proved buggy.

    Published Apr 9, 2026self-described: Evaluated LiteLLM for Anthropic models and MCP

    Counts toward

    • Overall signal
    • One API Across Providers: Mixed or negative
    • Stability & Code Quality: Raised as a concern
    • When practitioners weigh LiteLLM against another gateway, which do they keep?: Chose another tool

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

79. Negative

    lukewarm707, Hacker News commenter

    Comment on: The Claude Code LeakHacker News comment

    Found LiteLLM a 700 MB install with Postgres, Prometheus and an API layer, complicated to configure, when a simple proxy needed about 30 lines of FastAPI.

    Published Apr 2, 2026self-described: Tried a local LiteLLM install

    Counts toward

    • Overall signal
    • Operational Burden: Raised as a concern
    • Some replace it or build their own

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

80. Mixed

    babanetworx, GitHub user

    Focus: Stabilize core features and fix accumulated bugs/UX issuesGitHub issue

    Asks BerriAI to pause new features until every documented proxy and UI feature works, saying accumulated bugs erode trust.

    Published Mar 31, 2026self-described: Proxy and UI user

    Counts toward

    • Overall signal
    • Stability & Code Quality: Raised as a concern

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

81. Mixed

    Dan O'Leary, Independent developer

    TIL: uv Settings I Changed after LiteLLMPersonal blog post, Antisimplistic

    Uses LiteLLM in several projects and was not hit, then added a three-day uv dependency cooldown and a block on the bad versions.

    Published Mar 28, 2026self-described: Several personal projects that use LiteLLM

    Counts toward

    • Overall signal
    • Security & Supply Chain: Discussed without concern

    Published on

    Engineering Blogs & Reviews

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

    Observed on

    Python SDK via uv

82. Negative

    StrauXX, Hacker News commenter

    Comment on: My minute-by-minute response to the LiteLLM malware attackHacker News comment

    Evaluated LiteLLM as a proxy and rejected it for production: it adds lag and latency, features are half-baked, and the code is disorganized.

    Published Mar 27, 2026self-described: Evaluated LiteLLM for a project

    Counts toward

    • Overall signal
    • Stability & Code Quality: Raised as a concern
    • Performance at Scale: Raised as a concern
    • Is LiteLLM ready to be the production gateway in front of every model call?: Not production-grade
    • When practitioners weigh LiteLLM against another gateway, which do they keep?: Chose another tool

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

    Observed on

    LiteLLM Proxy

83. Negative

    sschueller, Hacker News commenter

    Comment on: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromisedHacker News comment

    Looking for an alternative for sharing LLMs across users: LiteLLM has been getting worse, pushes the paid version, and creating tokens for other users failed.

    Published Mar 24, 2026self-described: Sharing several LLMs across a set of users

    Counts toward

    • Overall signal
    • Stability & Code Quality: Raised as a concern
    • Enterprise-Gated Features: Raised as a concern
    • When practitioners weigh LiteLLM against another gateway, which do they keep?: Chose another tool

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

    Observed on

    LiteLLM Proxy

84. Negative

    chillfox, Hacker News commenter

    Comment on: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromisedHacker News comment

    Moved to OpenRouter a year earlier because LiteLLM was very flaky and kept causing outages.

    Published Mar 24, 2026self-described: Former LiteLLM user

    Counts toward

    • Overall signal
    • Stability & Code Quality: Raised as a concern
    • Some replace it or build their own
    • Is LiteLLM ready to be the production gateway in front of every model call?: Not production-grade
    • When practitioners weigh LiteLLM against another gateway, which do they keep?: Chose another tool

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

85. Mixed

    0fflineuser, Hacker News commenter

    Comment on: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromisedHacker News comment

    Checked their homelab LiteLLM proxy after the PyPI compromise and found the Docker image was an older 1.77 build, while noting auto-updates could have pulled a bad one.

    Published Mar 24, 2026self-described: Homelab proxy in Docker Compose

    Counts toward

    • Overall signal
    • Security & Supply Chain: Discussed without concern

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

    Observed on

    LiteLLM Proxy Docker image

86. Negative

    te_chris, Hacker News commenter

    Comment on: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromisedHacker News comment

    Reviewed the LiteLLM source code a while back, found it a mess, and steered clear.

    Published Mar 24, 2026self-described: Evaluated LiteLLM source

    Counts toward

    • Overall signal
    • Stability & Code Quality: Raised as a concern
    • When practitioners weigh LiteLLM against another gateway, which do they keep?: Chose another tool

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

87. Negative

    abhikul0, Hacker News commenter

    Comment on: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromisedHacker News comment

    Hit the compromised release through browser-use, which installs LiteLLM as a dependency; rebooted and invalidated the GitHub and Hugging Face tokens on the machine.

    Published Mar 24, 2026self-described: Local Python environment with browser-use

    Counts toward

    • Overall signal
    • Security & Supply Chain: Raised as a concern

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

    Observed on

    Transitive dependency of browser-use

88. Positive

    jerieljan, Hacker News commenter

    Comment on: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromisedHacker News comment

    Defends LiteLLM's value: it smoothed drift between OpenAI-compatible APIs and now centralizes guardrails, key spend tracking and key issuance, which is why its compromise spread so far.

    Published Mar 24, 2026self-described: Long-time LiteLLM proxy user

    Counts toward

    • Overall signal
    • One API Across Providers: Positive
    • Virtual Keys, Budgets & Spend Tracking: Positive
    • Security & Supply Chain: Discussed without concern
    • One gateway for the organization

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

89. Negative

    treefarmer, Hacker News commenter

    Comment on: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromisedHacker News comment

    Switched from the LiteLLM proxy to Portkey's free plan, finding it much faster, and criticizes LiteLLM's code for a 5,000-line core Python file.

    Published Mar 24, 2026self-described: Former LiteLLM proxy user

    Counts toward

    • Overall signal
    • Stability & Code Quality: Raised as a concern
    • Performance at Scale: Raised as a concern
    • Some replace it or build their own
    • When practitioners weigh LiteLLM against another gateway, which do they keep?: Chose another tool

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

90. No opinion stated

    Simon Willison, independent developer and Datasette creator

    Malicious litellm_init.pth in litellm 1.82.8: credential stealerPersonal blog post, simonwillison.net

    Simon Willison notes that installing the compromised LiteLLM 1.82.8 package was enough to run a credential stealer that collects SSH, cloud, and Kubernetes secrets.

    Published Mar 24, 2026self-described: Link-blog note on the March 2026 PyPI compromise

    Counts toward

    • Security & Supply Chain: Raised as a concern

    Published on

    Engineering Blogs & Reviews

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

91. Negative

    mathis-l, Hacker News commenter

    Comment on: Tell HN: Litellm 1.82.7 and 1.82.8 on PyPI are compromisedHacker News comment

    Points out that CrewAI, which depends on LiteLLM, pinned it to 1.82.6, the last good version, hours after the compromise, without saying why in the commit message.

    "CrewAI (uses litellm) pinned it to 1.82.6 (last good version) 5 hours ago but the commit message does not say anything about a potential compromise."

    Published Mar 24, 2026self-described: Following CrewAI's dependency on LiteLLM during the March 2026 compromise

    Counts toward

    • Overall signal
    • Security & Supply Chain: Raised as a concern

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Still applicable

    Observed on

    CrewAI's LiteLLM dependency

92. Positive

    alexsmirnov, Hacker News commenter

    Comment on: Why Developers Keep Choosing Claude over Every Other AIHacker News comment

    Connects Claude Code to a LiteLLM router dispatching to Bedrock, OpenAI, Gemini, OpenRouter and Ollama, and re-evaluates which model does each job faster or cheaper.

    Published Feb 26, 2026self-described: Claude Code across several providers with an evaluation loop

    Counts toward

    • Overall signal
    • Routing, Fallbacks & Load Balancing: Positive
    • Stay provider-neutral
    • Coding tools go through the gateway

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

    Observed on

    LiteLLM Router with Claude Code

93. Positive

    raybb, Hacker News commenter

    Comment on: Gemini 3 Deep ThinkHacker News comment

    Rates OpenRouter highly but thinks LiteLLM does a very good job as a plain Python library with no platform middleman.

    Published Feb 12, 2026self-described: Calling Gemini Deep Think

    Counts toward

    • Overall signal
    • Self-Hosted Control: Positive
    • The library alone is enough for some
    • When practitioners weigh LiteLLM against another gateway, which do they keep?: Chose or kept LiteLLM

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

    Observed on

    Python SDK

94. Mixed

    pstanisl, GitHub user

    Updating the team/key as enterprise feature in v1.81..6.rc.1?GitHub issue

    In a new release, changing a team's budget or models demanded an Enterprise license.

    Published Feb 5, 2026self-described: Self-hosted proxy

    Counts toward, pending a recheck

    • Overall signal
    • Enterprise-Gated Features: Raised as a concern

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Needs a recheck

    Observed on

    v1.81.6 release candidate

95. Negative

    zeroxfe, Hacker News commenter

    Comment on: Kimi K2.5 Technical Report [pdf]Hacker News comment

    Tried Claude Code with Kimi through the LiteLLM proxy and found it failed in too many places, since Claude Code does not use standard completions APIs.

    Published Jan 30, 2026self-described: Claude Code with Kimi through a proxy

    Counts toward

    • Overall signal
    • One API Across Providers: Mixed or negative
    • Coding tools go through the gateway

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

    Observed on

    LiteLLM Proxy with Claude Code

96. Positive

    Roark66, Hacker News commenter

    Comment on: Show HN: A MitM proxy to see what your LLM tools are sendingHacker News comment

    Runs a slightly modified LiteLLM with Langfuse to record everything Claude Code and other coding assistants send, and is quite happy with it.

    Published Jan 29, 2026self-described: Recording coding assistant traffic

    Counts toward

    • Overall signal
    • Coding tools go through the gateway
    • When practitioners weigh LiteLLM against another gateway, which do they keep?: Chose or kept LiteLLM

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

    Observed on

    Modified LiteLLM with Langfuse

97. Mixed

    photios, Hacker News commenter

    Comment on: The Agentic AI Handbook: Production-Ready PatternsHacker News comment

    Got Claude Code running on Copilot APIs through the LiteLLM proxy at a bank, but calls it a pain and recommends OpenCode instead.

    Published Jan 21, 2026self-described: Previously at a bank where only Copilot was approved

    Counts toward

    • Overall signal
    • Operational Burden: Raised as a concern
    • Coding tools go through the gateway

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

    Observed on

    LiteLLM Proxy with Claude Code

98. Positive

    mlrtime, Hacker News commenter

    Comment on: Anthropic blocks third-party use of Claude Code subscriptionsHacker News comment

    When a Claude Pro plan runs out, points Claude Code at LiteLLM through ANTHROPIC_BASE_URL to finish work on a cheaper model.

    Published Jan 9, 2026self-described: Claude Code with cheaper models

    Counts toward

    • Overall signal
    • Stay provider-neutral
    • Coding tools go through the gateway

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Current

    Observed on

    LiteLLM Proxy with Claude Code

99. Mixed

    Manouchehri, Hacker News commenter

    Comment on: Control LLM Spend and Access with any-LLM-gatewayHacker News comment

    LiteLLM was good early on, but over the past year they run into more bugs than features.

    Published Nov 20, 2025self-described: Long-time LiteLLM user

    Counts toward

    • Overall signal
    • Stability & Code Quality: Raised as a concern

    Published on

    Developer Communities

    Who

    Individual builder

    Evidence

    Reported

    Applies to

    Still applicable

100. Negative

     everlier, Hacker News commenter

     Comment on: Control LLM Spend and Access with any-LLM-gatewayHacker News comment

     Had to debug a LiteLLM bug where tools failed only for the Ollama provider and only with streaming on.

     Published Nov 19, 2025self-described: Debugging LiteLLM with Ollama

     Counts toward

     • Overall signal
     • One API Across Providers: Mixed or negative
     • Stability & Code Quality: Raised as a concern

     Published on

     Developer Communities

     Who

     Individual builder

     Evidence

     Reported

     Applies to

     Still applicable

101. Positive

     malnourish, Hacker News commenter

     Comment on: 5 Things to Try with Gemini 3 Pro in Gemini CLIHacker News comment

     Still runs Roo Code through LiteLLM and has seen no compelling reason to switch.

     Published Nov 18, 2025self-described: Roo Code user

     Counts toward

     • Overall signal
     • Coding tools go through the gateway
     • When practitioners weigh LiteLLM against another gateway, which do they keep?: Chose or kept LiteLLM

     Published on

     Developer Communities

     Who

     Individual builder

     Evidence

     Reported

     Applies to

     Still applicable

     Observed on

     LiteLLM with Roo Code

102. Mixed

     menardorama, GitHub user

     [Feature]: Provide non-profit licensesGitHub issue

     Asks for non-profit licenses, calling LiteLLM promising but its Enterprise license cost a show-stopper for non-profits.

     Published Nov 12, 2025self-described: Non-profit and research use

     Counts toward

     • Overall signal
     • Enterprise-Gated Features: Raised as a concern

     Published on

     Developer Communities

     Who

     Individual builder

     Evidence

     Reported

     Applies to

     Still applicable

103. Positive

     Owain Lewis, AI engineering educator

     Build Production AI Agents in 2025 [With LiteLLM]Video, YouTube

     Builds simple production agents in plain Python on the LiteLLM SDK and skips agent frameworks.

     Published Nov 7, 2025self-described: Plain-Python agents built on the LiteLLM SDK

     Counts toward

     • Overall signal
     • One API Across Providers: Positive
     • The library alone is enough for some

     Published on

     Podcasts, Talks & Videos

     Who

     Individual builder

     Evidence

     Reported

     Applies to

     Still applicable

     Observed on

     Python SDK

104. Positive

     libraryofbabel, Hacker News commenter

     Comment on: Claude Code on the webHacker News comment

     Runs Claude Code against GPT-5 through a LiteLLM proxy to compare models, calling it not hard and quite interesting.

     Published Oct 20, 2025self-described: Comparing coding models under Claude Code

     Counts toward

     • Overall signal
     • Stay provider-neutral
     • Coding tools go through the gateway

     Published on

     Developer Communities

     Who

     Individual builder

     Evidence

     Reported

     Applies to

     Still applicable

     Observed on

     LiteLLM Proxy with Claude Code

105. Mixed

     LLukas22, GitHub user

     [Bug]: This feature is only available for LiteLLM Enterprise users error while trying to update a virtual keyGitHub issue

     After an upgrade, editing an existing virtual key, even adding a model, returned an Enterprise-only error that earlier open-source versions did not.

     Published Oct 6, 2025self-described: Self-hosted proxy without a license

     Counts toward, pending a recheck

     • Overall signal
     • Stability & Code Quality: Raised as a concern
     • Enterprise-Gated Features: Raised as a concern

     Published on

     Developer Communities

     Who

     Individual builder

     Evidence

     Reported

     Applies to

     Needs a recheck

     Observed on

     LiteLLM Proxy, open source

106. Negative

     binalpatel, Hacker News commenter

     Comment on: Building your own CLI coding agent with Pydantic-AIHacker News comment

     Switched a coding-agent project from LiteLLM to Pydantic AI partly out of disgust at LiteLLM's poor documentation and developer experience.

     Published Aug 28, 2025self-described: Hobby coding agent CLI

     Counts toward

     • Overall signal
     • Operational Burden: Raised as a concern
     • The library alone is enough for some
     • Some replace it or build their own
     • When practitioners weigh LiteLLM against another gateway, which do they keep?: Chose another tool

     Published on

     Developer Communities

     Who

     Individual builder

     Evidence

     Reported

     Applies to

     Still applicable

     Observed on

     Python SDK

107. Positive

     ziftface, Hacker News commenter

     Comment on: Building your own CLI coding agent with Pydantic-AIHacker News comment

     Left Pydantic AI over streaming problems and moved to LiteLLM, finding its docs simple and everything working as expected.

     Published Aug 28, 2025self-described: Agentic application

     Counts toward

     • Overall signal
     • One API Across Providers: Positive
     • The library alone is enough for some
     • When practitioners weigh LiteLLM against another gateway, which do they keep?: Chose or kept LiteLLM

     Published on

     Developer Communities

     Who

     Individual builder

     Evidence

     Reported

     Applies to

     Still applicable

     Observed on

     Python SDK

108. Positive

     samsk, Hacker News commenter

     Comment on: Show HN: AgentGuard - Auto-kill AI agents before they burn through your budgetHacker News comment

     Controls agent spend with LiteLLM virtual keys that carry daily or weekly budgets, and finds the setup flexible with a nice UI.

     Published Jul 31, 2025self-described: Agent spend control

     Counts toward

     • Overall signal
     • Virtual Keys, Budgets & Spend Tracking: Positive

     Published on

     Developer Communities

     Who

     Individual builder

     Evidence

     Reported

     Applies to

     Still applicable

     Observed on

     LiteLLM Proxy

109. Positive

     jerieljan, Hacker News commenter

     Comment on: Ollama's new appHacker News comment

     Has run a LiteLLM proxy in front of Open WebUI for over a year and finds it very effective for any OpenAI-compatible app.

     Published Jul 31, 2025self-described: Personal Open WebUI setup

     Counts toward

     • Overall signal
     • One API Across Providers: Positive
     • One gateway for the organization

     Published on

     Developer Communities

     Who

     Individual builder

     Evidence

     Reported

     Applies to

     Still applicable

     Observed on

     LiteLLM Proxy with Open WebUI

110. Positive

     therealpygon, Hacker News commenter

     Comment on: Show HN: AgentGuard - Auto-kill AI agents before they burn through your budgetHacker News comment

     Points every editor and tool at a local LiteLLM proxy, calling it a locally hosted OpenRouter that charges nothing for routing; some models need manual pricing config.

     Published Jul 31, 2025self-described: Local proxy for trying editors and tools

     Counts toward

     • Overall signal
     • One API Across Providers: Positive
     • Virtual Keys, Budgets & Spend Tracking: Positive
     • Self-Hosted Control: Positive
     • Stay provider-neutral
     • Coding tools go through the gateway

     Published on

     Developer Communities

     Who

     Individual builder

     Evidence

     Reported

     Applies to

     Still applicable

     Observed on

     LiteLLM Proxy in Docker

111. Positive

     sneilan1, Hacker News commenter

     Comment on: Cerebras launches Qwen3-235B, achieving 1.5k tokens per secondHacker News comment

     Pointed a local LiteLLM proxy at the Cerebras API and connected Aider to it within minutes to try Qwen-235B.

     Published Jul 23, 2025self-described: Aider on Cerebras through a local proxy

     Counts toward

     • Overall signal
     • Provider & Model Coverage: Positive
     • Coding tools go through the gateway

     Published on

     Developer Communities

     Who

     Individual builder

     Evidence

     Reported

     Applies to

     Still applicable

     Observed on

     LiteLLM Proxy with Aider

112. Positive

     dlojudice, Hacker News commenter

     Comment on: Show HN: Any-LLM - lightweight and open-source router to access any LLM ProviderHacker News comment

     Runs the LiteLLM Proxy even in development because its usage and logs give visibility into LLM use, and caching cuts the cost of repeated testing.

     Published Jul 22, 2025self-described: Development environment

     Counts toward

     • Overall signal
     • Virtual Keys, Budgets & Spend Tracking: Positive

     Published on

     Developer Communities

     Who

     Individual builder

     Evidence

     Reported

     Applies to

     Still applicable

     Observed on

     LiteLLM Proxy in Docker

113. Negative

     delijati, Hacker News commenter

     Comment on: Show HN: Any-LLM - Lightweight router to access any LLM ProviderHacker News comment

     Found nothing lite about LiteLLM while experimenting with it as a library, and moved to Simon Willison's llm instead.

     Published Jul 22, 2025self-described: Experimenting with the library

     Counts toward

     • Overall signal
     • Operational Burden: Raised as a concern
     • The library alone is enough for some
     • Some replace it or build their own
     • When practitioners weigh LiteLLM against another gateway, which do they keep?: Chose another tool

     Published on

     Developer Communities

     Who

     Individual builder

     Evidence

     Reported

     Applies to

     Still applicable

     Observed on

     Python SDK

114. Mixed

     Szpadel, Hacker News commenter

     Comment on: Show HN: Any-LLM - Lightweight router to access any LLM ProviderHacker News comment

     Uses LiteLLM as a personal gateway and reports a release that broke DeepSeek reasoning output in both sync and streaming responses.

     Published Jul 22, 2025self-described: Personal AI gateway

     Counts toward

     • Overall signal
     • One API Across Providers: Mixed or negative
     • Stability & Code Quality: Raised as a concern

     Published on

     Developer Communities

     Who

     Individual builder

     Evidence

     Reported

     Applies to

     Still applicable

     Observed on

     LiteLLM Proxy

115. Negative

     ruidazeng (Ruida Zeng), GitHub user

     LiteLLM + Gemini 2.5 Pro: cached_tokens=None crashes Agents SDK with Pydantic int-validation errorGitHub issue, openai/openai-agents-python

     An Agents SDK run on Gemini through LiteLLM crashed during cost calculation because LiteLLM returned no cached-token count; the issue was later closed.

     "When `Runner.run()` executes an agent whose model is a **Gemini 2.5-pro** instance wrapped by **LiteLLM**, the pipeline dies during cost-calculation with…"

     Published May 26, 2025self-described: An OpenAI Agents SDK agent running Gemini through LiteLLM

     Counts toward, pending a recheck

     • Overall signal
     • One API Across Providers: Mixed or negative
     • Stability & Code Quality: Raised as a concern

     Published on

     Developer Communities

     Who

     Individual builder

     Evidence

     Reported

     Applies to

     Needs a recheck

     Observed on

     LitellmModel wrapping Gemini in the OpenAI Agents SDK

116. Mixed

     sammcj, GitHub user

     litellm fails to block requests over end-user budget when user header usedGitHub issue

     LiteLLM let users keep sending requests after they exceeded their budget, and a March pull request with a fix was closed without the bug being fixed.

     Published May 23, 2025self-described: LiteLLM proxy with per-user budgets

     Counts toward, pending a recheck

     • Overall signal
     • Virtual Keys, Budgets & Spend Tracking: Mixed or negative
     • Stability & Code Quality: Raised as a concern

     Published on

     Developer Communities

     Who

     Individual builder

     Evidence

     Reported

     Applies to

     Needs a recheck

     Observed on

     main-v1.70.4-nightly

117. Negative

     nprateem, Hacker News commenter

     Comment on: An upgraded dev experience in Google AI StudioHacker News comment

     Tried LiteLLM to paper over differences in structured output between Anthropic and other providers, without success.

     Published May 22, 2025self-described: SaaS product with fallbacks across Claude, Gemini and OpenAI

     Counts toward

     • Overall signal
     • One API Across Providers: Mixed or negative

     Published on

     Developer Communities

     Who

     Individual builder

     Evidence

     Reported

     Applies to

     Still applicable

118. Mixed

     stuaxo, Hacker News commenter

     Comment on: A critical look at MCPHacker News comment

     Uses LiteLLM as a thin abstraction over native libraries in a Django app, alongside LangChain for the rest, and still hits inconsistent model names across backends such as Bedrock.

     Published May 11, 2025self-described: Django app on several model backends

     Counts toward

     • Overall signal
     • One API Across Providers: Mixed or negative
     • The library alone is enough for some

     Published on

     Developer Communities

     Who

     Individual builder

     Evidence

     Reported

     Applies to

     Still applicable

     Observed on

     Python SDK

119. Positive

     simple10, Hacker News commenter

     Comment on: Gemini 2.5 Pro Preview: even better coding performanceHacker News comment

     Runs LiteLLM locally between Cursor and provider APIs, with Langfuse traces and per-project keys to monitor or cap billing.

     Published May 6, 2025self-described: Local LiteLLM with Langfuse in front of Cursor

     Counts toward

     • Overall signal
     • Virtual Keys, Budgets & Spend Tracking: Positive
     • Coding tools go through the gateway

     Published on

     Developer Communities

     Who

     Individual builder

     Evidence

     Reported

     Applies to

     Still applicable

     Observed on

     LiteLLM Proxy with Langfuse

120. Mixed

     miki123211, Hacker News commenter

     Comment on: Google Gemini has the worst LLM APIHacker News comment

     Their structured-output code built on LiteLLM does not work with Google's models, because Gemini expects a different JSON schema format.

     Published May 4, 2025self-described: Structured output code across providers

     Counts toward

     • Overall signal
     • One API Across Providers: Mixed or negative
     • The library alone is enough for some

     Published on

     Developer Communities

     Who

     Individual builder

     Evidence

     Reported

     Applies to

     Still applicable

     Observed on

     Python SDK

121. Positive

     ehsanu1, Hacker News commenter

     Comment on: Show HN: Memex is a Claude Code alternative built on Rust+Tauri for vibe codingHacker News comment

     Their company runs LiteLLM internally so any open-source tool can use any backend, with a virtual key per developer to monitor and limit usage.

     Published Apr 29, 2025self-described: Employer requires LLM use through its own provider contracts

     Counts toward

     • Overall signal
     • Virtual Keys, Budgets & Spend Tracking: Positive
     • Self-Hosted Control: Positive
     • One gateway for the organization
     • Coding tools go through the gateway

     Published on

     Developer Communities

     Who

     Individual builder

     Evidence

     Reported

     Applies to

     Still applicable

122. Mixed

     uyzeqzer, Hacker News commenter

     Comment on: Show HN: Memex is a Claude Code alternative built on Rust+Tauri for vibe codingHacker News comment

     Their workplace uses LiteLLM, so coding tools that cannot point at it are ruled out; Codex works with LiteLLM once the Responses API is disabled.

     Published Apr 29, 2025self-described: Workplace that routes coding tools through LiteLLM

     Counts toward

     • Overall signal
     • One gateway for the organization
     • Coding tools go through the gateway

     Published on

     Developer Communities

     Who

     Individual builder

     Evidence

     Reported

     Applies to

     Still applicable

123. Positive

     dimitri-vs, Hacker News commenter

     Comment on: xAI has acquired X, xAI now valued at US$80BHacker News comment

     Uses LiteLLM because rolling your own router across many viable providers with different specialties gets annoying.

     Published Mar 28, 2025self-described: Team app using several providers

     Counts toward

     • Overall signal
     • One API Across Providers: Positive
     • Stay provider-neutral

     Published on

     Developer Communities

     Who

     Individual builder

     Evidence

     Reported

     Applies to

     Still applicable

124. Positive

     scosman, Maintainer of the open-source Kiln app (as stated)

     Comment on: We chose LangGraph to build our coding agentHacker News comment

     Migrated a bring-your-own-key app from LangChain to LiteLLM and never looked back, but needed over 1,000 integration tests to keep the provider grid working.

     Published Mar 25, 2025self-described: Kiln, bring-your-own-key app across 13 providers

     Counts toward

     • Overall signal
     • One API Across Providers: Positive
     • Provider & Model Coverage: Positive
     • Stay provider-neutral
     • The library alone is enough for some

     Published on

     Developer Communities

     Who

     Individual builder

     Evidence

     Reported

     Applies to

     Still applicable

     Observed on

     Python SDK

125. Positive

     wkat4242, Hacker News commenter

     Comment on: Chatbox: Cross-platform desktop client for ChatGPT, Claude and other LLMsHacker News comment

     Bridges Claude, OpenAI and Groq into Open WebUI through LiteLLM to control which models appear, and reports it works perfectly.

     Published Jan 25, 2025self-described: Personal setup: Open WebUI with Claude, OpenAI and Groq

     Counts toward

     • Overall signal
     • One API Across Providers: Positive

     Published on

     Developer Communities

     Who

     Individual builder

     Evidence

     Reported

     Applies to

     Still applicable

     Observed on

     LiteLLM Proxy with Open WebUI