Route traffic to the right provider. Automatic fallback. Zero config. Then let Correctover verify the responses are actually correct.
# Start in one command local-gateway --providers deepseek,kimi,claude # Point any OpenAI-compatible client export OPENAI_BASE_URL=http://localhost:8765/v1
LocalGateway routes your requests. Correctover verifies your responses. Two different problems, one seamless stack.
| LocalGateway | Correctover | |
|---|---|---|
| Layer | Network (proxy) | Application (SDK) |
| Role | "The wire operator" | "The quality inspector" |
| Does | Routes traffic to the right provider | Verifies responses are actually correct |
| On failure | SSE fallback to next provider | 6-dimensional contract validation + MAPE-K |
| Complexity | 73 lines, pure urllib | 37 modules, 100 public APIs |
| Overhead | Network hop only | P50 22µs validation |
| Moat | Anyone can fork | Core壁垒 — not replicable |
| Price | Free & Open Source | Pro / Enterprise |
LocalGateway is the problem amplifier — use it and you'll discover why verification matters.
pip install local-gateway — start routing in 30 seconds. Nine providers, zero config.
"Every time I failover, I don't know if the new provider's response is correct."
"I need to verify the response content, not just the HTTP status code."
pip install correctover — add the verification layer on top.
Automatic model name mapping across providers. No manual config needed.
# 1. Install pip install local-gateway # 2. Set your API keys export DEEPSEEK_API_KEY=sk-... export KIMI_API_KEY=sk-... # 3. Start the gateway local-gateway --providers deepseek,kimi # 4. Point your app export OPENAI_BASE_URL=http://localhost:8765/v1 # Done. Automatic fallback on failure. # Need response verification? → pip install correctover
Failover switches providers. Correctover verifies the response is correct.