Sense
Poll real equipment over real protocols and keep each reading's quality. A failed read is bad, never zero, so a dead sensor doesn't trip every low alarm.
Home automation is a toy right up until the day it matters. Industrial automation works, costs a fortune, and comes with a guy who has to drive out to change a setpoint. HotLoop is the thing in the middle that should have existed ten years ago: it reads real equipment, keeps the history, raises the alarm, and moves the machine, from a Pi on a shelf to a whole plant. It's free for you, and free for your business through EmberNet.
Inside deadband. No alarm raised, nothing paged.
A simulation in your browser. Drag the setpoint and watch the loop decide whether this is worth waking somebody up for. In the Gateway, the write that moves it crosses one gate. Out of range is refused and never clamped, and the refusal is written down.
Native protocol drivers in the Gateway, for talking to PLCs and other equipment. No placeholder drivers, every one run on real equipment, and a table that says exactly how far each has been proven.
Node types in Flow, our Node-RED-compatible wiring tool. Each one says how close it is to Node-RED, and the build fails if one lies about it.
The whole Flow container image on amd64. The method and the caveats are on the Flow page, because a benchmark without caveats is marketing in a lab coat.
That's the whole product. A rule you set once and pray over is not a loop. A loop is something you can walk away from, because it tells you the truth when it can't see and it refuses to do something stupid when somebody tells it to.
Poll real equipment over real protocols and keep each reading's quality. A failed read is bad, never zero, so a dead sensor doesn't trip every low alarm.
ISA-18.2 alarms (the industrial alarm standard), so an alarm that cleared before anybody saw it is still on the list at shift change. Rules are checked on save, so a typo dies in the editor.
Every write, from a person, a rule, or an agent, crosses one gate nothing routes around. Out of range is refused, not clamped. Go try to break it.
Poll real equipment over real protocols, and keep the quality of every reading, not just the number. A failed read is bad, never zero, so a dead sensor doesn't trip every low alarm on the unit and send the night shift chasing a tank that's fine.
ISA-18.2 alarms (the industrial alarm standard), including the one homegrown systems forget: the alarm that cleared on its own before anybody saw it. It's still on the list at shift change. Rules are checked when you save them, so a typo dies in the editor, not at 3am halfway through a batch.
Every write, from a person, a rule, or an agent, crosses one gate that nothing routes around. Out of range is refused, not clamped, and the refusal gets written down. Want to watch it say no? Go try to break it.
HotLoop is eight products for the plant floor: four that grow with a site (IoT, Edge, Gateway, and Edge Relay), plus Flow for wiring, Cascade for workflows, HotLoop for CODESYS for the PLC's own screen, and Transmitter for putting a PLC's values on the wire.
HotLoop core line, 4.21.1
Flow line, 2.14.1
Cascade line, 1.2.1
HotLoop for CODESYS line, 0.3.5
Transmitter line, 1.1.0
Most integration pages are a wall of logos. Ours has four tiers, and the top one is empty on purpose, because nothing has earned it yet. You'd rather know that now than at commissioning.
Proven on real plant equipment by somebody standing next to it. Nothing has earned this yet. The day something does, that zero becomes a one, and not a day before.
Ran against a real target, and the row names exactly which one. Real is not the same as certified, so it doesn't get to say certified.
A driver proven on the raw protocol messages and not yet on a real device. Nothing is in this tier today: S7comm and EtherNet/IP were here until they were tested on bare metal on 2026-11-17.
No driver, on purpose. These come in through the gateway your site already has, instead of a half-built one of ours.
Every HotLoop product except Flow is under the HotLoop Free Use License 1.0, and Flow is under the EmberNet Source License 1.0. HotLoop is free to use and it is not open source, apart from Flow's source, which is public. Home and lab use is free. A business signs up for EmberNet, free, and runs HotLoop there. There's no key to type in and nothing waiting behind a paywall. Want somebody else to own the rollout, SLAs and warranty included? That's our Official Systems Integrator, Fireball Industries.