Go-based LLM gateway. Unifies AWS Bedrock (Runtime + Mantle) behind a single OpenAI-compatible API with virtual keys, budgets, and request logs. Replaces LiteLLM. Runs on i3.Documentation Index
Fetch the complete documentation index at: https://docs.augustin.ai/llms.txt
Use this file to discover all available pages before exploring further.
Access
- Admin UI:
bifrost.augustin.ai— enable password protection under Workspace → Config → Security (no env master key; auth is UI-configured) - OpenAI dialect:
bifrost.augustin.ai/openai/v1/... - Anthropic dialect:
bifrost.augustin.ai/anthropic/v1/... - Native:
bifrost.augustin.ai/v1/...
{provider}/{model_id}, e.g. bedrock/us.anthropic.claude-haiku-4-5-20251001-v1:0 or mantle/openai.gpt-oss-120b.
Services
Single container — no external database. Config and logs live in sqlite files inbifrost/data/.
| File | Purpose |
|---|---|
data/config.json | Seed config, read on first boot only |
data/config.db | Runtime config (providers, virtual keys, budgets, teams) |
data/logs.db | Request logs with 365-day retention |
Configuration
Two paths:- Seed file (
data/config.json) — bootstrap only; after first boot,config.dbis authoritative. To reset, deleteconfig.dband restart. - UI / API — runtime changes via the admin dashboard or
POST /api/providers. This is the expected path.
Providers
Bedrock auth uses a long-term bearer token (AWS_BEARER_TOKEN_BEDROCK in .env) — no sigv4, no STS. The token flows through env.AWS_BEARER_TOKEN_BEDROCK references in the config. Models are listed explicitly per key; wildcards (["*"]) do not match arbitrary model IDs.
Mantle is wired as a custom provider with base_provider_type: openai and base_url: https://bedrock-mantle.us-east-1.api.aws — bifrost appends /v1/chat/completions itself. Same bearer token works for both.
Health
GET /health— process + sqlite pings
Why not LiteLLM
LiteLLM bundles a postgres requirement, 800MB+ Python image, and a default branch namedlitellm_internal_staging. Bifrost is a single Go binary with sqlite, faster cold start, and a coherent provider interface. The tradeoff: some governance features (audit logs, clustering, advanced load balancing) are enterprise-gated, but the OSS core covers routing/virtual keys/budgets.