Install guide
Install 9router only after choosing the route you actually need
A good 9router install is not just a command. It is a decision about where credentials live, which coding tool connects first, what fallback models are allowed, and how much token compression you want.
For buyers and operators who want a practical install path without hiding operational tradeoffs.
Choose the install shape
Use npm for a fast local trial. Use source when you want to inspect or modify the app. Use Docker when you need repeatable persistence. Use a secured cloud endpoint only after auth, TLS, and secret rules are clear.
The first-screen planner on this site mirrors that decision because installation and conversion should not be separate worlds.
- Local trial: npm install -g 9router && 9router.
- Source: clone the repository, install dependencies, set PORT=20128, then run the app.
- Docker: mount a persistent data directory and expose port 20128.
- Team endpoint: define API keys, dashboard auth, logging policy, and provider ownership first.
Connect one tool first
Do not connect every client on day one. Start with Codex, Cursor, Antigravity, or Claude Code, confirm the /v1 endpoint works, then add fallback routes.
A controlled first client makes debugging easier and prevents scattered credentials before the team understands the router.
What success looks like
A successful install has a visible dashboard, a working /v1 models or chat endpoint, one validated provider, a configured API key for the client, and a fallback path that does not surprise the team.
Once that is true, the paid Pro path makes sense because the work shifts from installation to operation.
Common questions
What is the safest first install?
For most users, a local npm trial or Docker container on a private machine is safer than exposing a remote router immediately.
Do I need every provider before starting?
No. Start with one provider and one client. Add cheap and free backups once the baseline path works.
Why does the site ask about deployment before checkout?
Deployment shape determines the support and policy work you actually need. That is why Pro annual is selected for serious team setups.