How it works
Fitted in a day. Then it stops being your problem.
There is no project here. A technician fits the units, you set your alert rules once, and the system runs — including the parts everybody eventually forgets to do by hand.
- 01
A technician fits the unit
Each refrigeration unit gets a CoolTech controller wired to its sensors and its compressor, fan and defrost circuits. A refrigeration technician handles it — yours or one of ours. Provisioning is a single command in the field, so most sites are finished the same day.
- No image to build, no server to stand up, nothing per-site to maintain
- Existing sensor placement is usually reused
- Monitoring-only fits are supported where you do not want control handed over
- 02
It enrols itself, you approve it
The unit asks to join your fleet. An administrator sees what it is reporting about itself and approves it. Nothing appears in your fleet unasked, and every unit carries its own credentials from that moment.
- Approval is a single click in the console
- Replacing failed hardware carries identity, history and settings across
- A unit can be paused and reinstated later without losing its record
- 03
You set the rules once
Thresholds, how long a breach must hold before it counts, who gets told, in what order, and how long between steps. Scope a rule to one unit, a location, a group, or the entire fleet — so a blast freezer and a produce cooler are never held to the same numbers.
- Every alert type shows its true worst-case detection time as you set it
- Phone numbers live on people, so one number change updates every rule
- Business-hours rules hold non-urgent texts; critical always breaks through
- 04
It runs without you
Readings arrive continuously, alerts fire when they should and stay quiet when they should not, and escalation keeps moving until somebody acknowledges. When something needs changing, you change it from a browser instead of a truck.
- A change made to an offline unit queues, shows as pending, and confirms when it lands
- Every notification is recorded, so a broken alert channel is visible
- Degrading equipment raises an alert before it fails
- 05
The record is already written
Because readings are recorded continuously, the HACCP log and the setpoint audit trail exist before anyone asks for them. Generate them on demand for any window, or schedule them to arrive by email.
- Exports to CSV for inspectors, auditors and insurers
- Configuration history per unit, dated
- History keeps accruing during an internet outage and backfills afterwards
The important part
Control lives at the unit, not in the cloud
This is the design decision everything else rests on. The refrigeration cycle — compressor, fans, defrost — is decided at the equipment. The console is for visibility, records and remote changes.
So when the internet drops, your product does not care. The unit keeps controlling and keeps recording, and uploads the gap when the link returns. You lose the dashboard for an hour. You do not lose the load, and you do not lose the log.
What is affected by an outage
- Refrigeration control
- Unaffected. Decided at the unit.
- Temperature recording
- Unaffected. Recorded locally, backfilled after.
- Local alarm behaviour
- Unaffected. Configured limits still apply.
- Remote visibility
- Paused until the connection returns.
- Outbound alerts
- Paused, and the silence itself raises an offline alert.
See it running on your own coolers.
A 20-minute walkthrough on your equipment, your locations, your alert rules. No slide deck.
Talk to the people who build it. No call centre, no gatekeeping.