litellm vs my-free-code
litellm is much bigger: 62.0k stars against 625. Over the days we have tracked them litellm moved +12.9% and my-free-code +34.7%, so my-free-code is growing faster right now.
Neither one leads on the six capability axes, so the choice comes down to which of them fits the way you already work.
Stars and commit dates come from our own daily tracking. The six axes are read off each project's documentation by our review pipeline, so they describe what a project says about itself, not what we measured in its code.
Where they stand today
A lightweight, production-ready self-hosted AI gateway that unifies 100+ LLM providers into a single OpenAI-compatible API with virtual keys, spend tracking, guardrails, and load balancing.
- Stars
- 62.0k
- Tracked growth
- +12.9%
- Maturity
- ●●●●●
- Last commit
- 2h ago
- Language
- Python
- License
- NOASSERTION
- Cost to run
- Self-hosted — your API keys (pay providers)
Multi-provider gateway that routes Claude Code and other coding agents across a broad provider catalog with ordered fallbacks and local-model runtimes.
- Stars
- 625
- Tracked growth
- +34.7%
- Maturity
- ●●●●●
- Last commit
- 4d ago
- Language
- Python
- License
- MIT
- Cost to run
- Your API keys for upstream providers; local models run locally (no provider fees).
Six axes, head to head
Each axis runs 0 to 5. The label under a score is what that project's own docs claim, not a category average.
| Axis | litellm | my-free-code |
|---|---|---|
Context depth How much of your codebase it sees before it answers: the open diff, the diff plus related files, or the whole repository. | ●●●●● No repo context | ●●●●● Diff only |
Noise control How it keeps output volume down — severity thresholds, deduplication, incremental runs over new commits only. | ●●●●● Basic guardrails | ●●●●● Basic filters |
Customization How far it bends to your team: custom rules, prompts, style guides, per-path config. | ●●●●● Configurable | ●●●●● Env/config options |
Privacy Whether your code stays on your own infrastructure: fully local, self-hostable, or cloud API only. | ●●●●● Self-hostable | ●●●●● Runs fully local |
Model freedom Whether you can point it at any provider, or it is wired to one. | ●●●●● Bring-your-own-key | ●●●●● Bring-your-own provider |
Setup ease What it takes to get a first useful run out of it. | ●●●●● Config + API key | ●●●●● Env + API key |
Which one to pick
Pick litellm if…
Unified multi-provider support — use one OpenAI-compatible API to call 100+ LLMs with a self-hosted gateway, virtual keys, and cost tracking.
Pick my-free-code if…
Privacy-first — run a self-hosted gateway that supports many upstream providers plus local runtimes (Ollama/llama.cpp) for Claude Code and other coding agents.
What people want from each one
Questions people ask
Is litellm better than my-free-code?
Neither one leads on the six capability axes, so the choice comes down to which of them fits the way you already work. litellm is worth picking when unified multi-provider support — use one OpenAI-compatible API to call 100+ LLMs with a self-hosted gateway, virtual keys, and cost tracking.
Which of litellm and my-free-code keeps my code private?
litellm: Self-hostable (4/5). my-free-code: Runs fully local (5/5).
What does each one cost to run?
litellm: Self-hosted — your API keys (pay providers). my-free-code: Your API keys for upstream providers; local models run locally (no provider fees)..
Full profiles: BerriAI/litellm and hkqr/my-free-code. Everything else in Gateways & routing.