This message was deleted.

If you are thinking of using these environments for saving some money, I have seen quite a few success stories here. Although a lot of people suggest using temporary environments for branch previews, this almost never works out in a complex system. Instead if you use one stable environment for qa/pre-prod and schedule it with some availability and scaling rules, that works out quite well.

We use preview environments successfully. I guess it mostly depends on what you are planning to test and how your system is structured. Can you already create a new environments today with relative ease?

Thank you for the out reach, we are still in planning phase. Right now we use codespaces to create a "preview env", but codespaces has some shortcomings and we would rather work with other tools.

Sorry for the late replay, I’m working at Humanitec, so we use Humanitec for that, but thinks like argocd likely also work.