Who's behind RackNet?
RackNet is built by the same engineering team that helped build the Innorack digital controller: the device on every Innovive rack, and the source of the airflow, pressure and alarm data RackNet reports.
In use by research institutions and contract research organizations in North America, Europe and the Middle East, with some customer relationships running more than a decade.
Built from the inside out
RackNet began inside Innovive. In 2009 Reese Systems partnered with Innovive to develop the digital controller for the Innorack IVC system — the embedded hardware and firmware that manages airflow, monitors differential pressure and reports system status on every rack. That controller became the foundation for RackNet.
For years RackNet ran as an Innovive-offered add-on, connecting to controllers over facility WiFi through a locally installed server. It worked, but it needed IT involvement and tied monitoring data to on-premise hardware.
In 2019 Innovive chose to focus on its core caging and rack products, and the RackNet intellectual property transferred to Reese Systems, its original architect and developer. Free to rebuild without constraints, we designed RackNet 2.0 from the ground up. The WiFi dependency became a purpose-built long-range wireless network that needs no facility infrastructure and no IT involvement. The on-premise server became a cloud platform on redundant, fault-tolerant services.
Today RackNet 2.0 monitors Innovive racks on multiple continents — and because Reese Systems continues to develop the Innorack controller alongside Innovive, RackNet moves in step with the hardware it monitors.
About Reese Systems
Reese Systems, Inc. was founded by Doug Reese, an engineer with more than 25 years in embedded systems, cloud architecture and IoT. He was previously CTO of a cloud-based consumer technology platform, where he led the design and scaling of infrastructure serving millions of users — experience that shaped the architecture behind RackNet 2.0.
Reese Systems remains a small company by design. RackNet is not a side project inside a large corporation or a product passed between owners: it is the primary focus of a dedicated engineering team with direct, ongoing access to Innovive's hardware platform. That means faster response to customer needs, tighter integration with Innovive's roadmap, and an accountability that larger monitoring vendors cannot offer.
Our commitment
Vivarium monitoring exists for one reason: to protect research. Equipment failures, airflow disruptions and environmental changes do not wait for business hours. RackNet is built around that reality — continuous monitoring, immediate alerts and a complete data history, so problems are caught early and nothing goes undocumented.
Monitoring should be simple to deploy and invisible to IT. Data should be reachable from anywhere, exportable for compliance reporting, and kept as a complete historical record rather than trapped on a local server that one person knows how to maintain.
Customers describe working with RackNet as a partnership. That is their word, not ours. Customer requests shape what we build next.
If your team needs something RackNet does not do yet, tell us about it.
See it in your own facility
The RackNet 5×5×5 trial monitors five racks for five weeks, with all hardware included.