UnifyRoute – Self-hosted OpenAI-compatible LLM gateway with failover
Drop-in OpenAI API gateway with failover—LiteLLM does this but this has a dashboard.
AI gateway written in Go. Lightweight unified OpenAI-compatible API for OpenAI, Anthropic, Gemini, Groq, xAI & Ollama. LiteLLM alternative with observability, guardrails, streaming, costs and usage tracking.
17MB Docker image versus LiteLLM's 746MB is a genuine engineering win.
Backend developers building AI-powered applications
LiteLLM · Helicone · Portkey
I’ve been building GoModel since December with a couple of contributors. It's an open-source AI gateway that sits between your app and model providers like OpenAI, Anthropic or others.
I built it for my startup to solve a few problems : - track AI usage and cost per client or team - switch models without changing app code - debug request flows more easily - reduce AI spendings with exact and semantic caching
How is it different? - ~17MB docker image - LiteLLM's image is more than 44x bigger ("docker.litellm.ai/berriai/litellm:latest" ~ 746 MB on amd64) - request workflow is visible and easy to inspect - config is environment-variable-first by default
I'm posting now partly because of the recent LiteLLM supply-chain attack. Their team handled it impressively well, but some people are looking at alternatives anyway, and GoModel is one.
Website: https://gomodel.enterpilot.io
Any feedback is appreciated.
Drop-in OpenAI API gateway with failover—LiteLLM does this but this has a dashboard.
LiteLLM and OpenRouter already solve multi-provider routing better and have production users.
Go gateway with circuit breakers, but auth isn't production-ready yet.
Stripped-down Portkey fork handling protocol translation for 77 providers without enterprise bloat.
Yet another PII redaction proxy when Lakera and Portkey already dominate this space.
Runs as a single binary with embedded SQLite and zero-config start, acting as a transparent, provider-agnostic proxy that logs model, tokens, latency, cost and API key hashes while leaving full body capture opt-in. It also proxies streaming responses in real time and exposes stable JSON analytics endpoints — a practical, instrumentable way to get reproducible, audit-ready traces for real LLM traffic, though long-term value depends on how it handles provider edge-cases and SDK compatibility.