Choose the modules your site needs
Start with your site layout, crop records and sensor readings. Add shift planning, equipment control or decision tools as your operation needs them.
Three capability layers
The modules are grouped around the job they do on site. Start with monitoring and day-to-day operations, add automated control where it helps, and use decision tools when you need to weigh forecasts, demand or cost. You can choose the combination that fits your site; decision tools do not require equipment control.
Core and monitoring
See what is happening across the site and trace each batch back to its plan, conditions and work.
Environmental monitoring · Crop recipes & lifecycle · Crop health & scouting · Labour & shift planning · Harvest & post-harvest · Farm design & capacity · Analytics & financial modellingAutonomous control actions
Run recipe setpoints automatically, within fixed safety limits that recipes and models cannot change.
Fertigation & irrigation · Climate & lighting control · Closed-loop control & safetyAI-driven optimisation and decision intelligence
Your growing history, harvest forecasts, lighting costs and customer demand, weighed before the crop plan changes. Nothing in this layer controls equipment.
Forecasting & prediction · Energy & tariff optimisation · Demand-led planningSix levels in the stack
Behind the capability layers, each part of the platform looks after its own data and connects through one API gateway. That keeps the modules connected without turning the whole platform into one tightly coupled system.
Site model
A digital map of the farm, from zones and racks to shelves and equipment. Every reading and action is tied to a real place, so batches and sites can be compared properly.
Level 2Sensing
MQTT and configured Modbus readings are timestamped against the site, zone and device. Sensor history and calculated summaries are kept distinct, with missing readings visible in the record.
Level 3Intent
Versioned crop recipes hold the growth stages, nutrient formulations and target environment. They give the team a clear plan to compare with the result.
Level 4Action
Setpoints and PID control turn the crop plan into actuator commands. Fixed safety limits sit underneath, and PID refusals are logged with the reason.
Level 5Economics
Time-of-use tariffs, lighting cost, capex, opex and labour put a price beside each operational choice.
Level 6Intelligence
Harvest estimates use a trained model when suitable data is available. Growth-stage estimates use rules and recorded observations; outcomes can be checked against both.
No racks, towers or lights to buy from us
Full-stack vendors solve integration by owning every component, which works well until you want to change one of them. BeeGrow AI takes the other route: the platform reads and writes through open protocols, and the equipment stays your choice and your property.
That has a cost, and it is worth stating plainly. An integration has to be validated against the actual make and model rather than assumed, so we scope your hardware before promising anything. What you get in return is a platform that survives a supplier change.
- MQTT as the primary ingestion and command path
- Configured Modbus TCP polling for supported sensor hardware
- Actuators described by type, command set and MQTT topic, not hard-coded
- Equipment registered against the zone it serves, whoever made it
Actuator types the control layer models
Each is defined with its own command set, control direction and hard limits on intensity, duration and minimum interval before it can be driven.
- Heating and cooling
- Humidification and dehumidification
- pH up and pH down dosing
- Two-part EC dosing
- Water pumps and drain valves
- CO₂ injection and ventilation fans
- Lighting control, including spectrum channels
Web and mobile access
Web
Planning, design, recipes, analysis and reporting. Built for the desk work: laying out a site, comparing cycles, and answering the questions a board or an auditor asks.
Mobile
Live readings against targets, alerts, growth records and harvest capture on a phone. A connection is needed to save new records.
Live updates
Readings, alerts and operational status changes push to connected clients rather than waiting for a refresh, so an escalation reaches whoever is holding a phone.
Platform-wide operating standards
- Tenant isolation. Tenant scope is enforced at the gateway and data-access layers and covered by release tests.
- Role-based access. Permissions are enforced server-side and mapped to the job each user performs.
- Audit trail. Critical state changes record actor and timestamp context.
- UTC internally. Timestamps are stored in UTC and converted only at display, so cross-site comparison is sound.
- Live operations. Readings, alerts and operational status changes use push updates.
- Open data. Authenticated APIs, licensed per integration, and a full copy of your data on request.
The full index
Grouped by layer, for anyone who wants the whole list at once.
See BeeGrow AI on your own crop plan
A 30-minute walkthrough against your zones, crops and sensors. No slides unless you ask for them.
- Walkthrough led by someone who has built the system
- We map your zones, crops and sensors before the call
- Straight answers on what fits and what does not