Databricks Unity AI Gateway hits GA: a governance guide

If your team has been stitching together access to Anthropic, OpenAI, and Gemini models across a dozen notebooks with no central audit trail and no one quite sure what the monthly AI bill is, Databricks shipped something for you. Unity AI Gateway reached general availability on August 4, 2026, bringing provider routing, MCP server governance, spend caps, and usage lineage under the Unity Catalog umbrella. The GA covers the core gateway: routing traffic, enforcing access controls, and reporting cost. Some of the more interesting capabilities, including Smart Routing and agent services, remain in Beta. If you are a workspace owner who influences the bill, this is the moment to decide what goes through the gateway and what stays direct.

What does Unity AI Gateway actually do?

Unity AI Gateway is the Databricks governance solution for enterprise AI, built as a component of Unity Catalog. It sits between your applications, agents, and coding assistants and the model providers they call. Every AI request flows through the gateway, which applies your policies, records what happened, and reports back to a central dashboard.

The four core capabilities are straightforward. You control which AI services teams can use, from external LLM providers to internal MCP servers. You route and manage AI traffic across providers, reserving expensive frontier models for tasks that need them. You govern MCP servers to control access and costs. And you monitor usage, cost, access, and lineage from one place.

The gateway supports frontier models from Anthropic, OpenAI, Gemini, Kimi, and GLM through a single-query API, according to the Databricks GA announcement. That means a developer can swap the model behind a request without rewriting application code: change a config, not a codebase.

What makes this different from calling a provider API directly is that Unity Catalog's identity and permissions model extends to every AI interaction. The same RBAC you use for tables and volumes now covers AI traffic. A user who loses access to a model sees that enforced at the gateway, not just at the application layer. The gateway also provides end-to-end observability and granular cost attribution across models, providers, teams, and applications, all centralized in Unity Catalog.

How does provider routing work?

Unity AI Gateway exposes a single API endpoint that fronts multiple providers. Instead of pointing your application at a provider URL, you point it at the gateway. The gateway then forwards the request to the provider you configured.

In its GA form, routing is policy-based: you define which models are available and which teams can use them. A team building a coding assistant might get access to Claude and GPT-4, while a team running summarization gets routed to a cheaper model. You make the routing decision in configuration, and the gateway enforces it.

The more interesting piece is Smart Routing, which remains in Beta. Smart Routing dynamically routes each request to the right model based on factors like quality, cost, performance, availability, and budget. The gateway evaluates each incoming request and picks the model that best fits your configured trade-offs, reserving the most capable and expensive models for tasks that need them while routing routine work to more efficient options. Databricks says interested teams should contact their account team to join the Beta.

Here is what a basic gateway query looks like in SQL, using the Databricks ai_query function:

-- Query a model registered in Unity Catalog through the gateway
SELECT ai_query(
  'my_catalog.my_schema.my_claude_model',
  'Explain RBAC in one sentence'
);

The ai_query function sends the request through the gateway, which applies your policies, forwards it to Anthropic, and logs the token usage and cost. Swap the model name and the same function hits a different provider.

The chart above shows which Unity AI Gateway capabilities shipped as GA versus Beta in the August 2026 release. The four GA capabilities are core gateway routing, provider integration via the single-query API, spend budgets and caps, and usage monitoring with Genie-powered dashboards. The four Beta capabilities are service policies, agent services, Smart Routing, and MCP connector integration.

What does it cost to run?

Here is the part that matters to anyone who signs off on the bill. Unity AI Gateway itself is a feature of Unity Catalog, not a separately priced SKU. You do not pay a gateway subscription fee. What you do pay for is the compute and token consumption that flows through it.

There are two cost surfaces to track:

1. Provider token costs: Every request routed through the gateway to an external provider like Anthropic or OpenAI incurs that provider's per-token pricing. The gateway records these costs in its dashboards, but the billing flows through your existing provider relationship.
2. Databricks compute: If you are running Databricks-hosted models via Foundation Model APIs, you pay DBUs based on the provisioned throughput. The gateway does not add a surcharge on top of provider token costs.

Cost surface	What you pay	Who bills you
External provider tokens	Per-token pricing from the provider	Anthropic, OpenAI, etc.
Databricks-hosted models	DBUs based on provisioned throughput	Databricks
Gateway infrastructure	No separate charge; included in Unity Catalog	N/A

The financial value proposition is spend control, not spend reduction. The gateway gives you proactive budgets and hard spend caps so a runaway agent cannot quietly burn through a provider quota. You set a monthly cap per team or per application, and the gateway enforces it at runtime. The out-of-the-box dashboards surface cost by model, team, and application. That attribution is the real win for a workspace owner who has been trying to explain an unpredictable monthly AI bill to finance.

How do you set it up?

Setting up Unity AI Gateway requires admin access to Unity Catalog. The high-level flow:

1. Register providers and models in Unity Catalog so the gateway knows what is available.
2. Define service policies that map teams or applications to allowed models. Note that service policies remain in Beta.
3. Set spend budgets per team or application using the gateway's budget configuration.
4. Point your applications at the gateway endpoint instead of calling providers directly.

For MCP servers, the August 6 release note confirms that all Databricks-managed MCP connectors for Genie One and Genie Code have migrated to Unity AI Gateway. If your team uses these connectors, users must reauthenticate to continue using them. A notification in Genie prompts impacted users to reconnect.

Here is how you might call the gateway from a Python application using a REST endpoint:

import requests

# Route a completion through Unity AI Gateway
response = requests.post(
    "https://<workspace>.cloud.databricks.com/api/2.0/ai-gateway/query",
    headers={"Authorization": f"Bearer {token}"},
    json={
        "model": "my_catalog.my_schema.my_claude_model",
        "messages": [
            {"role": "user", "content": "Summarize this table schema"}
        ]
    }
)

# The gateway logs the request, applies policies,
# and returns the response with token usage metadata
result = response.json()
print(result.get("usage", {}).get("total_tokens"))

The API contract is the same whether the model is hosted on Databricks or external. The gateway abstracts the provider difference. For a deeper walk through the budget and spend-cap mechanics, read our Unity AI Gateway budgets guide.

What is still in Beta and what should you wait on?

Several capabilities shipped as Beta alongside the GA core. Service policies, the engine that maps who-can-use-what at a fine-grained level, are still in Beta. You can register models and route traffic in GA, but the policy enforcement layer may not be fully stable. Agent services, including agent runtime policies and agent-level spend controls, also remain in Beta.

Smart Routing, the dynamic per-request model selection feature, is in Beta. Static routing where you pick the model is GA. MCP connector integration, while migrated to the gateway, is tagged Beta.

If your use case is routing all coding assistant traffic through one audited endpoint with a spend cap, the GA core covers you. If you want the gateway to automatically pick the cheapest model that meets a quality bar on every request, you are waiting on Smart Routing to leave Beta.

When is it the wrong choice?

Unity AI Gateway is not a model hosting platform. If your workload is a single Databricks-hosted model serving internal traffic with no external providers involved, the gateway adds a hop without adding much value. You already get lineage and access control through Unity Catalog and Model Serving.

It is also not a replacement for a full LLM observability platform. The dashboards surface cost and access, which is valuable, but if you need deep evaluation metrics like answer faithfulness, retrieval quality, or hallucination tracking, you will need a dedicated eval tool on top.

Finally, if your team has not yet adopted Unity Catalog for data governance, the gateway is not a shortcut. It depends on Unity Catalog's identity and permissions model. No Unity Catalog, no Unity AI Gateway.

What should you do this week?

If you are already on Unity Catalog and routing AI traffic to external providers, start planning the migration now.

1. Inventory every place your code calls an external provider API directly. Each one is a candidate for gateway routing.
2. Register your models in Unity Catalog so the gateway can route to them.
3. Set a spend cap on each team or application before you route production traffic. A cap you set before launch is a cap you control. A cap you set after an incident is a cap you explain to finance.
4. Reauthenticate MCP connectors if your team uses Genie One or Genie Code. The migration to the gateway requires users to reconnect.
5. Watch the dashboards for a week before you turn on Smart Routing. You need baseline cost data to know whether dynamic routing is actually saving you money.

The bottom line

Unity AI Gateway at GA is a governance layer, not a performance layer. It will not make your models faster or cheaper. What it does is give you one audited, policy-enforced path between your teams and the model providers they use, with spend caps and lineage that finance can actually read. If you are spending real money on external LLM providers through Databricks, the GA core is ready to use. The Smart Routing Beta is the feature to watch, but do not wait for it to start governing your AI traffic.

Sources

• Databricks , August 2026 release notes
• Databricks , Unity AI Gateway is Generally Available
• Databricks Community , Announcement: Unity AI Gateway is Generally Available