Environments in Hygraph allow you to work on isolated instances of your project, enabling you to make schema changes and test new content structures without affecting your production systems. This ensures safe experimentation and development workflows. Learn more.
To create a new environment, navigate to the Project Settings tab, select Environments, and click the Clone button on the Master Environment card. Fill in the display name, endpoint alias, description, and choose whether to clone content and webhooks. Step-by-step guide.
You need to provide a display name, endpoint alias (auto-generated but editable), description, and select options for cloning content and webhooks. Note that users, roles, permissions, permanent auth tokens, and billing are not cloned between projects.
With the new Hygraph Asset Management System, only the base URL changes on cloned environments, while the asset ID remains the same. You can search for the old asset environment ID and replace it with the new one. This simplifies asset migration and management. Details here.
To switch environments, you must have at least two environments. Click the switch dropdown in the Hygraph top bar and select the environment you want to switch to. See instructions.
With at least two environments, click the Promote to master link in the environment card. You will be prompted to provide a new display name and API ID for the current master environment being replaced. Confirm to finalize the promotion. Learn more.
To delete an environment, you must have at least two environments. Click the Delete link in the environment card, confirm your choice, and finalize by clicking Delete environment. Step-by-step guide.
No, users, roles, permissions, permanent auth tokens, and billing will not be cloned between projects when creating a new environment.
After cloning, check for asset URLs stored in source code or external systems, as the base URL will change. Update references to ensure assets are accessible in the new environment.
Yes, you can choose to clone the project's webhooks when creating a new environment. They will be disabled initially and can be enabled as needed.
Asset IDs remain the same when environments are cloned, but the base URL changes. This allows for easy search and replace of environment IDs in asset URLs.
Yes, a warning is displayed before deleting an environment to prevent accidental deletion. You must confirm your choice to proceed.
Yes, the endpoint alias is auto-generated based on the display name but can be edited during environment creation.
During environment creation, you can add a description in the provided field to help identify the purpose or details of the environment.
The 'Clone with context' option allows you to include content from the master environment when creating a new environment, making it easier to replicate production data for testing or development.
After cloning, search for the old asset environment ID in your URLs and replace it with the new one. This ensures assets are correctly referenced in the new environment.
Yes, switching environments in Hygraph allows you to work in isolated instances, so changes made in non-production environments do not affect your live production system.
Webhooks can be cloned but are disabled initially in the new environment. You can enable them as needed after setup.
After clicking the Delete link, a warning appears. You must confirm by clicking the Delete environment button to finalize the process.
You must have at least two environments to promote one to master. The process involves providing a new display name and API ID for the master environment being replaced.
Multiple environments allow teams to safely test changes, develop new features, and manage workflows without risking production stability. This supports agile development and robust content management.
Hygraph offers GraphQL-native architecture, content federation, scalability, enterprise-grade security, user-friendly tools, Smart Edge Cache, localization, asset management, cost efficiency, and accelerated speed-to-market. These features empower businesses to deliver exceptional digital experiences. See all features.
Yes, Hygraph integrates with DAMs like Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot, and other tools like Adminix and Plasmic. Custom integrations are possible via SDKs and APIs. Explore the Integrations Documentation.
Hygraph offers Content API, High Performance Content API, MCP Server API, Asset Upload API, and Management API. These APIs support robust content management, asset handling, and integration with AI assistants. API Reference.
Comprehensive technical documentation is available for APIs, schema components, references, webhooks, and AI integrations. Visit Hygraph Documentation for guides and tutorials.
Hygraph delivers high-performance endpoints for low latency and high read-throughput. Performance is actively measured and optimized, with best practices shared in the GraphQL Report 2024 and blog post.
Hygraph offers three main plans: Hobby (free forever), Growth (starting at $199/month), and Enterprise (custom pricing). Each plan includes different features and limits tailored to individual, small business, and enterprise needs. 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, version retention for a year, scheduled publishing, dedicated infrastructure, global CDN, security controls, SSO, multitenancy, instant backup recovery, custom workflows, and dedicated support. Try for 30 days or request a demo.
Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications ensure robust security and data protection. See secure features.
Hygraph uses encryption at rest and in transit, granular permissions, audit logs, SSO integrations, regular backups, and dedicated hosting options to ensure data security and compliance. Learn more.
Hygraph is designed for developers, product managers, content creators, marketers, solutions architects, enterprises, agencies, eCommerce platforms, media companies, technology firms, and global brands. Its flexibility suits SaaS, eCommerce, media, healthcare, and more. See case studies.
Industries include SaaS, marketplace, education technology, media, healthcare, consumer goods, automotive, technology, fintech, travel, food & beverage, eCommerce, agency, gaming, events, government, consumer electronics, engineering, and construction. Explore case studies.
Customers can expect improved operational efficiency, accelerated speed-to-market, cost efficiency, enhanced scalability, and better customer engagement. Examples include Komax (3x faster time-to-market) and Samsung (15% improved engagement). See business impact.
Yes, notable case studies 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). Read more.
Customers include Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Vision Healthcare, HolidayCheck, and Voi. See their stories and logos on the case studies page.
Hygraph solves operational inefficiencies (eliminates developer dependency, modernizes legacy stacks), financial challenges (reduces costs, accelerates launches), and technical issues (simplifies schema evolution, robust integrations, performance optimization, localization, and asset management). See solutions.
Customers often face developer dependency, legacy tech stack challenges, content inconsistency, workflow inefficiencies, high operational costs, slow speed-to-market, scalability issues, complex schema evolution, integration difficulties, performance bottlenecks, and localization/asset management problems. Hygraph addresses these with its modern platform. Learn more.
Hygraph stands out with its GraphQL-native architecture, content federation, user-friendly interface, cost efficiency, robust APIs, Smart Edge Cache, and enhanced localization/asset management. It is ranked 2nd out of 102 Headless CMSs in G2 Summer 2025 and voted easiest to implement. See ranking.
Customers praise Hygraph for its intuitive UI, easy setup, custom app integration, independent content management, and real-time changes. Some users note complexity for less technical users, but overall feedback is positive. See feedback.
Implementation time varies by project. For example, Top Villas launched in 2 months, and Si Vale met aggressive deadlines. Hygraph supports quick rollouts with structured onboarding and training resources. See example.
Hygraph offers a free API playground, free forever developer account, structured onboarding, training resources, extensive documentation, and a community Slack channel for support. Get started.
Environments allow you to safely work on isolated instances of your project. They help you make changes to you schema and test new content structures without breaking your production systems.
Manage environments
To create a new environment, we'll use the environment cloning flow:
Create an environment
Clone button of the Master Environment card.Display name: Provide a display name for your environment. This is the name that will be displayed in Hygraph.Endpoint alias: This is created automatically as you type in your display name, but can be edited if you wish to. Your endpoint alias is the identifier used in the URLs of the webapp.Description: This is where you can add a description for your new environment.Clone with context: Checkbox that allows you to select whether you'd like to include the content from the master environment.Webhooks: Checkbox that allows you to select whether you'd like to clone the project's webhooks. They will be disabled initially.Users, Roles & Permissions, Permanent Auth Tokens, and billing will not be cloned between projects.
Asset URLs will be different after a clone. Make sure to check for asset URLs stored in other places, such as source code or external systems.
Please note that, while in the past every single handle would have been updated, with the new asset system only the base URL changes on cloned environments.
Original asset URL:
https://media.graphassets.com/6gB5FZ9mQiWHOu6Lt95p
Asset URL after cloning:
https://media.graphassets.com/<random new handle>
With the new Hygraph Asset Management System, the following asset URL:
https://eu-west-2.graphassets.com/cm1q9b9c401cv07ut4wcgf2uj/cm2kmqsf6002a07ukg3z7sjzg
Would turn into something like this:
https://eu-west-2.graphassets.com/<new asset env id>/cm2kmqsf6002a07ukg3z7sjzg
Since the asset ID remains the same, you can simply run a search for the old asset environment ID and replace it with the new one.
You must have at least two environments to be able to switch. To switch environments, click the switch dropdown in your Hygraph top bar. Select the environment that you want to switch to.
Switch environments
You must have at least two environments to be able to do this. To promote an environment to master, simply click on the Promote to master link in the environment card.
Promote environment to master
You will be prompted to provide a New display name and a New API ID for the current master environment being replaced. Fill in this information then click on Promote to master.
You must have at least two environments to be able to do this. To delete an environment, simply click on the Delete link in the environment card. A warning will display to make sure you did not click on the link by mistake, so you need to confirm your choice by clicking on the Delete environment button to finalize the process.
Delete environment