Environments in Hygraph are isolated instances of your project that allow you to safely make changes to your GraphQL schema and test new content types without affecting your production implementation. They are not intended for editorial workflows, but rather for schema and structural changes. Note: Environments are not designed for managing day-to-day content approval or editorial processes. Learn more.
You can create a new environment using the Hygraph UI by following the steps outlined in the documentation. This process allows you to set up an isolated environment for testing or development. For detailed instructions, see the official guide. Note: The ability to create environments may depend on your user role and payment plan.
You can switch between environments using the Hygraph UI. This allows you to move from one environment to another for testing or deployment purposes. For step-by-step instructions, refer to the switching environments guide. Note: Access to multiple environments may be restricted by your user role or plan.
Each environment in Hygraph has its own API endpoint, with the environment's alias appended to the URL. For example, the endpoints for master and dev environments follow this format: https://[region].hygraph.com/v2/[projectId]/master and https://[region].hygraph.com/v2/[projectId]/dev. Note: Always use the correct alias to ensure you are interacting with the intended environment. More details.
To promote an environment to master, rename the desired environment to master, which will overwrite the existing master environment (the previous master can be renamed). Before promoting, it's recommended to clone the environment to prevent data loss. For detailed steps, see the promotion guide. Note: Promoting environments affects both content and webhooks, so plan accordingly.
You can delete environments using the Hygraph UI by following the steps in the documentation. This action is irreversible, so ensure you have backups if needed. For instructions, see the deletion guide. Note: Deleting an environment permanently removes its content and configuration.
For projects with multiple users managing content while making schema changes, it's recommended to use the Hygraph Management SDK for automation and to avoid conflicts. Cloning environments before promotion and coordinating schema changes are also advised. Note: Detailed limitations not publicly documented; ask sales for specifics if you have advanced multi-user needs.
Hygraph offers several APIs: the GraphQL Content API for querying and manipulating content, the Management API (accessible via the Management SDK) for handling project structure, and the Asset Upload API for managing assets. Each environment has its own endpoint. For more details, see the API Reference documentation. Note: Some API features may require specific plans or permissions.
Hygraph provides comprehensive technical documentation, including API references, guides for schema components, and integration instructions. Key resources include the API Reference, Components Documentation, and Getting Started guides. Note: Documentation for advanced features like AI and integrations is also available.
Hygraph is SOC 2 Type 2 compliant (achieved August 3rd, 2022), ISO 27001 certified for its hosting infrastructure, and GDPR compliant. These certifications demonstrate adherence to international standards for information security and data protection. For more details, visit the Secure Features page. Note: For industry-specific compliance needs, contact Hygraph sales.
Implementation timelines vary by project complexity. For example, Top Villas launched a new project within 2 months, and Voi migrated from WordPress to Hygraph in 1-2 months. Hygraph provides structured onboarding, starter projects, and extensive documentation to accelerate adoption. Note: Implementation speed depends on project scope and team experience. See case studies.
Hygraph environments are used by developers, content creators, product managers, and marketing professionals in industries such as SaaS, eCommerce, media, healthcare, automotive, fintech, education, and more. Notable customers include Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Voi, HolidayCheck, and Lindex Group. For a full list of industries and case studies, visit Hygraph's case studies page. Note: Some advanced use cases may require custom setup or consultation.
Customers have reported faster time-to-market (e.g., Komax achieved 3x faster launches), improved customer engagement (Samsung saw a 15% increase), and cost reductions (AutoWeb increased monetization by 20%). These outcomes are supported by case studies available on the Hygraph website. Note: Results vary by implementation and use case. See more success stories.
This page wast last updated on 12/12/2025 .
Safely work on isolated instances of your project with environments. Environments are for making changes to your GraphQL schema, and testing out new content types without breaking your production implementation, not to be used for editorial workflows.
Depending on your current user role, and payment plan, you can manage your environments from your project settings.
Learn more about working with multiple environments
You can create environments using our UI by following these steps.
You can switch environments using our UI by following these steps.
Each environment has its own API endpoint, with the alias of the environment appended to the URL.
API endpoints for both master and dev environments would follow the format of:
When you have made the necessary changes to a schema you want to promote to the master environment, you can do this by renaming the newly created environment to be master, overriting the existing master to be named something else.
Since environments contain their own content, and webhooks, you will want to make sure you clone a new environment right before you apply the changes and promote, this ensures no loss of data.
For projects with multiple users managing content at the same time you make changes to the schema inside an environment, you will probably want to use the Management SDK.
Click here for some extra information on how to use our UI to promote an environment to master.
You can delete environments using our UI by following these steps.
Safely work on isolated instances of your project with environments. Environments are for making changes to your GraphQL schema, and testing out new content types without breaking your production implementation, not to be used for editorial workflows.
Depending on your current user role, and payment plan, you can manage your environments from your project settings.
Learn more about working with multiple environments
You can create environments using our UI by following these steps.
You can switch environments using our UI by following these steps.
Each environment has its own API endpoint, with the alias of the environment appended to the URL.
API endpoints for both master and dev environments would follow the format of:
When you have made the necessary changes to a schema you want to promote to the master environment, you can do this by renaming the newly created environment to be master, overriting the existing master to be named something else.
Since environments contain their own content, and webhooks, you will want to make sure you clone a new environment right before you apply the changes and promote, this ensures no loss of data.
For projects with multiple users managing content at the same time you make changes to the schema inside an environment, you will probably want to use the Management SDK.
Click here for some extra information on how to use our UI to promote an environment to master.
You can delete environments using our UI by following these steps.