9Router on GCP Marketplace by Meetrix: Deploy a Self-Hosted AI Router With Automatic Fallback

9Router on GCP: One Endpoint for Every AI Coding Tool You Use

Every AI coding setup hits the same wall eventually. Claude Code is pointed at one provider, Cursor at another, Codex is on a separate API key entirely, and the moment one of them hits its rate limit mid-task, whatever you were doing just stops. You either wait it out, or you go rewire a config file while the deadline stays exactly where it was.

Meetrix packaged 9Router as a GCP Marketplace deployment that launches to a single VM in your own Google Cloud project. One OpenAI-compatible endpoint, 40+ providers behind it, automatic fallback when one runs dry, and nginx already tuned for the long-lived streaming connections coding agents depend on. Ready to try it? Launch the Meetrix 9Router listing on GCP Marketplace.

What Is 9Router?

9Router is a self-hosted AI routing proxy, not another model provider. It sits between your coding tools and whatever LLM accounts you have, and exposes a single OpenAI-compatible endpoint for all of them. Point Claude Code, Cursor, Codex, Cline, or Copilot at it once, and it handles the translation between OpenAI, Claude, and Gemini request formats underneath, so the tool never needs to know which provider answered. The container ships as decolua/9router on Docker Hub, and it's an MIT-licensed open-source project.

Day to day, the fallback chain is what matters. Connect a subscription, a cheaper pay-as-you-go option, and a free tier like Kiro AI or DeepSeek Free, and 9Router works through them in that order automatically when one hits quota. The routing follows a three-tier system: subscription first, then cheap paid models (GLM at around $0.60 per million tokens, MiniMax at around $0.20), then free options like Kiro, OpenCode Free, or a new GCP account's $300 trial credit. It monitors quota in real time and switches providers automatically when one runs dry.

There's also a built-in RTK token saver that compresses tool output, things like git diff, grep, ls, and tree results, before it reaches the model, cutting input tokens by roughly 20-40% depending on how verbose your workflow's tool calls are. And it supports multi-account round-robin, so if you have multiple accounts with the same provider, 9Router can rotate between them.

How to Deploy 9Router on GCP

Setting this up by hand means picking a base image, installing Docker, wiring nginx to not buffer server-sent events (coding agents stream, and a default nginx config will silently break that), and scripting your own SSL renewal before a single request gets routed. Through the Marketplace, it's four steps:

1. Find and Launch From GCP Marketplace Open the Meetrix 9Router listing, select your project, and launch the deployment. The default General purpose e2-small (2 vCPU, 2 GB RAM) machine type is enough for a single user or a small team, and the listing's 5-day free trial lets you try it with up to $50 in licence fee credits first. On-demand pricing for that instance in us-central1 runs about $0.0495 per hour, or roughly $36 per month. Spot pricing drops it to around $0.030 per hour.
2. SSL and the Streaming Proxy Are Already Configured nginx ships tuned for Server-Sent Events, no buffering, long timeouts, so streaming responses don't cut off mid-answer. SSL issues automatically through Let's Encrypt once your domain resolves.
3. Wait for Boot, Then Log In Give the instance a few minutes, then open the dashboard URL and log in with the Dashboard initial password you set as a deployment parameter. There's no separate username.
4. Connect a Provider and Point Your Tools at the Endpoint Add a provider from the dashboard, free tier or your own key, then copy your API key from the Endpoint page and set your coding tool's base URL to your domain's /v1 path. The endpoint is the same for every tool: Claude Code, Cursor, Codex, Cline, Copilot, Gemini CLI, Qwen Code, and any other OpenAI or Claude-compatible CLI all point at the same address.

What Meetrix Brings to This Deployment

• 9Router comes pre-pulled on Ubuntu 26.04, and nginx is already set up for streaming. That's the config you'd otherwise be debugging after your first cut-off response.
• Let's Encrypt certificates issue automatically once your domain's DNS points at the instance.
• SQLite state sits on the persistent boot disk, with a one-command script to write a backup.
• A firewall, unattended upgrades, and the standard GCP guest environment are active from the first boot.
• No software license fee beyond the Meetrix licence fee shown before you deploy. The GCP machine cost is the same at ten requests a day or ten thousand; only the machine type changes the bill.
• Support from the engineers who build this image, at support@meetrix.io, with a reply inside 12 hours.

Who Is 9Router on GCP Right For?

This fits anyone whose AI coding setup has outgrown a single provider and a single API key. More specifically, it's a strong match if you're:

• A developer running Claude Code, Cursor, or Codex who's tired of a rate limit stopping work mid-task (or running an agent platform like OpenHands that burns through tokens overnight)
• A team stacking a subscription, a cheap provider, and a free tier, and wants the fallback between them handled automatically instead of by hand
• Someone who priced out OpenRouter's 5.5% fee against a real month of usage and wants to know what self-hosting the same routing looks like instead
• A developer who wants tool output compressed before it hits the model, since input tokens add up fast on long agent sessions
• A compliance-conscious team that needs provider API keys and request history to stay inside its own GCP project, not routed through a third party's servers. If the models themselves also have to stay in-house, vLLM on GCP serves open-weight models on your own GPU VM.
• Anyone standardizing several coding tools on one endpoint instead of maintaining separate provider configs per tool

9Router on GCP by Meetrix vs Alternatives

Resources

9Router on GCP - Developer Guide

The full walkthrough: launching from GCP Marketplace, configuring DNS and SSL, connecting a provider, and pointing your first CLI tool at the endpoint.

Meetrix.IO | Binuka Ranatunga

Under the Hood

What's running once the deployment finishes:

One Thing 9Router Won't Do For You

It won't back itself up on a schedule. The database survives a stop and restart because it lives on the persistent boot disk, but the backup script only runs when you or a cron job tells it to. Skip that step and a bad deployment replacement could cost you routing history and provider configuration you'd rather not rebuild from memory. It's a five-minute cron entry. Set it up on day one.

Choosing which open models to route to? Our roundup of the best self-hosted LLMs is a good place to start.