Databricks puts Unity Gateway at center of public sector AI governance

Public sector AI adoption is framed as a governance problem rather than a technology one. It describes a familiar sequence: developers adopt third-party coding agents such as Codex and Claude Code, then compliance asks where data is routed and the budget office asks who is driving spend. When neither question can be answered, the project stalls before it scales. Databricks argues that organizations making progress solved governance first and centrally, so each team did not have to self-govern.

Unity Gateway is presented as that central layer inside Databricks. It gives administrators control over which models, coding agents, MCPs and AI tools are available and to whom, with day-zero access to frontier and open-source models but no default rollout to every user. Spending limits and hard caps can be set by user, team or use case, and every request is tracked and attributable. Smart Routing is described as directing tasks to more cost-effective models while maintaining quality. Data residency is handled by geography for Databricks-hosted foundation models, with admins able to require processing within their workspace's geography.

Multi-provider support is also stressed, so teams are not locked into a single vendor while governance retains visibility. Databricks says Unity Gateway is built into Databricks with existing data governance in place, adding AI governance on top without a parallel system or multi-year implementation. The claimed result is that compliance confidence and budget visibility make saying yes to AI easier, though no customer results or independent verification are offered.