9router vs router
Self-hosted gateway pointing any AI coding CLI (Claude Code, Codex, Cursor, Cline) at 40+ providers, with subscription→cheap→free auto-fallback and tool_result compression for 20-40% token savings. — versus — Weave's Go model router: drop-in proxy speaking Anthropic, OpenAI and Gemini APIs that scores each request with an on-box ONNX embedder (Avengers-Pro clusters) and routes to the cheapest fit model.
Same drop-in-endpoint-for-coding-CLIs shape; 9router is about pointing at 40+ providers and subscriptions, weave router about semantic model selection.
| 9router | router | |
|---|---|---|
| Stars | 28k | 4.2k |
| Forks | 5.1k | 116 |
| Language | JavaScript | Go |
| License | MIT | NOASSERTION |
| Last activity | 6 days ago | yesterday |
| Topics | gateway, coding | gateway |
| Curated connections | 11 | 5 |
9router — the curator's take
The 'never hit a rate limit again' gateway: run it on localhost, point Claude Code / Codex / Cursor / Cline / Copilot at its OpenAI-compatible endpoint, and it round-robins your accounts and cascades Subscription → cheap ($0.2-0.6/1M) → free (Kiro, OpenCode) providers so a job never dies mid-flight, while RTK compresses tool_result payloads (git diff, grep, ls) to shave 20-40% of tokens. Best when you juggle several provider subscriptions/keys and keep exhausting quota. NOT for you if you want one stable premium model (free-tier fallbacks vary in quality/availability), if routing traffic through third-party free providers raises data-privacy concerns, or if you want savings from smarter code retrieval rather than payload compression. Overlaps heavily with lynkr — pick 9router for free/multi-account fallback breadth, lynkr for tool-stripping, semantic caching and local-model routing.
router — the curator's take
Choose it when the goal is *smart* routing, not just multi-provider fan-out: an in-process embedder classifies each action and picks a model per request in under 50ms, with a `/v1/route` endpoint to inspect the decision and OTLP traces out of the box. `npx @weave-os/router` wires Claude Code, Codex, opencode or pi in one step; self-hosting needs Postgres (and Pub/Sub for multi-replica). Don't reach for it if you want a plain gateway (litellm), free-tier pooling (omniroute), or to route through subscription CLIs (cliproxyapi) — and note the Elastic License v2, which is not OSI open source, and that the frictionless quickstart is the hosted service.