Atlas Cloud is a full-modal AI inference platform that gives developers a single AI API to access video generation, image generation, and LLM APIs. Instead of managing multiple vendor integrations, you connect once and get unified access to 300+ curated models across all modalities.
Thank you to Krill AI for sponsoring this project. Krill provides official, stable, high-speed API relay services for GPT, Claude, Gemini, and a wide range of Chinese models, with enterprise customization, invoicing support, and dedicated technical support 16 hours a day, 7 days a week. Its optimized WebSocket connection can deliver a faster time to first token.
Register through this link and enter the llm-proxy coupon code when topping up to receive 23% off your first Codex plan purchase.
Try llm-proxy with zero local setup on Bloome:
Quick start,
one click from your browser or phone, easy to share with your team.
📖 Project Introduction
All-in-one AI Development Platform
llm-proxy is the AI gateway that lets you switch between model providers without changing a single line of code.
Whether you're using OpenAI SDK, Anthropic SDK, or any AI SDK, llm-proxy transparently translates your requests to work with any supported model provider. No refactoring, no SDK swaps—just change a configuration and you're done.
What it solves:
🔒 Vendor lock-in - Switch from GPT-4 to Claude or Gemini instantly
🔧 Integration complexity - One API format for 10+ providers
📊 Observability gap - Complete request tracing out of the box
💸 Cost control - Real-time usage tracking and budget management
# Download and extract (macOS ARM64 example)
curl -sSL https://github.com/mutallipp/llm-proxy/releases/latest/download/llm-proxy_darwin_arm64.tar.gz | tar xz
cd llm-proxy_*
# Run with SQLite (default)
./llm-proxy
# Open http://localhost:8090
# First run: Follow the setup wizard to initialize the system (create admin account, password must be at least 6 characters)
That's it! Now configure your first AI channel and start calling models through llm-proxy.
Zero-Code Migration Example
Your existing code works without any changes. Just point your SDK to llm-proxy:
from openai import OpenAI
client = OpenAI(
base_url="http://localhost:8090/v1", # Point to llm-proxy
api_key="your-llm-proxy-api-key" # Use llm-proxy API key
)
# Call Claude using OpenAI SDK!
response = client.chat.completions.create(
model="claude-3-5-sonnet", # Or gpt-4, gemini-pro, deepseek-chat...
messages=[{"role": "user", "content": "Hello!"}]
)
Switch models by changing one line: model="gpt-4" → model="claude-3-5-sonnet". No SDK changes needed.
# Extract and run
unzip llm-proxy_*.zip
cd llm-proxy_*
# Set environment variables
export LLM_PROXY_DB_DIALECT="tidb"
export LLM_PROXY_DB_DSN="<USER>.root:<PASSWORD>@tcp(gateway01.us-west-2.prod.aws.tidbcloud.com:4000)/llm-proxy?tls=true&parseTime=true&multiStatements=true&charset=utf8mb4"
sudo ./install.sh
# Configuration file check
llm-proxy config check
# Start service
# For simplicity, we recommend managing llm-proxy with the helper scripts:
# Start
./start.sh
# Stop
./stop.sh
📖 Usage Guide
Unified API Overview
llm-proxy provides a unified API gateway that supports both OpenAI Chat Completions and Anthropic Messages APIs. This means you can:
Use OpenAI API to call Anthropic models - Keep using your OpenAI SDK while accessing Claude models
Use Anthropic API to call OpenAI models - Use Anthropic's native API format with GPT models
Use Gemini API to call OpenAI models - Use Gemini's native API format with GPT models
Automatic API translation - llm-proxy handles format conversion automatically
Zero code changes - Your existing OpenAI or Anthropic client code continues to work
1. Initial Setup
Access Management Interface
http://localhost:8090
Configure AI Providers
Add API keys in the management interface
Test connections to ensure correct configuration
Create Users and Roles
Set up permission management
Assign appropriate access permissions
2. Channel Configuration
Configure AI provider channels in the management interface. For detailed information on channel configuration, including model mappings, parameter overrides, and troubleshooting, see the Channel Configuration Guide.
3. Model Management
llm-proxy provides a flexible model management system that supports mapping abstract models to specific channels and model implementations through Model Associations. This enables:
Unified Model Interface - Use abstract model IDs (e.g., gpt-4, claude-3-opus) instead of channel-specific names
Intelligent Channel Selection - Automatically route requests to optimal channels based on association rules and load balancing
Flexible Mapping Strategies - Support for precise channel-model matching, regex patterns, and tag-based selection
Priority-based Fallback - Configure multiple associations with priorities for automatic failover
For comprehensive information on model management, including association types, configuration examples, and best practices, see the Model Management Guide.
4. Create API Keys
Create API keys to authenticate your applications with llm-proxy. Each API key can be configured with multiple profiles that define:
Model Mappings - Transform user-requested models to actual available models using exact match or regex patterns
Channel Restrictions - Limit which channels an API key can use by channel IDs or tags
Model Access Control - Control which models are accessible through a specific profile
Profile Switching - Change behavior on-the-fly by activating different profiles
For detailed information on API key profiles, including configuration examples, validation rules, and best practices, see the API Key Profile Guide.
5. AI Coding Tools Integration
See the dedicated guides for detailed setup steps, troubleshooting, and tips on combining these tools with llm-proxy model profiles:
dev 与 prod 状态完全隔离:dev DB 库名为 llm-proxy-dev(独立 PostgreSQL 库),dev 容器名为 llm-proxy-dev,互不冲突。.env.dev 是可提交的默认配置;首次运行前,在被 Git 忽略的 .env.dev.local 写入完整 LLM_PROXY_DB_DSN。如需以线上库的最新表结构初始化空 dev 库,执行 make dev-db-sync-schema:它同步表、索引、约束与序列,但不会复制业务数据、API Key、OAuth token 或渠道 Cookie;dev 库非空时会拒绝执行,避免误覆盖开发数据。需要完整复刻线上数据时,执行 make dev-db-sync-full:它会先停止 dev、销毁并重建 dev DB,再导入完整 prod 快照,包括 API Key、OAuth token 与渠道 Cookie,且会覆盖现有 dev 数据。