@mwl@io.mwl.io The dodge we found here is to point out that _this_ gear has to remain in the released config, and it's the _customer_ who decides what that config is. So we _obviously_ need another identical set to do all our development on, and when it's finally released, it becomes static and the other one is now dev. They *have* to pay for that. But not for the other 100 machines that make up the infrastructure all that happens in. There, we push it out and see what happens...