# Prod vs Dev environments **URL:** \ **Category:** Ideas & Features\ **Created:** [September 12, 2022, 7:12am UTC](https://community.fibery.io/t/prod-vs-dev-environments/3275 "2022-09-12T07:12:36Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![neil](https://avatars.discourse-cdn.com/v4/letter/n/839c29/32.png) [@neil](https://community.fibery.io/u/neil)\ **Post date:** [September 12, 2022, 7:12am UTC](https://community.fibery.io/t/prod-vs-dev-environments/3275/1 "2022-09-12T07:12:36Z")
Apologies if this has already been discussed, I searched briefly for these topics but didn’t find anything. it would be nice to have a distinction between a production environment, where the various apps can be used with my team on our company data, and a dev environment where we can try things out and make mistakes (and where I might be able to hire a consultant to build Spaces without being able to access my important/secure data). Perhaps it could be enabled only in an “advanced” mode. Is anything like this in the works? ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [September 12, 2022, 9:01am UTC](https://community.fibery.io/t/prod-vs-dev-environments/3275/2 "2022-09-12T09:01:46Z")
You might find some value in this topic: > [@How do you test your apps?](https://community.fibery.io/t/how-do-you-test-your-apps/3227): > > Say you have a complex set of related apps that’s running your business. How do you ensure that someone making a change in some formula over here does not break some workflow over there? I’m wondering whether there’s anything like integration tests, that ensure that everything is as expected on an ongoing basis. ([Asked for Coda](https://community.coda.io/t/how-do-you-test-your-docs/33418), and got an [interesting response](https://community.coda.io/t/how-do-you-test-your-docs/33418/3?u=jean_jordaan1).) ---
**Author:** ![neil](https://avatars.discourse-cdn.com/v4/letter/n/839c29/32.png) [@neil](https://community.fibery.io/u/neil)\ **Post date:** [September 12, 2022, 9:47am UTC](https://community.fibery.io/t/prod-vs-dev-environments/3275/3 "2022-09-12T09:47:57Z")
Thanks Chris - the suggestion to create a duplicate workspace seems like a good idea. But is it something that can be done at scale, every time you want developers to make a change? ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [September 12, 2022, 9:51am UTC](https://community.fibery.io/t/prod-vs-dev-environments/3275/4 "2022-09-12T09:51:23Z")
Well, there are no limits to when/how often you create a workspace clone, so it’s scalable, but only to the extent that it has to be done manually ---
**Author:** ![Chr1sG](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/chr1sg/32/3941_2.png) [@Chr1sG](https://community.fibery.io/u/Chr1sG)\ **Post date:** [April 29, 2025, 11:23am UTC](https://community.fibery.io/t/prod-vs-dev-environments/3275/5 "2025-04-29T11:23:01Z")