Sandbox Environments

Safely make changes to the GraphQL schema, and test new content types without breaking production implementation.

I love the flexibility of GraphCMS. It's meant to be a headless CMS, and it thrives at that, but don't get it twisted. GraphCMS can be a super powerful GraphQL database. I use it for my administrative tables, as well as for other projects.
Jordan S. Director of Product Growth
Integrated GraphQL Playground is very helpful when developing and debugging.
Pascal F.Software-Entwickler
Very powerful GraphQL capabilities and the new UX is on point.
Saskia Jung
GraphCMS focuses on the benefits and how we can help you get better results for your business or your customers. This focus on use to the user is what makes GraphCMS unique.
Shabnam M. Content Specialist
Super impressed with the fine grained roles and permissions; I had a colleague on a hangout who has experience with other headless CMS vendors, and his jaw dropped at the sheer capability.
GraphCMS User

Sandbox Environments

To allow safe iterations on your schema until you develop the final content model for the feature you want to add, GraphCMS supports working with multiple environments. Environments are instances of your project. Think of them as copies of your whole project, or branches similar to Git. Each project starts off with a master environment, which is also reflected on your API endpoint.

How to Setup Environments

With GraphCMS, setting up different Environments to ensure your content is accurate for the various platforms like web, voice, mobile and beyond, is easy with inherent tools withing GraphCMS.

Read more about how easy it is to set up a development environment within your project with a set-by-step guide -->

Read the Documentation

How to Setup Environments

With GraphCMS, setting up different Environments to ensure your content is accurate for the various platforms like web, voice, mobile and beyond, is easy with inherent tools withing GraphCMS.

Read more about how easy it is to set up a development environment within your project with a set-by-step guide -->

Read the Documentation