StackMap
Subscribe

otari vs plano

Mozilla.ai's self-hosted AI gateway: one OpenAI/Anthropic-compatible endpoint over 40+ providers via any-llm, with virtual keys, pre-dispatch budgets, routing policies and a usage dashboard. — versus — AI-native Envoy-based proxy for agentic apps: agent orchestration via a 4B routing model, smart LLM routing, guardrail filter chains and zero-code OTEL traces. Rust, framework-agnostic.

The curated verdict

Both sit between apps and model providers with routing, failover and guardrails; plano is an Envoy-based agent proxy with a routing model, Otari is a key/budget-centric gateway with a management dashboard.

otariplano
Stars9537.1k
Forks138498
LanguagePythonRust
LicenseApache-2.0Apache-2.0
Last activitytoday26 days ago
Topicsgatewaygateway, orchestration
Curated connections210

otari — the curator's take

Pick it when a team needs to hand out revocable, scoped model keys and enforce spend limits before requests go out — Docker-run with zero config, Postgres when you outgrow SQLite, plus Claude Code hooks for per-developer tracking. It's young (1.0) next to LiteLLM's provider breadth and ecosystem; for a solo dev just pointing a coding CLI at free tiers, a lighter local router is less to operate.

plano — the curator's take

Reach for it when multi-agent code is drowning in hidden middleware — intent routing, provider quirks, guardrail hooks, tracing glue. Plano moves all of that out-of-process: agents are plain OpenAI-compatible HTTP servers in any language, orchestration is YAML plus a purpose-built 4B router model. NOT for a quick single-agent demo (it adds an infra hop and Envoy operational surface), and note the catch: the hosted Plano-Orchestrator LLM is free-tier only — production means running the routing models yourself or getting API keys. If you only need provider unification, LiteLLM is lighter.