9Router

9Router runs entirely on your local machine as a self-hosted proxy. Your API keys and request payloads never leave your computer unless you explicitly enable Cloud Sync or deploy to a VPS. The debug request log is stored locally and can be toggled off at any time.

9Router checks quota availability in real time across all configured accounts. When a Tier 1 subscription provider hits its rate limit or token quota, 9Router automatically routes the next request to the cheapest available Tier 2 provider (e.g., GLM at $0.6/1M tokens), then falls to a fully free Tier 3 provider like Kiro or OpenCode Free — all without any interruption to your coding session.

RTK (Result Token Kompressor) inspects the first 1 KB of each tool_result block and applies format-specific filters — git-diff, grep, find, ls, tree, and more — to remove redundant characters and structure. If any filter increases the token count or throws an error, RTK silently falls back to the original text, making the process completely safe and lossless.

Yes. For standard API-key-based tools like Cursor, Cline, and Continue, you simply point the base URL to http://localhost:20128/v1. For subscription-based IDEs like GitHub Copilot and Kiro IDE, 9Router uses its MITM bridge to intercept traffic at the network level, allowing you to redirect those subscriptions to any backend provider.

9Router supports localhost (default), VPS/cloud deployment via PM2, Docker (multi-platform: linux/amd64 and linux/arm64), Cloudflare Workers edge tunnel, and Tailscale Funnel for stable TLS. Docker images are published on both Docker Hub and GitHub Container Registry.