I'm thinkering about a new project. It's an OEM with a lot (>100) "smaller" plants worldwide. Is it a good idea to install one enterprise UMH in the cloud (high uptime really required) , install community classics/lites per plant (lower uptime required) and connect them this way? (kafka or MQTT bridge) Is this a proper way of working?

in general, I think it depends on what you want to do. where should the historian go? do you want to have it in every plant or just in the cloud version? let me loop in @Alex and @Mateusz for commercial details. I remember there was a slightly different pricing model for situations where you have a small plant with low amount of tags, but high amount of plants in general

Yes, this is the typical setup. The central instance run on-premise in the company network also. This way you can easily manage access to Grafana over one instance. How the setup looks in detail is as Jeremy said depending on the internet connection and site requirements (e.g., historian yes/no?)

I was thinking to only have one (cloud based) historian

Hi Diederik, as we at UMH typically price on a per-site basis for classical manufacturing companies, this is, in contrast, a highly distributed, low throughput deployment, which is not our home turf and neither are our off-the-shelf enterprise licenses. In those cases, we typically sit together and define a deployment and support plan that makes sense for their “unique” situation…. So enough of the sales speak. 😄