Very much, but maybe also it is not fully clear what the UMH is and what it is not. This can come from the fact that there is not 100% agreement of the UNS IT appears to me to do two things. 1) help me manage my container instances so a bit more a a grown up version of the MING stack. Where I use Portainer today, I am limited to the Portainer running on one VM, UMH can manage the containers across distributed devices. 2) IT will help me structure my data into a systematic hierarchy But I don't see the compelling case, as to why I would start with UMH rather than Ignition, apart from licencing. And certainly coming from a Traditional Automation ( siemens Rockwell Wonderware), installed on Windows the level of expertise a manufacturer would need in their organisation is much higher. If I advise a client to go with ignition then they can find an integrator to help in almost any area of the world. So while I use the MING stack at home, for learning and developing custom solutions for customers (I have a Windturbine power forecast system) For a client starting off I would probably advise the "Everything is Ignition" ( Sung to the tune of Everything is Awesome from the Lego movie) And I can then move them to the "Magic UNS" as they scale, or for a larger plant they can start with the "Magic UNS" And I can take any of the three solution to a cloud MQTT broker (or one on a corporate server) to hand off the corporate/cloud type apps. So my problem with the UMH is how do I start quickly and start it out, to solve problems in a plant. Or as I grow past the "Everything is Igntion" stage how do I link in?