u/WarningOut_OfMinD

LiteLLM is moving to Rust. Sub-1ms overhead. A sub-100MB binary. The same Python SDK and AI gateway you already use.

Over the past year we've heard the same thing from our users and our community - they want the fastest, most lite AI gateway they can run. We've heard you, and we're committing to it.

This goes straight at the problems our customers report: latency spikes under load, and the memory leaks and OOM kills that take pods down at the worst possible time. A Rust hot path is faster and bounded in memory, so those whole classes of issues go away.

It's a gradual, non-breaking change. The Python SDK and proxy stay exactly the same - under the hood they start calling the Rust binary through PyO3, one component at a time, each proven in production before the next.

The whole ai gateway will be running on Rust by December 1, 2026.

We think this is the right call to build the best, most scalable, and cheapest AI gateway out there.

Read the full announcement: https://docs.litellm.ai/blog/litellm-rust-launch

We’re making stability a first-class citizen at LiteLLM

Over the past few months, we’ve heard from users that LiteLLM has had more bugs and regressions than it should. We take that seriously.

So we’re kicking off a dedicated stability sprint with two goals:
- Close 20 reported bugs in core functionality
- Fix the root causes behind bugs in 3 core areas: MCP, Gateway, and UI

The main bug classes we’re driving down:

1. MCP Authentication - View/List Tools should work reliably across every supported MCP auth method.

2. Gateway Authentication - Every request should resolve to the right key, user, team, and team member, so spend and budgets are always attributed correctly.

3. UI Forms- When you save a form, it should only change the field you edited. Nothing else should get wiped or overwritten.

If there’s a LiteLLM bug affecting you that isn’t on the list, please comment on this GitHub issue

You can read more about our stability sprint here