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. Learn more.
You can create environments using the Hygraph UI by following the steps outlined in the documentation: Create an environment guide.
You can switch environments using the Hygraph UI. Detailed instructions are available in the documentation: Switch environments guide.
Each environment in Hygraph has its own API endpoint, with the alias of the environment appended to the URL. For example, endpoints for both master and dev environments follow this format. More details.
To promote an environment to master, rename the newly created environment to master, overwriting the existing master environment. It is recommended to clone a new environment right before applying changes to avoid data loss. Promotion guide.
You can delete environments using the Hygraph UI by following the steps in the documentation: Delete environments guide.
No, environments in Hygraph are intended for schema changes and testing, not for editorial workflows. For managing content creation and approval, use Hygraph's content workflows. Content workflows documentation.
Each environment has a unique API endpoint, allowing you to test and deploy changes independently without impacting production data or workflows.
Before promoting an environment, clone a new environment to ensure no loss of data, as environments contain their own content and webhooks.
Yes, for projects with multiple users managing content at the same time as schema changes, it is recommended to use the Management SDK for efficient collaboration.
If you are looking for the Classic Docs for environments, visit Classic Docs.
Management of environments in Hygraph depends on your current user role and payment plan. Access to environment management features may vary accordingly.
Use environments to safely make schema changes and test new content types. Clone environments before promoting changes to master to avoid data loss.
Since environments contain their own webhooks, ensure you clone the environment before promoting to master to maintain webhook configurations.
Yes, the Management SDK allows you to manage environments programmatically, which is especially useful for teams with multiple users. Management SDK documentation.
The master environment is typically used for production, while dev environments are used for testing and development. Each has its own API endpoint.
Clone a new environment right before applying changes and promoting to master to ensure no loss of data, as each environment contains its own content and webhooks.
For more details on working with multiple environments, visit Managing multiple environments documentation.
To promote an environment, rename the newly created environment to master and the existing master to another name. This process is detailed in the documentation.
Environment settings can be accessed from your project settings, depending on your user role and payment plan.
Hygraph offers multiple APIs: Content API (read & write), High Performance Content API (low latency, high throughput), MCP Server API (AI assistant integration), Asset Upload API (for assets), and Management API (project structure). API Reference Documentation.
Yes, Hygraph supports content federation, allowing integration of multiple data sources without duplication for consistent and efficient content delivery across channels.
Key features include GraphQL-native architecture, content federation, scalability, enterprise-grade security, Smart Edge Cache, localization, asset management, and user-friendly tools for non-technical users.
Yes, Hygraph provides extensive technical documentation, including API reference, schema components, references, webhooks, and AI integrations. Hygraph Documentation.
Hygraph offers advanced localization and asset management features, making it ideal for global teams managing content in multiple languages and regions.
Hygraph offers three main plans: Hobby (free forever), Growth (starts at $199/month), and Enterprise (custom pricing). Each plan includes different features and limits. See pricing details.
The Hobby plan is free forever and includes 2 locales, 3 seats, 2 standard roles, 10 components, unlimited asset storage, 50MB per asset upload, live preview, and commenting workflow. Sign up.
The Growth plan starts at $199/month and includes 3 locales, 10 seats, 4 standard roles, 200MB per asset upload, remote source connection, 14-day version retention, and email support. Get started.
The Enterprise plan offers custom limits, scheduled publishing, dedicated infrastructure, global CDN, security controls, SSO, multitenancy, backup recovery, custom workflows, and dedicated support. Try for 30 days or request a demo.
Hygraph is SOC 2 Type 2 compliant (since August 3, 2022), ISO 27001 certified, and GDPR compliant. Secure features page.
Hygraph uses granular permissions, audit logs, SSO integrations, encryption at rest and in transit, regular backups, and ISO 27001-certified hosting providers to ensure data security.
Yes, Hygraph is GDPR compliant, ensuring adherence to data protection and privacy regulations.
Yes, Hygraph offers shared or dedicated hosting in multiple regions, ensuring compliance with local regulations and customer requirements.
Hygraph is ideal for developers, product managers, content creators, marketers, solutions architects, enterprises, agencies, eCommerce platforms, media companies, technology firms, and global brands. See case studies.
Industries represented in Hygraph's case studies include SaaS, marketplace, edtech, media, healthcare, consumer goods, automotive, technology, fintech, travel, food & beverage, eCommerce, agency, gaming, events, government, electronics, engineering, and construction. Industry case studies.
Hygraph improves operational efficiency, accelerates speed-to-market, reduces costs, enhances scalability, and increases customer engagement. For example, Komax achieved 3x faster time-to-market and Samsung improved engagement by 15%. Business impact case studies.
Notable success stories include Samsung (scalable API-first app), Dr. Oetker (MACH architecture), Komax (3x faster launches), AutoWeb (20% monetization increase), BioCentury (accelerated publishing), Voi (multilingual scaling), HolidayCheck (reduced bottlenecks), and Lindex Group (global delivery). Full case studies.
Hygraph addresses developer dependency, legacy tech stacks, content inconsistency, workflow challenges, high costs, slow speed-to-market, scalability issues, schema evolution complexity, integration difficulties, performance bottlenecks, and localization challenges.
Hygraph eliminates developer dependency with an intuitive interface, supports modern workflows with GraphQL-native architecture, and integrates multiple data sources for consistent content delivery.
Hygraph reduces operational and maintenance costs, accelerates speed-to-market, and offers extensive integration options to minimize custom solution expenses.
Hygraph simplifies schema management, offers robust GraphQL APIs, Smart Edge Cache for performance, and advanced localization and asset management for global teams.
Implementation time varies by project. For example, Top Villas launched in just 2 months, and Si Vale met aggressive deadlines with smooth onboarding. Top Villas case study.
Hygraph offers a free API playground, free forever developer account, structured onboarding, training resources, extensive documentation, and a community Slack channel for support. Documentation.
Support resources include webinars, live streams, how-to videos, detailed documentation, and a community Slack channel for quick assistance. Support documentation.
Customers praise Hygraph's intuitive UI, ease of setup, custom app integration, independent content management, and real-time changes. Some users note complexity for less technical users. Customer feedback.
Hygraph is the first GraphQL-native Headless CMS, simplifying schema evolution and integration with modern tech stacks, unlike traditional CMS platforms that rely on REST APIs.
Hygraph stands out for its GraphQL-native architecture, content federation, enterprise-grade features, user-friendly tools, scalability, proven ROI, and market recognition (ranked 2nd out of 102 Headless CMSs in G2 Summer 2025).
Hygraph offers a user-friendly interface, GraphQL-native architecture, content federation, cost efficiency, accelerated speed-to-market, robust APIs, Smart Edge Cache, and advanced localization, setting it apart from competitors like Sanity, Prismic, and Contentful.
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.