Compare · Claude Code Router and Selan
Is there a Claude Code Router alternative for a team?
Yes, if a whole team needs the same models, limits and usage record. Claude Code Router (CCR) is a free, MIT-licensed gateway that runs on your own machine and sends Claude Code, Codex and other agents to the providers you choose. Selan is a hosted gateway: each developer signs in once, with no provider key on the laptop. For one developer trying models, CCR is the better answer.
How do Claude Code Router and Selan compare?
| Claude Code Router | Selan | |
|---|---|---|
| What it is | A local model gateway with a management UI, as a desktop app, an npm CLI or a Docker image | A hosted gateway, with a CLI that launches Claude Code, Codex and OpenCode through it |
| Where it runs | On your machine, at http://127.0.0.1:3456, or on a server you run with Docker | A hosted service, built and hosted in the EU. Nothing to run |
| Agents | Claude Code, Codex, OpenCode, Grok CLI, Kimi CLI, Kilo Code, Pi, ZCode, Claude Design, WorkBuddy and compatible API clients | Claude Code, Codex, OpenCode and Claude Desktop, plus agent apps such as Hermes Agent and Paperclip |
| Providers | Presets such as OpenRouter, DeepSeek, Moonshot, Mistral and Z.AI, or any endpoint that speaks the OpenAI, Anthropic or Gemini protocols | Anthropic, OpenAI, Google Vertex, OpenRouter, nexos.ai and Ollama Cloud |
| Provider keys | Entered into CCR and stored in its configuration, on that machine or server | Connected once by an owner; none on a developer's laptop |
| A developer's credential | A CCR client key | One sign-in with Google or Microsoft through selan login |
| Choosing the model | Routing rules on headers and bodies, rewrites, retries and ordered fallbacks to other models | The model you name. Subscriptions are tried first, then a key, and nothing is substituted silently |
| Limits | Request, token and image limits per client key, with an expiry date | A spend limit per person, by day, week or month in UTC, on pay-per-use keys |
| Usage record | Request logs on that install, with provider, model, tokens, latency and an estimated cost | One record for the company: people and teams ranked, and every request with who ran it |
| Cost | Free, under the MIT licence | Free for up to three seats, no card |
Claude Code Router is a gateway each developer runs. Selan is a gateway a team signs in to.
When is Claude Code Router the better answer?
For one developer who wants to try models. CCR is free, its code is open, and everything stays on your own machine. It reaches far more providers than Selan does, through any endpoint that speaks a protocol it knows.
It also does things Selan does not. Routing rules can send a request to a different model by what it contains. Fusion models add vision and web search to existing models. ToolHub and MCP tools are managed in the same app, and it covers agents Selan does not launch, such as Grok CLI, Kimi CLI and Pi.
If nobody else on your team needs the same setup, you do not need Selan.
What changes when a team shares Claude Code Router?
Either every developer runs their own CCR, or somebody runs one for everyone.
- One per laptop means every developer adds the providers and their keys, and keeps their own routing rules and logs.
- One shared server is CCR's Docker image behind Nginx. You then look after its HTTPS, its backups and its upgrades, and keep three credentials apart: the management token, the CCR client keys and the provider keys.
Either way, CCR knows a developer by a client key, and its limits count requests, tokens and images rather than money.
When is Selan the better answer?
When the traffic is a team's coding tools and nobody wants to run a gateway. A developer
runs selan login once, then selan claude, selan codex
or selan opencode. Claude Desktop goes through the same gateway with one
settings file.
An owner connects the company's accounts and keys once, and switches on the models the team may use. Claude, GPT, Kimi, DeepSeek, Qwen and GLM then run through one endpoint, with OpenRouter for the rest. A limit per person applies across every pay-per-use key, and with secret scanning on, a secret it recognises is replaced before the request leaves.
The trade-off is that requests travel through Selan, so if Selan is unavailable those requests fail. Your accounts can still be used directly.
Which providers serve which models is in models and providers, limits per person are on the spend page, and scanning is in the secret scanning docs.
How do you move Claude Code from Claude Code Router to Selan?
CCR applies an agent profile that points Claude Code at its local gateway with a CCR
client key. selan claude sets ANTHROPIC_BASE_URL and
ANTHROPIC_AUTH_TOKEN for the session it launches, in place of whatever the
shell exported.
Connect the same provider accounts in Selan and switch on their models. You can keep CCR on your own machine for trying models, and run the team's work through Selan. Other models in Claude Code are covered in how to run GPT in Claude Code and how to run DeepSeek in Claude Code.
Free for up to three seats, and the Free plan needs no card.
The short version
- Claude Code Router is free, MIT-licensed and runs on your own machine or a server you run.
- It reaches more providers and agents than Selan, and can pick a model per request by rules.
- Shared across a team, each developer is a client key, and someone runs and secures the server.
- Selan is hosted in the EU: one sign-in per person, no provider key on the laptop, and a spend limit per person.
What Claude Code Router does is as its README (github.com/musistudio/claude-code-router, commit 057abaa) and its documentation at ccrdesk.top described it at version 3.1.3, read on 30 October 2026. It changes: check the date before relying on it. What Selan does is as its CLI and docs stated it on that date.