On this page
One device, one probe, no rack integration.
TempGuard is a standalone unit with a wired temperature probe. It does not sit on your network, it does not need an agent on anything, and it does not touch the equipment it watches.
You place the probe where the temperature actually matters, usually a cold-aisle rack inlet rather than the room's ambient air, run the cable back to the device, and plug the device into mains. It has a built-in SIM, so it is online the moment it powers up. Thresholds are set from the dashboard, alert recipients are set per site, and that is the install.
For most server rooms that means no change request, no VLAN, no firewall rule, and no conversation with whoever owns the network. It is a temperature sensor with its own phone line.
A sensor on the network goes quiet at exactly the wrong moment.
This is the part that matters for a server room, and it is worth being blunt about.
Most environmental sensors report over the facility network. That is fine until the incident you actually bought them for. A power event, a failed switch, a UPS that did not hold, a cooling failure that takes down the rack the monitoring itself is plugged into, and the sensor stops reporting. What you get is silence, and silence is indistinguishable from everything being fine.
TempGuard reports over its own cellular connection and carries battery backup. When the room loses its network, or its power, the device keeps measuring and keeps alerting. It is not sharing a fate with the equipment it is watching.
If a device stops reporting for any reason, the platform flags it after 24 hours rather than leaving a quiet gap in the record. A hole in your temperature history is something that happened, not nothing.
Who was told, when, and whether anyone did anything.
A temperature alert nobody acts on is the same as no alert. The platform is built around that:
- All four channels
- When a reading crosses your threshold, phone call, WhatsApp, email and mobile push all dispatch together. No staged cascade, no waiting for an email nobody is reading at 2am.
- Escalation
- An alert nobody acknowledges within 60 minutes escalates, and the fact that nobody responded is recorded.
- Attribution
- Acknowledgement and resolution are tied to the person who did them, with the time.
- Trend history
- Continuous readings per probe, so you can show an inlet creeping up over three weeks rather than only the night it finally tripped.
- Unchangeable readings
- Stored readings cannot be edited or deleted, by anyone, including us. The database itself refuses the write.
- Export
- Readings, alerts and the change log export as CSV and PDF for any date range, site or device.
For a post-incident review, that is the difference between "the room got hot" and a timeline showing when it started, who was called, and how long it took someone to answer.
Where people actually put them.
- Server rooms
- Cold-aisle rack inlets, because that is the air the equipment is drawing. A sensor by the door tells you about the room, not about the hardware.
- UPS & battery rooms
- Battery life falls off sharply with sustained heat, and a UPS room is often the least-visited space in the building. It is also the one nobody notices until it is needed.
- Comms cupboards
- Switch closets and riser cupboards, frequently unventilated, sometimes with cooling that was never sized for what ended up in there.
- Branch and remote sites
- Small rooms with no on-site IT presence, which is exactly where a cellular device with its own alerting earns its place. One dashboard covers as many sites as you run, with per-site access per user.
Temperature, measured properly.
TempGuard is built around temperature and that is what we deploy. The sensor operates from -55 °C to +125 °C, with accuracy of ±0.5 °C from -10 °C to +85 °C, which covers every temperature a server room or UPS room will ever legitimately sit at.
If your room needs more than temperature, tell us what you need measured and we will scope it with you.