How it works
From a map of your data platform to a pull request your team merges, with the same map served over MCP.
1. Map
Datapace builds one map of your data: where it lives, the cloud it runs on, the jobs that move it, the projects and dashboards that use it. Each part carries its usage and its cost. See integrations for what it can read. Which systems it reads on your platform is agreed with your team.
2. Find
On the map, you see what costs more than it should: idle capacity, jobs that copy everything, data nobody reads. Each finding becomes a business case with its saving.
3. Propose
For each case, an agent prepares the change as a pull request in your repository. Your team reviews it and merges it. Datapace applies nothing on its own.
4. Serve
The same map is available to your own agents and copilots over MCP, with any LLM.
Last updated on October 25, 2026
