Radiator-level vs Building-level Control

Radiator Labs attacks the comfort problem one radiator at a time, while Runwise attacks the control problem at the building brain. That difference matters because radiator covers let an owner throttle heat inside specific apartments after steam is already moving through the system, while Runwise changes when the boiler fires based on apartment level sensor data, which is usually easier to deploy across an entire portfolio and easier to extend into cooling, leak, and gas monitoring.

• Radiator Labs sits at the point of delivery. Its hardware is attached to each radiator, so the product acts like a smart valve and enclosure at the room level. That is a good fit for steam heated buildings with uneven heat by line or by apartment, where one resident is opening windows while another is cold.
  1 sacra 2 radiatorlabs
• Runwise keeps the old radiators and changes the upstream logic instead. Wireless temperature sensors across apartments feed a boiler room controller that decides when and how hard to heat the building. That means fewer device types to install, one dashboard for supers, and a cleaner path to layering on other building systems later.
  3 sacra 4 sacra
• The market is moving from simple boiler monitoring to outcome based control. Parity bundles optimization software, measurement and verification, and automated demand response, while New York rules like Local Law 97 push owners to cut emissions from large buildings now, making fast retrofit control products more valuable than slow capital projects alone.
  4 sacra 5 paritygo 6 nyc

Over time, the winners in this category are likely to be the systems that become the default operating layer for the whole building, not just a fix for one hot radiator. Point solutions can open the door, but portfolio owners will keep consolidating toward platforms that control more equipment, surface more savings, and help satisfy emissions rules with one install base.