Vertical farm management software for multi-tier racks

The zone is the unit everything hangs off. Its racks, shelves and growing cells are described once in the rack and shelf model, and sensors, the active recipe and every record sit against that zone, so two zones growing the same crop compare like with like.

You do not set each zone up by hand. A shelf configuration can be duplicated and applied to other zones, and the same recipe can run in every zone growing that crop. When a zone changes, the change is recorded against that zone and the rest of the site is untouched.

Daily light integral is calculated from the PPFD readings of a light sensor in the zone, never from lux. Where no PPFD sensor reports, there is no DLI to review.

The hours a DLI target needs follow by arithmetic: the DLI multiplied by 1,000,000, divided by the product of PPFD and 3,600. You enter the lighting load, and each price period on the site’s intelligent electricity tariff is tried as a start time, including windows that run past midnight. Tariffs are compared on the cost of running that load, and the pricing sits beside the crop requirement so you can see what a schedule costs before you apply it. The grower decides whether to use it.

The method is worked through on the energy and tariff optimisation page and in buying light when it is cheap, and the grow light running cost calculator runs it on your own figures.

pH and EC are read against the targets in the recipe for the batch and stage in that zone. How much detail you see depends on the probes you have and how often they report.

Water temperature, dissolved oxygen and ORP are recorded as readings alongside pH and EC. Recipes carry no dissolved oxygen or ORP targets, so these readings inform your judgement rather than sitting against a target band.

The platform also holds nutrient recipes, solution tanks, dosing records and lab analyses. A dosing event can carry the pH and EC measured before and after it, and tank refills are recorded as their own action.

Monitoring comes first. Sensors publish over MQTT as the primary path, with configured Modbus TCP polling where that suits the hardware. Every integration is validated before it is promised, and control is commissioned when the readings are trusted.

Automation is started and stopped per zone, and the active recipe sets the targets for the zone it runs in. Fixed limits sit below the control loop, and no recipe can raise them. An emergency stop takes the zone out of automation and sends stop commands to its configured dosing, water, CO₂ and HVAC equipment, with ventilation commanded to full. Lights are left as they are, and humidifiers are not part of the sequence.

If you only ever want monitoring, the platform stays there. The evaluation guide lists the control questions worth putting to any vendor.

A cultivation plan can start in a nursery zone and move to a production zone when the nursery phase ends. Each plan names its nursery and production zones and the recipe stage it moves at.

The platform shows when the batch is ready to move, and the move is confirmed and recorded rather than assumed. The batch keeps one history from sowing through the move to harvest, so germination, spacing and production sit on the same record.

BeeGrow AI supplies software, not hardware. Racks, lights and HVAC stay your choice and your property, and your controllers stay in place. Connections to them are scoped by make and model and confirmed in writing before you sign.

Two limits to note. There are no seed lots and no recall workflow in the product, so lot questions are answered from the harvest batch number, which stock and order lines can carry. If a connection or a workflow sits outside the scope above, you hear that during scoping rather than after.