Danny Kopping
e3ac65aa5f
## Summary Adds an operator-facing migration guide for the AI Bridge to AI Gateway rebrand, as a new docs page under **AI Coder > AI Gateway** (last child in the section). The guide documents: - **Config aliases** (env vars, CLI flags, YAML group keys): old `aibridge` names still work as hidden, deprecated aliases; new `ai_gateway` names are canonical. Includes full env-var mapping tables and the mechanical substitution rules. - **HTTP API**: canonical path is now `/api/v2/ai-gateway`; legacy `/api/v2/aibridge` routes retained. - **Metrics**: prefixes renamed `coder_aibridged_*` -> `coder_ai_gateway_*` and `coder_aibridgeproxyd_*` -> `coder_ai_gateway_proxy_*`. Both old and new names are emitted today, so dashboards keep working; guidance to migrate before the old names are removed, plus an optional `metric_relabel_configs` drop snippet. - **No database changes** and no required config changes to upgrade. Implements the docs/release-notes portion of [AIGOV-240](https://linear.app/codercom/issue/AIGOV-240) (parent: [AIGOV-207](https://linear.app/codercom/issue/AIGOV-207)). ## Notes - Content reflects what actually shipped in the codebase (metrics are *aliased*, not hard-renamed), which differs from the original RFC that assumed a hard rename. - Registered in `docs/manifest.json` with `state: ["ai governance add-on"]` to match sibling pages. --- *This PR was produced by opencode (agent) using the `anthropic/claude-opus-4-8` model, under human direction and review.* --------- Signed-off-by: Danny Kopping <danny@coder.com>
2.3 KiB
AI Gateway
AI Gateway is a smart gateway for AI. It acts as an intermediary between your users' coding agents / IDEs and providers like OpenAI and Anthropic. By intercepting all the AI traffic between these clients and the upstream APIs, AI Gateway can record user prompts, token usage, and tool invocations. AI Gateway supports clients running inside or outside Coder workspaces.
AI Gateway solves 3 key problems:
- Centralized authn/z management: no more issuing & managing API tokens for OpenAI/Anthropic usage.
Users use their Coder session or API tokens to authenticate with
coderd(Coder control plane), andcoderdsecurely communicates with the upstream APIs on their behalf. - Auditing and attribution: all interactions with AI services, whether autonomous or human-initiated, will be audited and attributed back to a user.
- Centralized MCP administration: define a set of approved MCP servers and tools which your users may use.
Note
AI Gateway requires the AI Governance Add-On. As of Coder v2.32, deployments without the add-on will not be able to access AI Gateway.
AI Gateway was previously known as "AI Bridge". Visit Rebranding Migration for details.
When to use AI Gateway
As LLM adoption grows, administrators need centralized auditing, monitoring, and token management. AI Gateway enables organizations to manage AI tooling access for thousands of engineers from a single control plane.
If you are an administrator or devops leader looking to:
- Measure AI tooling adoption across teams or projects
- Establish an audit trail of prompts, issues, and tools invoked
- Manage token spend in a central dashboard
- Investigate opportunities for AI automation
- Uncover high-leverage use cases last
AI Gateway is best suited for organizations facing these centralized management and observability challenges.
Next steps
- Set up AI Gateway on your Coder deployment
- Configure AI clients to use AI Gateway
- Configure MCP servers for tool access
- Audit AI sessions
- Monitor usage and metrics and configure data retention
- Reference documentation