Why a separate layer
Agents change every month. Governance shouldn't.
Frameworks, models and agent tools will keep changing. The rules for what an agent may do, for whom, and at what cost belong in one layer that outlives them. That is why Magertron governs the calls rather than the agents. See the MCP control plane and AI spend control in detail, or build an agent on it.
Questions
Frequently asked
What is Magertron's AI Orchestrator?
A Kubernetes-native governance platform for AI agents. Every MCP tool call, model call and API call your agents make passes through it, where it is identified, authorized, priced, limited and audited.
Is the AI Orchestrator an agent framework?
No. It does not build or run your agents' reasoning loop. It sits underneath whatever framework or harness you use, as the layer the agents call through.
Is it a model router?
No. It does not choose models on your behalf. It governs the models and tools you decide to use.
Where does it run?
In your own Kubernetes cluster, on any cloud, on-premises or air-gapped, with a free tier up to 20 servers.
Who is it for?
Platform, security and finance teams that need to let agents work in production while keeping control of what they can reach, what they spend, and who approved it.