Evaluate an AI gateway without losing provider custody

I am evaluating AI gateways for agent workloads and want the model layer to stay hot-swappable.

Checklist I am using:
- One OpenAI-compatible endpoint for Codex, Cursor, OpenClaw, Aider, Continue, OpenHands, and SDK clients.
- Local-first routing where provider API keys, OAuth subscription paths, local Ollama, and private endpoints can stay on my host or Tailnet.
- OpenRouter support as a BYOK-compatible route, without assuming bundled marketplace resale in the subscription.
- Multiple API keys per provider with load balancing and failover, especially on 429s.
- Capability-aware routing for image, audio, video, document, tool, and long-context requests.
- A hosted generated key path for quotas, analytics, and public-edge access when I need it.

Sage Router proof page: https://sagerouter.dev/reddit-ai-gateway-evaluation
60-second setup: https://sagerouter.dev/quickstart
Gateway comparison: https://sagerouter.dev/compare/model-gateways
Max implementation review: https://sagerouter.dev/managed-access?intent=max-implementation

Copy evaluation post

I built and open-sourced the model router I run between my agents and Ollama.

Sage Router exposes one OpenAI-compatible endpoint, routes by task/model capability/provider health/policy, and can fail over between local Ollama, Ollama Cloud through your authorized local Ollama runtime, and other providers you configure.

The Ollama-specific use case:
- keep local Ollama first for privacy, latency, or cost;
- overflow to cloud providers when local capacity is not enough;
- fall back to local Ollama when a cloud provider rate-limits or fails;
- keep provider keys and OAuth/subscription paths on your router host by default;
- route image/audio/video requests only to models that can actually handle those inputs.

30-second local start:
python3 router.py --port 8790
export OPENAI_BASE_URL=http://localhost:8790/v1
export OPENAI_API_KEY=local-router

Ollama route overview:
https://sagerouter.dev/ollama-ai-model-router?utm_source=reddit&utm_medium=community&utm_campaign=sage-router-launch

Public model catalog:
https://sagerouter.dev/models?utm_source=reddit&utm_medium=community&utm_campaign=sage-router-launch

Quickstart:
https://sagerouter.dev/quickstart?utm_source=reddit&utm_medium=community&utm_campaign=sage-router-launch

Repo:
https://github.com/earlvanze/sage-router?utm_source=reddit&utm_medium=community&utm_campaign=sage-router-launch

How are you handling failover between local Ollama and cloud models today? Are people mostly keeping that in each app, using Open WebUI, writing a small gateway, or just accepting provider failures?

Copy r/Ollama post

I built Sage Router because every agent tool I use has its own model config, fallback behavior, and rate-limit failure mode.

The side project became a product: one OpenAI-compatible endpoint for Codex, Cursor, Aider, Continue, OpenHands, OpenAI SDKs, Anthropic-compatible clients, local Ollama, Ollama Cloud through authorized local runtime access, and other BYOK providers.

What it does:
- chooses routes by task, provider health, model capability, latency, and policy;
- fails over on 429s and provider outages;
- load-balances multiple API keys per provider;
- routes image/audio/video inputs only to capable models;
- keeps provider credentials local by default when self-hosted;
- offers hosted generated sk_sage_* keys, quotas, analytics, and reliability routing for teams that want a public edge.

Commercial boundary: Sage Router sells routing infrastructure, not bundled model resale. You still bring authorized provider access unless a future managed-provider beta explicitly satisfies provider terms and unit economics.

Hosted plans are live:
- Lite: $6/month
- Pro: $30/month
- Max: $72/month

Pricing:
https://sagerouter.dev/pricing?utm_source=reddit&utm_medium=community&utm_campaign=sage-router-launch

Create a hosted key:
https://app.sagerouter.dev/account.html?plan=pro&start=create_key&utm_source=reddit&utm_medium=community&utm_campaign=sage-router-launch

Quickstart:
https://sagerouter.dev/quickstart?utm_source=reddit&utm_medium=community&utm_campaign=sage-router-launch

Repo:
https://github.com/earlvanze/sage-router?utm_source=reddit&utm_medium=community&utm_campaign=sage-router-launch

For people launching AI infrastructure side projects: would you lead with the hosted key workflow, the local-first open-source core, or the OpenRouter comparison?

Copy r/SideProject post

export OPENAI_BASE_URL=https://api.sagerouter.dev/v1
export OPENAI_API_KEY=sk_sage_your_key_here

curl "$OPENAI_BASE_URL/chat/completions" \
  -H "Authorization: Bearer $OPENAI_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "sage-router/frontier",
    "messages": [{"role": "user", "content": "Route this through the best healthy model."}]
  }'

# Account/key setup:
# https://app.sagerouter.dev/account.html?plan=pro&start=create_key

Copy 60-second setup proof