Hi HN — I built LunarGate, a self-hosted OpenAI-compatible LLM gateway written in Go.
It exists because once you add multiple model providers, retries, fallbacks, routing, and observability logic start leaking into app code.
LunarGate moves that into one gateway layer.
Current features:
- provider/model routing
- retries and fallbacks
- circuit breakers
- optional caching and rate limiting
- hot-reloadable YAML config
- optional observability
- complexity-aware routing
Important caveat: inbound auth/security is not production-complete yet, so it should run behind an auth-enforcing proxy/gateway. I’m actively working on that now.
I also have a long roadmap, but I’m trying to figure out what matters most in practice. If you’ve run something like this before, I’d especially love to know: what 1–2 things would you need before trusting a gateway like this in production?
It exists because once you add multiple model providers, retries, fallbacks, routing, and observability logic start leaking into app code.
LunarGate moves that into one gateway layer.
Current features: - provider/model routing - retries and fallbacks - circuit breakers - optional caching and rate limiting - hot-reloadable YAML config - optional observability - complexity-aware routing
Important caveat: inbound auth/security is not production-complete yet, so it should run behind an auth-enforcing proxy/gateway. I’m actively working on that now.
I also have a long roadmap, but I’m trying to figure out what matters most in practice. If you’ve run something like this before, I’d especially love to know: what 1–2 things would you need before trusting a gateway like this in production?
It’s open source: https://github.com/lunargate-ai/gateway
Docs / site: https://docs.lunargate.ai/ https://lunargate.ai