Built by an engineer who needed it to work.
GrowRoom is designed and built end to end by one engineer: the circuit boards, their firmware, the cloud server and the apps.
Grow rooms tend to fail when nobody is there to see it. A pump sticks, a reservoir drifts, the WiFi drops on the night the heater is needed. Most controllers are built as if those things will not happen.
GrowRoom starts from the other end. The hardware uses industrial parts and standard buses, because a room full of water and fertiliser is a hostile place for electronics. The software is tested mostly for the unpleasant cases: power cuts, dropped connections, a command sent twice, and one customer seeing another's data.
It is a prototype, and this site says so on every page that matters. Each feature carries its test status, and every specification says where its number came from.
What exists today
- A main controller board: STM32H743 processor with an ESP32-C5 WiFi gateway on board
- A pump driver board for each dosing pump, with its own STM32G0, motor driver and encoder input
- Firmware for both boards and the gateway, with signed over-the-air updates for the gateway
- A cloud server with 284 automated tests, including customer data separation
- A phone app and a browser portal, built from one codebase
How far each of these has been tested is on the status page.
Four rules the design follows.
They decide the arguments that come up while building it, and they are why the site reads the way it does.
Measure, do not assume
Every pump counts its own output with an encoder instead of trusting a timer, and the pump boards report their own supply voltage. A guess about hardware state is a bug waiting to be believed.
Fail safe, never silent
Pumps start disarmed and stop on a stall or a time limit. Irrigation never restarts by itself. A room that stops reporting raises an alarm rather than looking calm.
Say what is tested
"Working" on this site means demonstrated. Manufacturer figures are labelled as theirs, and anything undecided says so instead of being left out.
Your rooms are yours
An account sees only its own organisation's rooms, enforced by the server and checked by automated tests. Data is hosted in the EU with encrypted backups.
How to reach us.
Email: hello@your-domain.example
For a reservation, use the basket; for pilot enquiries, the early-access form, so we have your room details first.
Company name, registered address and team details are to be confirmed and will appear here before launch.
See where it stands.
What works, what is being built, and what is planned, updated as milestones are met.