Analysis updated 2026-05-18
Route chat requests across OpenAI, Anthropic, and DeepSeek with one API call.
Automatically fall back to a backup provider if the primary one fails.
Track token usage and cost across every AI provider from one dashboard.
Manage API keys for a team through a web admin panel instead of config files.
| aaronrzh/llm-gateway | craftingcodegig/datamatic | izzzzzi/agent-assh | |
|---|---|---|---|
| Stars | 12 | 12 | 12 |
| Language | Go | Go | Go |
| Setup difficulty | moderate | moderate | easy |
| Complexity | 4/5 | 3/5 | 3/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Needs Docker for PostgreSQL and Redis plus API keys for each provider you want to route to.
LLM Gateway is a traffic router that sits between your application and multiple AI providers such as OpenAI, Anthropic, DeepSeek, and a few Chinese providers. Instead of writing separate code for each provider's API format, you send requests in either OpenAI or Anthropic style, and the gateway automatically translates the request to whatever format the chosen upstream provider expects, including streaming responses. The gateway picks which provider and model to use through configurable routing strategies: by priority order, round robin, lowest latency, or lowest cost. Models can also be grouped into tiers like premium, standard, or economy, so a request can automatically fall back to a similar tier if the first choice is unavailable. If a provider starts failing repeatedly, a circuit breaker temporarily stops sending it traffic and reroutes to healthy alternatives, then tests it again after a cooldown period. Other built-in features include rate limiting to control how many requests go through per second, token usage estimation and logging so you can track spend across providers, and API key management with support for both keys stored in config files and keys added dynamically through Redis. A web-based admin panel lets you manage providers, API keys, and model settings without editing configuration files directly, protected by login authentication. Under the hood it is built in Go using the Gin web framework, with PostgreSQL for storing usage data (with a file-based fallback if the database is unavailable), Redis for caching and dynamic key storage, and separate libraries for token counting and circuit breaking. Getting started involves copying an example environment file with your provider API keys, starting PostgreSQL and Redis with Docker, and running the gateway with a single command. This project would suit developers or small teams who call multiple AI providers and want one consistent endpoint, automatic failover, and centralized cost tracking, rather than building that plumbing themselves for every provider they use.
A self-hosted router that lets you call OpenAI, Anthropic, and other AI providers through one consistent API, with automatic failover and usage tracking.
Mainly Go. The stack also includes Go, Gin, PostgreSQL.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.