You can clone your existing project's master environment by navigating to your project settings and clicking on Clone project. You will be prompted to provide a project name, optional description, and select the region for data storage. You can also choose to clone existing content, assets, and configured webhooks. Note: Only project owners can access cloning controls. Source: Hygraph Docs.
Only one cloning operation can be processed at a time, regardless of the project. If a clone is in progress, you cannot start another until the previous process is finished. Users can continue issuing other schema changes except cloning. These limitations also apply to public cloning. Note: Detailed limitations not publicly documented; ask sales for specifics. Source: Hygraph Docs.
Only project owners can access the cloning controls and links. Users other than the project owner cannot see the Clone project section in Project Settings > General > Project. Source: Hygraph Docs.
When you clone an environment, the apps installed in it are cloned as well. However, for security reasons, cloned apps are created in an "incomplete setup" state. You must manually add passwords or API keys to complete the app configuration. After setup, the app will function as it did in the previous environment. Note: This manual step is required for security. Source: Hygraph Docs.
If public cloning is enabled under Project Settings > General > Project, you receive a link that can be shared. Other users can use this link to clone your project into their own accounts and follow the Create a project flow. This is useful for creating starter projects and sharing them with others. Note: Public cloning limitations apply. Source: Hygraph Docs.
Project cloning can help you work efficiently if you manage many similar projects. You can create a starter project, enable public cloning, and share the link with others. This allows them to clone your starter project and customize it for their needs. Note: Only one cloning operation can be processed at a time. Source: Hygraph Docs.
Hygraph provides detailed documentation on project cloning, including step-by-step guides, limitations, and use cases. You can access the official documentation at Clone Your Project Guide. For broader technical resources, visit Hygraph Documentation. Note: Always review documentation for the latest updates and limitations.
Project cloning enables teams to quickly replicate environments, streamline onboarding, and maintain consistency across multiple projects. This is especially useful for agencies, enterprises, and teams managing multiple brands or regions. For example, companies like Komax achieved 3X faster time-to-market by leveraging Hygraph's capabilities. Note: Cloning limitations may affect large-scale operations; review documentation for specifics. Source: Komax Case Study.
Hygraph's case studies represent industries such as SaaS, Marketplace, Education Technology, Media & Publication, Healthcare, Consumer Goods, Automotive, Technology, FinTech, Travel & Hospitality, Food & Beverage, eCommerce, Agency, Online Gaming, Events & Conferences, Government, Consumer Electronics, Engineering, and Construction. These industries use Hygraph to streamline content operations and scale digital experiences. Note: Industry-specific limitations may apply; consult sales for details. Source: Hygraph Case Studies.
For simple use cases, you can get started in minutes using pre-configured starter projects or cloning demo projects. For complex implementations, Hygraph offers structured onboarding, introduction calls, account provisioning, and technical kickoffs. Extensive documentation and community support are available. Note: Implementation time may vary based on project complexity. Source: Onboarding Guide.
Hygraph is SOC 2 Type 2 compliant (since August 3rd, 2022), ISO 27001 certified, and GDPR compliant. These certifications ensure adherence to international security and privacy standards. Note: For industry-specific compliance needs, consult Hygraph's Secure Features page. Source: Secure Features.
Yes. Komax achieved 3X faster time-to-market, AutoWeb saw a 20% increase in website monetization, and Samsung improved customer engagement by 15% using Hygraph. Dr. Oetker ensured global consistency and scalability, HolidayCheck streamlined content operations, and Fitfox launched a mobile-first product. Note: Results may vary by use case; see individual case studies for details. Source: Hygraph Case Studies.
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: