HVACloud is here, and I could not be prouder

There are days when you present a product. And there are days when you finally get to show what a team has worked on for years. Today is one of those days. This is HVACloud, and I am not going to hide how proud I am of it.

Why we started this at all

Everyone in our industry knows the starting point. A manufacturer builds an excellent heat generator. The control strategy is sound, the hydraulics are right, the machine runs. And then comes the part that has nothing to do with the actual product: connectivity, visualisation, an app, alarms, remote service, analysis, updates. Every time a project. Every time a contractor. Every time from scratch, as soon as a new generation of equipment arrives.

We watched that from close up for years. In the control cabinet, in the plant room, in the project plan. And we came away with one conviction that everything else now rests on: this work does not belong in every project, it belongs one level up. In a platform the manufacturer operates themselves, with their own people, under their own name.

That is what HVACloud became.

What came out of it

I would rather use numbers here than adjectives:

• Seventeen protocols are built in, from Modbus and BACnet through Climatix, OPC UA and MQTT to eBUS, CAN, the Solar API, SunSpec, EEBUS, Zigbee and Matter. Not bought in, ours. Connectivity
• EEBUS under VDE-AR-E 2829-6 is running, well ahead of the July 2027 deadline from which the German subsidy requires it.
• Our own hardware. Touch panels in the Pro class, the smart home class for flush mounting and the GWPro for product business, all running the same edge client. Hardware
• AI assistants that help with building schemas, grouping, units, dashboards and analyses. Suggestions, not automation, and vendor independent. AI assistants
• Updates that reach past the gateway. Even a controller with no way out of its own gets one through us. Operations and administration
• Tested with 5,000 parallel clients, designed for 100,000 plants. Security and scale

On top of that comes research that deserves the name: in the HYDRA project we are working on physics informed AI for plants, and on a planning tool built on the validated calculation cores of an Austrian research institute. So we are not merely talking about the next five years, we are doing the research for them.

This is my team’s achievement

Now the part where I really am not going to hold back.

I know how many people sit on a platform like this elsewhere. I also know how large my team is. Put those two side by side and you will understand why I am being this blunt: what this crew has built in this time is extraordinary. Not because there is a lot of it, but because it is built to a depth you do not even see from the outside at first.

You do not write protocol drivers in an afternoon. Guiding a commissioning so that a technician in a plant room gets through it without a manual is craft. Rolling an update safely across a fleet, with approval levels, signatures and a watch period afterwards, is responsibility. My people do that every day, to a standard I never had to impose. They bring it with them.

Thank you for that. This is your work.

Trust comes before the feature list

Our customers hand us something quite personal: their plant data, their control logic, their route into the field and with it a piece of their reputation with their own end customers. To me that is not a sales argument but an obligation, and the platform is built accordingly:

• One instance per manufacturer. No mixing, and no tenant boundary that is really just a column in a table.
• Data ownership stays with the manufacturer. Operated in European data centres, the region agreed contractually, on premise possible. We trade in none of this data.
• Certified operation. sinnograte is certified to ISO 27001 for development and operation, and the platform has a route for reporting vulnerabilities with a committed response time.
• Remote access you can prove. Over an overlay mesh instead of an entry into the whole network, granted per device, time limited, logged, and that log is audited. Who was on which device and when is therefore not a matter of trust but a query.

Nothing less than the best and the safest

From December 2027 the Cyber Resilience Act applies to every connected product, the manufacturer’s cloud included. Many in our industry are only now seeing what that means: without a route for updates no support period can be promised, and without a device register the question “which devices are affected” is an investigation rather than a query.

We did not bolt these things on afterwards. They are the reason the platform looks the way it does. Our standard here is immodest, and it is meant to be: for our customers, the best and the safest we know how to build. Not the fastest, not the cheapest. Regulation

Come and look at it

HVACloud is at its most convincing on screen rather than on the page. The interface is under The interface, and for everything beyond that I will gladly make the time.

Request a demo

We are nowhere near finished. But what stands today stands properly. And I am proud of it.