Skip to content
CoolTech

The platform

A controller on every unit, one console over all of them

CoolTech takes over the refrigeration cycle on the equipment you already own, then reports what it is doing to CoolTech Central — monitoring, alerting, compliance records, multi-site structure, access control and the whole lifecycle of the units underneath it.

Control

CoolTech is the controller, not a sensor on the wall

It fits the walk-ins, freezers, reach-ins and cases you already own and takes over the refrigeration cycle — compressor, defrost, fans. You keep your equipment; CoolTech becomes the brain running it, and every setting a technician would turn at the unit is settable from a browser.

  • Fits your existing equipment

    You are not buying new coolers. CoolTech is wired into the refrigeration system you already run, by a technician, in a normal service visit.

  • Runs the refrigeration cycle

    Compressor staging, defrost initiation and termination, fan behaviour and alarm limits are all decided by CoolTech at the unit — not reported on from the outside.

  • Setpoints from anywhere

    Change a setpoint from the unit page or straight from the fleet list. Two setpoints with automatic time-of-day switching cover day and night targets.

  • Full defrost configuration

    Defrost type and mode, defrosts per day, run time between, demand sensitivity, pump-down, termination temperature, drain time and maximum defrost length.

  • Alarm setpoints and delays

    High and low alarm enable, offsets and delays configured per unit, so a blast chiller and a produce cooler are not held to the same rule.

  • Fan and coil behaviour

    Fan state, delay temperature and delay time, coil release temperatures, air temperature differential, minimum compressor run and off times.

  • Queued changes stay visible

    A change made while a unit is offline is shown as pending and applied on the next check-in, with confirmation when it lands. Nothing is silently lost.

  • Applied means applied

    Every command is acknowledged as applied or failed. CoolTech never reports 'sent' and lets you assume 'done'.

Visibility

Every unit, every site, one screen

The fleet view is the whole estate at a glance — and it updates itself the moment something changes, so what you are looking at is what is happening.

  • Live fleet dashboard

    Customer, unit, location, asset, return-air temperature, active setpoint, coil sensor readings and last-seen time for every unit you have access to.

  • Updates without refreshing

    The screen changes when the equipment does. Nobody has to remember to reload, and nobody is looking at a five-minute-old number.

  • Search that matches how you think

    Filter by customer, location, unit, asset, status, connection state, pending changes, or the current reading itself.

  • Temperature history charts

    Any unit, any time range, custom date windows. The shape of a defrost cycle is obvious, and so is the shape of a failing one.

  • Technician diagnostics

    Connection, sync, command and equipment health on one page — the screen you open before deciding whether to send a truck.

  • Wall display mode

    A full-screen rotating readout of setpoint, return air, coil sensors, outputs and last defrost for a back-office monitor or a screen at the unit.

Alerting

Alerts people actually trust

An alert system only works if nobody has learned to ignore it. Every rule here is built to fire when it matters and stay quiet when it does not.

  • Sustained-breach thresholds

    A reading has to be out of range and stay out of range for a duration you set. A delivery door held open does not page anyone.

  • Offline and stale detection

    Alerts when a unit stops reporting, and separately when a unit is still connected but its readings have stopped moving — the failure mode most systems miss entirely.

  • Published detection times

    Every alert type states its true worst-case detection time in the editor. You are never sold a fifteen-minute promise the system cannot keep.

  • Predictive equipment health

    Degradation in the unit's own hardware — wear, media faults, cabling, response times — raises an alert before the failure, so replacement happens on a scheduled visit.

  • Email and text deliveryRolling out

    Both channels, with retry. Phone numbers live on the person, so one number change updates every rule that reaches them.

  • Escalation chainsRolling out

    Manager now, on-call phone at fifteen minutes, whole admin group at thirty. Acknowledging in the console stops the chain.

  • Business hours and rate limitsRolling out

    Hold non-urgent texts to working hours; critical always breaks through. A per-number cap means a runaway condition pages once, never a hundred times.

  • Delivery receipts

    Every send is recorded with recipient, time and outcome. An alert channel that quietly broke is visible instead of looking like a quiet week.

Records

The log is already written

Compliance stops being a task when the record is a byproduct of the equipment doing its job.

  • HACCP temperature reports

    The food-safety temperature log an inspector asks for, over any date range, for one unit or a whole group.

  • Setpoint audit trail

    Who changed which setpoint, when, and to what. The report that answers 'why was this cooler at 45 degrees'.

  • CSV export

    Every report exports for spreadsheets, auditors, insurers and your own archive.

  • Scheduled delivery

    Reports generated and emailed on a recurring schedule, with nobody responsible for remembering to run them.

  • Configuration history

    A dated revision history for every unit, so a change three months ago is still explainable today.

Structure

Built for more than one building

Customers, locations and groups are first-class, which is why a service contractor can run an entire book of business from one login.

  • Separate customers

    Full separation between customers. A service company runs every client from one login and no client ever sees another.

  • Locations with real timezones

    Each site carries its own timezone, so overnight maintenance windows and daily reports read correctly where the equipment actually is.

  • Groups that cut across sites

    'Every walk-in freezer', 'Stores 12 and 14' — group anything, then scope alerts, reports and permissions to the group.

  • Scoped access

    Platform administrator, customer administrator and viewer roles, each seeing exactly the customers, groups and locations assigned to them.

  • Billable unit counts

    Per-customer counts with explicit exclusions for demo, internal and warranty units, exportable for invoicing.

Security

Access you can account for

Refrigeration control is an operational capability. It is treated like one.

  • Two-factor authentication

    Time-based two-factor enrolment for administrator accounts, with an administrator-side reset path.

  • Single sign-on

    Sign in with existing Microsoft or Google work accounts alongside username and password.

  • Audit trail

    A searchable record of administrative and security-relevant actions: who did what, when.

  • Per-unit credentials

    Every unit carries its own credentials, rotated automatically when it is paused, retired or re-enabled. A compromise is contained to one unit.

  • Individual service access

    Service access to each unit is issued individually and held under audit, never one shared key across a whole fleet.

  • Encrypted in transit, backed up continuously

    Automatic certificate renewal, point-in-time recovery and an independent daily backup with a rehearsed restore procedure.

Lifecycle

Fleets change. The record should not break.

Adding, replacing, pausing and retiring units are normal events, handled as normal events.

  • One-command install

    A new unit is provisioned in the field with a single command. No image building, no per-site configuration.

  • Approved enrolment

    A unit requests enrolment; an administrator reviews what it reports about itself and approves. Nothing joins your fleet unasked.

  • Replacement keeps the history

    A replacement carries identity, history and settings across; the old endpoint is retired and linked rather than deleted.

  • Pause and reinstate

    Pause a unit for a seasonal closure or a service hold, reinstate it later with its history intact. Paused units are not billed.

  • Update policiesRolling out

    Manual, scheduled or automatic updates set per customer, group or unit, with site-local maintenance windows, blackout dates and a per-unit hold.

  • Fleet version visibilityRolling out

    What every unit is actually running, at a glance, rather than what it was supposed to have received.

Already a customer?

CoolTech Central is where all of this lives. Sign in to see your fleet, run a report, or change a setpoint.

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.