Case Study

# How Unity Made Its Governed Metadata Callable by AI with Collate®

![](data:image/svg+xml,%3csvg%20xmlns=%27http://www.w3.org/2000/svg%27%20version=%271.1%27%20width=%27310%27%20height=%27400%27/%3e)![Form Header](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)

![Form Header](/_next/image?url=%2Fimages%2Febook%2Funity-case-study-form-header.webp&w=640&q=75)

Get your Copy

For years, most teams treated metadata as documentation: something people had to find and read before any decision could be made. That model does not scale, and it does not plug into AI. Teams that want to put AI to work on their data need governed metadata a system can call directly, not a copy of the docs that drifts out of date.

Learn how Unity, the real-time 3D engine behind more than 23 billion ad impressions a month, made its governed metadata callable by AI through the Collate MCP Server, turning a multi-day compliance review into a seven-minute answer, including:

*   How Unity turned metadata from documentation people read into infrastructure that AI can call, through the Collate MCP Server
*   How the first agent built on that foundation, an internal Slack bot, cut compliance review from days to about seven minutes on 100% of Unity Ads data products
*   Why Unity moved from self-hosted OpenMetadata to managed Collate: managed operations, actionable data-quality alerts, and a callable context layer that scales without adding headcount