Enclaves
Everything runs in a fast, secure sandbox
Connecting agents to your systems means running integration code, sometimes code you didn't write. On Metorial, that code never runs loose. Every integration runs inside an enclave: a fast, secure sandbox that keeps it isolated and monitored. The convenience of connecting tools never comes at the cost of security.
- 01
Sandbox every integration.
All integration code runs inside an isolated enclave. It's always contained and never running directly on shared infrastructure.
- 02
Keep it fast.
Enclaves are built to be lightweight and quick as well as strongly isolated. Strong security doesn't slow down the work agents are doing.
- 03
Isolate down to every interaction.
It isn't one sandbox per customer. Every user, connection, and tool call gets its own enclave. The blast radius of anything going wrong stays tiny.
How enclaves protect you
Sandboxing, network control, and monitoring
Enclaves are the runtime boundary that the rest of Metorial's protections build on.
Every integration contained
Controlled traffic
Monitored and controlled
How the sandboxes work
Fast, secure, and isolated everywhere
- Integrations sandboxedEvery
- Isolation scopePer user, connection, and tool call
- PerformanceFast
- Network rules per enclaveYes
Sandbox every integration. Keep it fast. Isolate every interaction. Contain anything that misbehaves.
FAQ
Answers to common questions about enclaves and how they fit into governed AI agent infrastructure.
What are Metorial enclaves?
Enclaves are the fast, secure sandboxes that run every integration on Metorial. Integration code always runs inside one, isolated and monitored. It never runs loose on shared infrastructure.Does everything really run in a sandbox?
Yes. Every integration runs inside an enclave by default. All the code connecting agents to your systems is always contained.Does sandboxing slow integrations down?
No. Enclaves are built to be fast as well as strongly isolated. You get production-grade security without the latency heavy sandboxing usually adds.How granular is the isolation?
Very. It isn't one sandbox per customer. Every user, connection, and tool call gets its own enclave. The blast radius of any single interaction is minimal.What runs inside enclaves?
First-party integrations, custom MCP servers, and Docker MCP servers all run inside enclaves.How do enclaves handle misbehaving integrations?
Enclaves are sandboxed and monitored. A malicious or misbehaving integration can be contained and its invalid traffic blocked without affecting others.Can I control network access for enclaves?
Yes. Firewalls let you apply network rules to control inbound and outbound traffic for every enclave.