Use the 9router GitHub project as the technical source of truth

What to inspect first

Start with the README, Docker notes, architecture document, provider constants, and the OpenAI-compatible API routes. Those files reveal how requests enter 9router, how provider credentials are selected, and where fallback decisions are made.

A serious evaluation should check the pieces that affect reliability: token refresh, account cooldown, combo model fallback, persistent data, request logging, and dashboard authentication.

• The upstream project is decolua/9router on GitHub.
• Core compatibility routes live under the Next.js API surface.
• Routing, streaming, provider execution, and translation are handled by shared SSE modules.
• Local state is stored in a JSON database under the configured data directory.

How the managed site helps

GitHub answers whether the tool is technically plausible. A buying page should answer whether your first rollout is scoped, safe, and valuable enough to fund.

9router Space turns that decision into a route plan: target tool, provider stack, token policy, deployment posture, and checkout path. The public source stays visible, while the purchase flow stays focused.

Trust model for teams

Provider keys, OAuth tokens, request logs, and local databases are sensitive. Before a team routes real coding traffic, define who can access the dashboard, where data is stored, and how credentials are rotated.

The middle Pro annual plan is selected by default because most teams need rollout help, fallback policy, and provider review before they need a custom enterprise setup.

Common questions