V1 / Active development / Scotland
Built by a breeder. Engineered without compromise.
RackStat is a ten-channel thermostat and monitoring platform designed specifically for reptile racks. Every level gets its own probe, heating output and control channel, giving breeders a clearer way to manage rack heating.
The problem
A ten-level snake rack may have ten separate heat sources, but most readily available thermostats are designed around one probe and one control point.
Use one or two thermostats and several levels have to share a reading. Give every level its own thermostat and the rack gains a pile of boxes, plugs, probe leads and power cables.
One or two thermostats shared across a ten-level rack.
Two readings stand in for ten different levels. Individual control means repeating the thermostat hardware, wiring and plugs.
One unit containing ten complete thermostat channels.
Every level keeps its own probe, target and output, without ten separate control boxes.
Breeding and seasonal changes
Cooling and warming periods can require planned temperature changes for a species or breeding group. That should be a controlled job, not an afternoon spent reaching behind racks, visiting several thermostats and wondering whether the right one was changed.
RackStat presets and per-channel settings are being designed so a keeper can choose the intended rack, review every affected channel and confirm the change from one place.
Planned V1 workflow — final preset behaviour will be proven during firmware and real-rack testing.
Why RackStat exists
“RackStat started because I wanted a better way to control the heating in my own racks. I did not want one probe representing an entire stack of animals, and I did not want to build every rack around a collection of unrelated thermostats.”
A thermostat should not become a sealed, disposable black box. Faults should be identifiable, settings should survive an interruption, and a damaged probe should be replaceable.
The first four-channel ESP32 prototype proved the basic control approach. The next job is less glamorous and more important: turn it into production-level hardware that can be built, tested, maintained and trusted.
V1 system overview
Each channel is intended to operate as a complete thermostat. Readings below are representative interface data, not live product telemetry.
Planned V1 capability
RackStat is being designed to show what each heating channel is doing, retain the settings that matter and provide useful information when something changes.
Ten temperature inputs and ten separately controlled outputs are the foundation of the design. Channel targets, modes, calibration and alarms remain independent.
Planned current sensing adds heater activity and energy use to each channel record. That can help show when a panel draws unexpectedly, stops drawing power or behaves differently from neighbouring levels.
Probe disconnection, abnormal heating, enclosure temperature and output behaviour are being considered as distinct fault states. Intended safeguards include watchdog operation, audible alerts and safe output behaviour.
The front display and rotary control are intended for direct use. A local web interface and over-the-air firmware updates are planned for broader visibility and maintenance.
No mandatory subscription. Core thermostat control, local monitoring and essential safety functions should remain part of the product itself.
Power interruption
Temperature targets, channel modes, calibration values and other essential settings are intended to remain stored when power is interrupted.
When power returns, RackStat should recover safely without requiring the user to crawl behind a rack and rebuild every setting.
Safety and thermal design
The production design is being developed with certification, electrical safety, thermal performance and manufacturability in mind. Compliance work is still ahead; no approval is being claimed.
Cool air is intended to enter near the lower components and leave near the hottest upper section. Fan speed will respond to internal temperature, with fault handling if the enclosure becomes too hot.
Mains and low-voltage sections are being laid out with physical separation, fused input and independent low-voltage protection in mind.
Internal monitoring and active push-pull airflow are part of the design, not accessories added after the electronics are packed in.
Probe loss, watchdog events, abnormal heating and over-temperature conditions need explicit output behaviour and clear fault reporting.
Serviceable connectors and replaceable parts are preferred where they improve the useful life of the product.
Probe and connector direction
RackStat is being designed around removable DS18B20-based probes and secure connectors so that a damaged cable does not mean replacing the entire thermostat.
Development record
RackStat is not yet a retail product. The first prototype validated the core control approach. The full ten-channel PCB, enclosure, firmware and safety systems are now being worked toward a production-level prototype.
No artificial percentages. No invented launch date.
Foundation
Proven in early prototypeProduction architecture
Current focusProduction-level prototype
Next major buildField testing
PlannedInitial production
Future stageContact
A project email and verified social links will be added here when they are ready. Until then, this page will not pretend to send a message anywhere.
Enquiry channel: being prepared
Planned enquiry routes
Planned social handle @rackstatuk