OpenLLM vs Claude Code Router
Claude Code Router is an open-source local proxy for Claude Code that sends requests to the API-key providers or local models you configure, with conditional routing, retries and ordered fallback models. Claude Code Router for API keys and local models on any OS; OpenLLM when your existing plans are the model access and you run several agents.
curl -fsSL https://www.openllm.sh/install | bashopenllm claudeOpenLLM vs Claude Code Router
| Feature | OpenLLM | Claude Code Router |
|---|---|---|
| Model access | Subscriptions, API keys and any OpenAI-compatible endpoint | API keys and local models |
| Runs | Local daemon for subscriptions; hosted gateway for API keys and the dashboard | Fully local |
| Fallback | Per-alias chains shared by every client; a rate-limited entry is cooled and the chain continues before any output | Retries and ordered fallback models |
| Clients | openllm claude, openllm codex, openllm opencode: a per-session overlay that leaves the client's config untouched | Claude Code |
| Config | Chains and aliases in one dashboard, shared by every device | A config file per machine |
| Platforms | macOS and Linux | macOS, Linux and Windows |
| Price | Free plan with a monthly token allowance, no card; no markup on provider tokens | Free and open source |
Pick Claude Code Router when
- You only use API keys or local models
- You are on Windows
- You want no hosted component at all
Pick OpenLLM when
- Your model access is the plans you already pay for
- You run more than one coding agent and want one key and one usage view
- You want chains managed in one place, not per machine
Your subscriptions stay on your machine
Subscription providers run through the local OpenLLM daemon, which delegates to the vendor's official CLI and its own login. The hosted gateway never holds a subscription credential.
Provider keys encrypted at rest
API keys are encrypted in your browser with AES-256-GCM under a key derived from your recovery phrase, and stored as ciphertext. They are decrypted in memory only while a request is being served, then discarded. Subscription credentials never reach the hosted service.
Fallback chains when a model is rate-limited
Define an ordered chain per model alias. When a hop returns a rate limit, an overload or a provider error, the request moves to the next hop instead of failing your session.
- Chains are configured once and shared by every client and device
- Each hop resolves its own model settings, so a fallback never inherits the wrong parameters
- Every hop that ran is visible in your request history
Code search and memory over MCP
The same binary ships one MCP server: semantic search over your indexed repositories and documentation, plus memory that persists across sessions and clients.
Questions
Something else? Contact us
Checked 2026-09-25 against Claude Code Router README.