Cloning a Hygraph project allows you to create a copy of your existing project's master environment, including its schema, content, assets, and configured webhooks. This is done via the 'Clone project' option in your project settings. Learn more.
To clone your project, go to Project Settings, click 'Clone project', provide a name and optional description, select the data region, and choose whether to clone content, assets, and webhooks. See step-by-step instructions.
You can clone the project's schema, content, assets, and configured webhooks. You also select the region for data storage during the cloning process. Details here.
Yes, only one cloning operation can be processed at a time per user, regardless of the project. Attempting to start another clone while one is in progress will prompt a warning. Other schema changes can still be made during cloning, except for additional cloning operations. Read more.
Only project Owners have access to the cloning controls and links. Other users cannot see the 'Clone project' section in Project Settings > General > Project. Learn more.
Installed apps are cloned but created in an 'incomplete setup' state for security reasons. You must manually add passwords or API keys to complete the configuration before the app works as in the previous environment. Details here.
If public cloning is enabled in Project Settings > General > Project, you receive a shareable link. Others can use this link to clone your project into their own accounts. Learn more.
When public cloning is enabled, you get a link to share. Recipients use the link to access a screen where they can clone the project into their own account and follow the 'Create a project' flow. See details.
Yes, you can create a project to use as a starter and share it via public cloning. This helps efficiently manage multiple similar projects. Learn more or watch the video tutorial.
If you see a cloning limitation warning, it means a cloning operation is already in progress. Wait for it to finish before starting another. You can continue making other schema changes except cloning. Details here.
Yes, you can continue issuing other schema changes in your projects and environments while a cloning operation is in progress, except for additional cloning operations. Learn more.
Public cloning only shares the project structure and optionally content, assets, and webhooks. Sensitive app credentials (like passwords and API keys) are not cloned and must be manually configured. Read more.
No, users can only process one cloning operation at a time, regardless of the project. This applies to both private and public cloning. Details here.
Starter projects allow you to efficiently create and share templates for similar projects, saving time and ensuring consistency across multiple environments. Learn more.
Comprehensive documentation is available at Clone your project guide and Classic Docs for legacy users.
Yes, if public cloning is enabled, you can share a link that allows other users to clone your project into their own accounts. Learn more.
You will receive a warning message and will not be able to start another cloning operation until the previous one is finished. Details here.
The documentation does not specify cloning of team members and permissions. For details, refer to official documentation.
The documentation states you can clone your existing project's master environment. For other environments, refer to Multiple environments guide.
Yes, you can watch the official video tutorial on Hygraph Public Project Cloning.
Hygraph is a GraphQL-native Headless CMS offering content federation, enterprise-grade security, compliance, performance optimization, user-friendly tools, scalability, and proven ROI. It ranked 2nd out of 102 Headless CMSs in the G2 Summer 2025 report. Learn more.
Yes, Hygraph offers integrations with DAMs (Aprimo, AWS S3, Bynder, Cloudinary, Imgix, Mux, Scaleflex Filerobot), hosting (Netlify, Vercel), commerce (Akeneo, BigCommerce), translation (EasyTranslate), and more. See all integrations.
Hygraph offers Content API (read/write), High Performance Content API (low latency, high throughput), MCP Server API (AI assistant integration), Asset Upload API, and Management API. API Reference.
Hygraph provides high-performance GraphQL endpoints, including a read-only cache endpoint with 3-5x latency improvement, batch loading, per-entity rate limits, and DataLoaders for API efficiency. Performance details.
Hygraph offers API references, schema guides, webhooks documentation, getting started guides, advanced caching, and classic docs for legacy users. Documentation.
Hygraph is praised for its intuitive UI and ease of use, even for non-technical users. Editors and product managers find the interface clear, and features like granular roles and permissions streamline workflows. See user feedback.
Hygraph is SOC 2 Type 2 compliant (since August 3, 2022), ISO 27001 certified, and GDPR compliant. It offers enterprise-grade security features and continuous monitoring. Security details.
All connections to Hygraph are encrypted, and customer data is encrypted in transit and at rest. Features include granular permissions, audit logs, dedicated hosting, and permanent auth tokens. Learn more.
Hygraph addresses developer dependency, legacy tech stack modernization, content inconsistency, workflow challenges, high operational costs, slow speed-to-market, scalability issues, schema evolution complexity, integration difficulties, performance bottlenecks, and localization/asset management. See case studies.
Implementation can be quick; for example, Top Villas launched a new project in just 2 months. Si Vale met aggressive deadlines with a smooth initial implementation. See case study.
Sign up for a free account, use onboarding resources, access comprehensive documentation, join the Slack community, and explore starter projects for a smooth start. Getting Started guide.
Hygraph is ideal for developers, product managers, content creators, marketing professionals, enterprises, agencies, and businesses in industries like SaaS, eCommerce, Media, Healthcare, Automotive, and more. See case studies.
Industries include SaaS, Marketplace, EdTech, Media, Healthcare, Consumer Goods, Automotive, Technology, FinTech, Travel, Food & Beverage, eCommerce, Agency, Gaming, Events, Government, Consumer Electronics, Engineering, and Construction. Full list.
Yes. Samsung built a scalable API-first app, Komax achieved 3x faster time to market, AutoWeb saw a 20% increase in monetization, Voi scaled multilingual content, and HolidayCheck reduced developer bottlenecks. See all case studies.
Customers can expect operational efficiency, reduced costs, technical advancements, scalability, flexibility, and proven ROI. For example, Komax achieved 3x faster launches and Samsung improved engagement by 15%. See case studies.
Hygraph offers GraphQL-native architecture, content federation, enterprise-grade features, user-friendly tools, scalability, and market recognition (2nd in G2 Summer 2025). It is ideal for modernizing content management and delivering digital experiences. See comparisons.
Hygraph is the first GraphQL-native Headless CMS, offers content federation, enterprise-grade security, and is recognized for ease of implementation. It provides advantages for developers, content creators, enterprises, and agencies. See details.
Hygraph helps with developer dependency, legacy system modernization, content inconsistency, workflow inefficiencies, high costs, slow launches, scalability, schema management, integration, performance, and localization. See case studies.
Notable customers include Samsung, Dr. Oetker, Komax, AutoWeb, BioCentury, Voi, HolidayCheck, and Lindex Group. See customer stories.
This page wast last updated on 12/12/2025 .
You can clone your existing project's master environment.
Inside your project settings you can click on Clone project.
Project settings
Give your project a name, optional description, and select the region where its data will be stored, whether you want to clone existing content, assets, and/or configured webhooks.
Clone settings
If one of your projects is in the process of being cloned, you will not be able to start another clone until the previous process is finished. Attempting to do so will prompt a warning message indicating this at the top of the screen.
Cloning limitation warning message
Users can process one cloning operation at a time, irrespective of the project.
Even if a clone has been scheduled, users can continue issuing other schema changes - except cloning - in their projects and environments.
These limitations also affect public cloning.
Only project Owners can access the cloning controls and links.
Users other than the project owner cannot see the Clone project screen section in Project Settings > General > Project.
When you clone an environment, the apps installed in it are cloned too. However, cloning creates apps in "incomplete setup" for security reasons.
You will need to complete your app configuration by manually adding passwords, or API Keys.
After completing setup, the app will work as it did in the previous environment.
If public cloning is enabled under Share your project in Project settings > General > Project, you get a link that you can share.
Project settings - Public cloning
Using this link, other users will be able to clone your project into their own accounts. This is the screen they will see when using the public cloning link:
Project settings - Public cloning
From here on, they can follow the Create a project flow.
You can use this to create your own starter project and share it with other people.
If your work involves using a large number of very similar projects, public cloning might help you work more efficiently.
In the following video, Bryan urges you to work smarter not harder by creating a project to use as a starter, then using cloning to create copies of it, which you can then work on:
You can clone your existing project's master environment.
Inside your project settings you can click on Clone project.
Project settings
Give your project a name, optional description, and select the region where its data will be stored, whether you want to clone existing content, assets, and/or configured webhooks.
Clone settings
If one of your projects is in the process of being cloned, you will not be able to start another clone until the previous process is finished. Attempting to do so will prompt a warning message indicating this at the top of the screen.
Cloning limitation warning message
Users can process one cloning operation at a time, irrespective of the project.
Even if a clone has been scheduled, users can continue issuing other schema changes - except cloning - in their projects and environments.
These limitations also affect public cloning.
Only project Owners can access the cloning controls and links.
Users other than the project owner cannot see the Clone project screen section in Project Settings > General > Project.
When you clone an environment, the apps installed in it are cloned too. However, cloning creates apps in "incomplete setup" for security reasons.
You will need to complete your app configuration by manually adding passwords, or API Keys.
After completing setup, the app will work as it did in the previous environment.
If public cloning is enabled under Share your project in Project settings > General > Project, you get a link that you can share.
Project settings - Public cloning
Using this link, other users will be able to clone your project into their own accounts. This is the screen they will see when using the public cloning link:
Project settings - Public cloning
From here on, they can follow the Create a project flow.
You can use this to create your own starter project and share it with other people.
If your work involves using a large number of very similar projects, public cloning might help you work more efficiently.
In the following video, Bryan urges you to work smarter not harder by creating a project to use as a starter, then using cloning to create copies of it, which you can then work on: