Skip to main content
If your data has to stay on your own infrastructure, Matrices is built so the data plane can run inside your own VPC while the control plane stays hosted by us.
Coming soon. This capability is part of where Matrices is heading, but its public API is not generally available yet. The shapes shown here describe the intended contract and may change before release.
The split already exists in the design; what’s missing is the packaging and setup to hand it to you. If you need this, get in touch. Here’s where it’s headed.

​
What runs where

The control and data plane split makes this possible, and the line between the two is already clean. Everything that runs, and everything it stores, lives on your side. The shared configuration stays on ours.

​
How the two halves talk

Very little crosses the line.
  • Down: the control plane sends a signed snapshot of the turn: the agent profile, the roles it selects, and the toolsets involved. The data plane checks the signature and runs exactly that.
  • Up: the data plane sends audit, usage, and event data. Raw credentials and sandbox files never go into a model prompt or a configuration snapshot.
Each turn’s configuration is signed and fixed when the turn starts, so editing a profile or role can’t change work already running. The next turn picks up the new configuration.