Deployment
Routeplane runs as a local proxy — a single binary on your machine. It’s fully self-hosted under Apache 2.0 with your own provider keys. There is no cloud dependency, no data egress, and no vendor lock-in.
Routeplane Cloud is on the roadmap as an optional managed overlay. Today, everything runs locally. See STRATEGY.md for the product roadmap.
What you get out of the box
Section titled “What you get out of the box”| Capability | Self-hosted (current) |
|---|---|
OpenAI-compatible API endpoint (127.0.0.1:4356) |
✅ |
| Subscription-first routing (Copilot, Grok, etc.) | ✅ |
| BYOK (bring your own provider keys) | ✅ |
| Model fallback & provider selection | ✅ |
Model presets (@fast, @standard, @heavy) |
✅ |
| OAuth login (device-code flow) | ✅ |
| Guardrails (prompt/output redaction) | ✅ |
| Observability (OTLP trace + metric export) | ✅ |
| MCP gateway | ✅ |
| Structured outputs | ✅ |
| Config hot-reload | ✅ |
Roadmap (Cloud features)
Section titled “Roadmap (Cloud features)”The following are planned for Routeplane Cloud, a managed overlay for teams:
- Managed provider network (no upstream keys needed)
- Team config sharing and audit logs
- Per-user rate limits and spend tracking
- SSO and enterprise compliance
See STRATEGY.md for the full roadmap and timeline.