Environments
Create an isolated environment from your production space. Test automations, workflows, and configuration changes safely, without jeopardizing live content or end-user experiences.
| #1 Enterprise Headless CMS
Don't let one "small change" break everything.
Pushing changes directly to a shared space can leave little room for safe iteration and validation.
Component creation
A simple test of a new component can unintentionally break a live layout.
Content updates
An update to content workflows in the product environment could break the end-user experience.
Automation & AI
MCP Servers, AI-driven automations, and scripts pointed at production can make changes you can't easily undo.
Introducing: native environments for Storyblok
Test, train, and validate in an isolated copy of your production space.
-
Test automations and AI agents
Point FlowMotion, the MCP Server, or your own scripts at an environment instead of production. See exactly what an automation does across real content and components before you let it near live stories.
-
Transform content safely
Refactor or migrate content structures in parallel environments. Map, test and validate your new setup before going live. Guaranteeing no downtimes and no risk.
-
Validate new components
Enable and test new components in a controlled environment first. Confirm behavior, styling and structure. Keep production clean and consistent.
-
Test configuration and permission changes
Try schema changes, datasource updates, and role or access adjustments in a copy of your space. Confirm the setup behaves as expected before you change anything for your team.
-
Contain what integrations can reach
Scope personal access tokens to a single environment. Third-party tools, agents, and experiments get real data to work against and no path to your production space.
-
Train & onboard your team
Create safe, isolated spaces where new team members can learn, experiment and explore real project setup - all without having to touch live environments. Perfect for onboarding devs, editors and designers.
-
Sync front-end & CMS updates
Test front-end releases alongside matching CMS components. Ensure perfect alignment and functionality.
-
Reproduce issues with real content
Investigate a rendering bug or a broken schema against an exact copy of your production content without editing live stories while you debug.
What you get
The controls you need to create, navigate, and secure isolated environments.
Environment creation
Set up your environment from your production space and decide what comes with it: your custom roles and user assignments, and your asset folder structure and internal tags.
Environment switcher
A sidebar control shows which environment you're working in and lets you move between every environment tied to the same production space.
Environment-scoped access tokens
Restrict a personal access token to a single environment, so integrations and scripts can never reach production.
This fundamentally changes how we manage complexity across development cycles. By enabling native environment management, teams can add new layers of experimentation and security to their development workflows without worrying about breaking live projects. It's a critical step toward more scalable and confident releases.
Start with one environment, free
If you're on Storyblok's Premium or Elite plan, your first environment is included.
Create it from your production space and start testing today.