Controls & Automation
Advise. Approve. Or run it closed-loop.
Recipe-driven setpoints, lighting and fertigation — with a ladder of autonomy you set per system, not all at once.
Automation in a farm is not a switch. Handing over the lights is a very different decision from handing over the dosing pumps, and any vendor who asks you to trust both on day one has not run a farm.
Digital Cultivation gives you a ladder. Every actuator class — lighting, dosing, climate — sits in monitor, advise, approve or auto, independently. Start in advise, where the platform tells you what it would change and why. Move to approve, where it drafts the change and waits for you. Go to auto only where you have earned the confidence.
Crop targets live in the recipe; the plumbing lives in Automation. Manual overrides carry a required expiry, so an override can never silently become policy. And there is a kill switch that says exactly what it is doing.
Questions
The things people actually ask.
What happens if the platform loses connectivity?
Actuators default to a safe state. Safety is enforced at the edge, not by a cloud service promising to stay up.
Can I automate one zone and not another?
The autonomy ladder is set per actuator class for a facility, so you can run lighting in auto while dosing stays in approve. Within advise mode, the engine will surface recommendations zone by zone.
Can it drive third-party equipment?
Yes. The platform speaks to third-party sensors and controllers through adapters, so it can run on a farm it did not build.
See Controls & Automation on a real farm.
We'll walk an order all the way through to its margin — on live farm data, not a slide.