A high-performance AI gateway written in Go, providing a unified OpenAI-compatible API for OpenAI, Anthropic, Gemini, xAI, Groq, OpenRouter, Azure OpenAI, Oracle, Ollama, and more.

Step 1: Start GOModel

docker run --rm -p 8080:8080 \
  -e LOGGING_ENABLED=true \
  -e LOGGING_LOG_BODIES=true \
  -e LOG_FORMAT=text \
  -e LOGGING_LOG_HEADERS=true \
  -e OPENAI_API_KEY="your-openai-key" \
  enterpilot/gomodel

Pass only the provider credentials or base URL you need (at least one required):

docker run --rm -p 8080:8080 \
  -e OPENAI_API_KEY="your-openai-key" \
  -e ANTHROPIC_API_KEY="your-anthropic-key" \
  -e GEMINI_API_KEY="your-gemini-key" \
  -e GROQ_API_KEY="your-groq-key" \
  -e OPENROUTER_API_KEY="your-openrouter-key" \
  -e XAI_API_KEY="your-xai-key" \
  -e AZURE_API_KEY="your-azure-key" \
  -e AZURE_BASE_URL="https://your-resource.openai.azure.com/openai/deployments/your-deployment" \
  -e AZURE_API_VERSION="2024-10-21" \
  -e ORACLE_API_KEY="your-oracle-key" \
  -e ORACLE_BASE_URL="https://inference.generativeai.us-chicago-1.oci.oraclecloud.com/20231130/actions/v1" \
  -e OLLAMA_BASE_URL="http://host.docker.internal:11434/v1" \
  enterpilot/gomodel

⚠️ Avoid passing secrets via -e on the command line - they can leak via shell history and process lists. For production, use docker run --env-file .env to load API keys from a file instead.

Step 2: Make your first API call

curl http://localhost:8080/v1/chat/completions \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gpt-5-chat-latest",
    "messages": [{"role": "user", "content": "Hello!"}]
  }'

That's it! GOModel automatically detects which providers are available based on the credentials you supply.

Example model identifiers are illustrative and subject to change; consult provider catalogs for current models. Feature columns reflect gateway API support, not every individual model capability exposed by an upstream provider.

✅ Supported ❌ Unsupported

Prerequisites: Go 1.26+

1. Create a .env file:

   cp .env.template .env

2. Add your API keys to .env (at least one required).

3. Start the server:

   make run

Includes GOModel + Redis + PostgreSQL + MongoDB + Adminer + Prometheus:

cp .env.template .env
# Add your API keys to .env
docker compose up -d

docker build -t gomodel .
docker run --rm -p 8080:8080 --env-file .env gomodel

GOModel is configured through environment variables and an optional config.yaml. Environment variables override YAML values. See .env.template and config/config.example.yaml for the available options.

Key settings:

Quick Start - Authentication: By default GOMODEL_MASTER_KEY is unset. Without this key, API endpoints are unprotected and anyone can call them. This is insecure for production. Strongly recommend setting a strong secret before exposing the service. Add GOMODEL_MASTER_KEY to your .env or environment for production deployments.

GOModel has a two-layer response cache that reduces LLM API costs and latency for repeated or semantically similar requests.

Hashes the full request body (path + ExecutionPlan + body) and returns a stored response on byte-identical requests. Sub-millisecond lookup. Activate by pointing it at Redis:

# config/config.yaml
cache:
  response:
    simple:
      redis:
        url: redis://localhost:6379
        ttl: 3600   # seconds; default 3600

Or via environment variables: REDIS_URL, REDIS_KEY_RESPONSES, REDIS_TTL_RESPONSES.

Responses served from this layer carry X-Cache: HIT (exact).

Embeds the last user message with all-MiniLM-L6-v2 (local ONNX, zero external dependency) and performs a KNN vector search. Semantically equivalent queries — e.g. "What's the capital of France?" vs "Which city is France's capital?" — return the same cached response without an upstream LLM call.

Expected hit rates: ~60–70% in high-repetition workloads vs. ~18% for exact-match alone.

Responses served from this layer carry X-Cache: HIT (semantic).

Supported vector backends: sqlite-vec (default, embedded), pgvector, qdrant.

Both cache layers run after guardrail/execution-plan patching so they always see the final prompt. Use Cache-Control: no-cache or Cache-Control: no-store to bypass caching per-request.

See DEVELOPMENT.md for testing, linting, and pre-commit setup.

✅ Shipped 🚧 Planned or in progress

Join our Discord to connect with other GOModel users.