Skip to content

Agrobotics

Contributor Use Case

Meet Agrobotics the company behind EnkiOS: a hydroponic and controlled-environment operating system designed to run on the LAB0 AI Foundry.

Together, they give growers a way to run serious automation and edge AI without disappearing into a tangle of proprietary boxes, cloud dashboards, and vendor lock-in. EnkiOS treats every LAB0 edge farm node as one control pane of glass for control room: pumps, valves, lights, meters, cameras, and sensors all wired into one local-first AI brain.

Agrobotics builds the hardware integrations, automation playbooks, and guardrails that make EnkiOS feel less like a science project and more like something you can trust to run all night while you sleep.

What Problem It Solves

Most farms and greenhouses grow into complexity by accident:

  • A timer here, a thermostat there, a "smart" relay that only talks to one app.
  • Spreadsheets, whiteboards, and notebooks that never quite match what the system is actually doing.
  • Late-night drives to "just go check" when the weather swings or a pump sounds wrong.

Add a second greenhouse, a headhouse, or an off-site building and everything multiplies. No one has the full picture, and every new controller is one more silo.

How Agrobotics / EnkiOS Works with LAB0

EnkiOS runs directly on LAB0 edge compute nodes, right where the work happens:

  • Each farm, greenhouse, silo can run LAB0 Edge Nodes and can host an EnkiOS instance, wired into local pumps, valves, sensors, and lights.
  • Agrobotics ships the device profiles and automation templates so those nodes come online fast and in a known-good state.
  • LAB0’s Foundry sees every EnkiOS instance as another edge workload: monitored, logged, and manageable from a central pane of glass.
  • Optional Reticulum MANET links sites together so data and models can sync, even when traditional backhaul is unreliable.

In practice, that means a grower can open their phone, open a dashboard, and see exactly what that environment is doing—without depending on the public internet.

Before Agrobotics / EnkiOS

Before Agrobotics and EnkiOS, even technical growers end up with:

  • One-off Raspberry Pi projects that no one wants to maintain.
  • Vendor apps that break the moment Wi‑Fi, firmware, or terms-of-service change.
  • No clean way to expand from "one cool setup" to "this runs my entire operation."

After Agrobotics / EnkiOS

With Agrobotics / EnkiOS running on LAB0:

  • One mental model: Every site, every tank, every zone behaves like the same system.
  • Local-first safety: The control logic lives on the edge nodes, not in someone else’s cloud.
  • Smarter automation: Playbooks encode best practices for irrigation, dosing, climate, and emergency responses.
  • Future-proofing: New sensors, cameras, and edge AI models can be slotted in without tearing everything apart.

Why This Matters to Contributors

Agrobotics and EnkiOS sit right at the intersection of open hardware, open source, and real-world food systems. Contributors help underwrite:

  • New hardware drivers and integrations.
  • Better automation templates tuned for real growers, not lab demos.
  • UI and data model improvements that make EnkiOS usable by people who are busy actually growing.

In return, Contributors get access to a production-grade edge control stack that runs on LAB0 and evolves in the open. Instead of paying a vendor to wall off their data and workflows, they help build a shared toolkit that makes controlled-environment agriculture more resilient for everyone who plugs in next.