Sandboxes
Try changes before they reach production
Changing anything that agents depend on is risky when production is the only place to test it. Sandboxes give you separate, fully functional environments for development, staging, and testing. You can try new integrations, skills, and configurations, see how they behave, and only promote them to production once you're confident.
- 01
Test without touching production.
Try new integrations, skills, workflows, and configurations in an isolated environment that behaves like the real thing, with no impact on what's live.
- 02
Promote changes when they're ready.
A configuration that works in a sandbox can be committed to production, so what you tested is what you ship.
- 03
Keep environments separate.
Each sandbox has its own access control and permissions, so people can experiment safely without affecting production or one another.
How sandboxes fit your workflow
From experiment to production
Sandboxes give every change a place to be tried, governed, and promoted.
A real environment
Separate access
Commit to production
What sandboxes give you
Test freely, ship confidently
- Environments for dev, staging, and testYes
- Impact on productionNone
- Separate access controlYes
- Available onPro and Enterprise
Spin up an isolated environment. Test new integrations and skills. Keep production untouched. Promote what works.
FAQ
Answers to common questions about sandboxes and how they fit into governed AI agent infrastructure.
What is a sandbox in Metorial?
A sandbox is an isolated, fully functional environment for development, staging, and testing. You can try changes in it without affecting your production setup.What can I test in a sandbox?
New integrations, skills, workflows, and configurations. Because a sandbox behaves like production, you can see how a change will work before it goes live.Does using a sandbox affect production?
No. Sandboxes are separate environments. Nothing you do in one touches production until you choose to promote it.Can I move changes from a sandbox to production?
Yes. A configuration that works in a sandbox can be committed to production, so what you tested is what you ship.Do sandboxes have their own access control?
Yes. Each sandbox has separate access control and permissions through policies and access control, so people can experiment without affecting production or each other.How are sandboxes different from enclaves?
Sandboxes are environments where you test changes before production. Enclaves are the secure, isolated compute that every integration and tool call runs inside. Sandboxes are about safe testing; enclaves are about runtime security.Which plans include sandboxes?
Sandboxes are included with Pro and Enterprise plans.
