The operations OS for growers

Connect every decision to the work that matters.

Labor, tasking, IoT and integrations, operations, the mobile workforce and AI, on one live record of how your operation runs. Canopy turns changing conditions into clear priorities and coordinated work, alongside the ERP and systems you already rely on.

The operations OS

One system for the whole operation

Six parts on one live record of how your operation runs. Each one says where it stands today. Irrigation control is one module inside IoT: live, deep, and where Canopy started.

  1. Labor

    Live

    Actual hours and units by work type, against your own standards and baselines. Crews are modeled as capacity, not rosters.

  2. Tasking

    Pilot

    The day's work as tasks, scheduled and assigned, each with a zone, a time window, a headcount and a priority.

  3. IoT and integrations

    Live

    Devices in the yard, irrigation control among them, and the systems you already run: Business Central, Teams, Slack and webhooks.

  4. Operations

    Live

    One spatial spine of sites, blocks and grow zones, and one record of what happened, so labor, tasks and devices line up.

  5. Mobile workforce

    In build

    A crew app for tasks, picks and scouting in the yard.

  6. AI

    Early access

    An assistant built into Canopy, and your team's own assistant, Microsoft Copilot first, working on the same records and permissions.

How it works

From what changed to what happens next

  1. See

    Where the hours actually went

    Hours and units are recorded by work type and compared with your own standards and baselines, week by week. Crews are capacity, not rosters, so there are no wages or personal details to manage.

    Canopy labor log screen with hours and units entered by work type.
    Where the hours actually went
  2. Decide

    What changed in the yard

    Devices in the yard report in, and each morning irrigation run times are recalculated from yesterday's evapotranspiration and rainfall. What changed overnight is on the record before the shift starts.

    Canopy irrigation schedules screen listing sequences with run times.
    What changed in the yard
  3. Do

    Work that reaches the crew

    Tasks carry a zone, a time window, a headcount and a priority, so the plan and the shift are the same list. Tasks and scheduling are in pilot, and the crew mobile app is in build.

    Canopy tasks screen listing work by zone with priority and time windows.
    Work that reaches the crew

One system

The whole operation, connected

In the field

Built for the way a nursery day actually runs

  • By work typeactual hours and units, against your own standards
  • No wagescrews are capacity, not rosters, so no pay rates or personal worker records
  • Offlinethe on-farm device keeps running its schedule without internet
  • Dailyirrigation run times recalculated from local ET and rainfall

Your AI, your choice

Ask your own assistant about your operation

Canopy has an assistant built in, and connects to the one your team already uses through MCP, the open standard. Ask what ran, record the work and dispatch the next task, within the same permissions your team already has.

  • Microsoft Copilot
  • Claude
  • ChatGPT
  • Gemini
  • Codex
  • Cursor

How Canopy works with AI, MCP and the command line

Built to be yours

A platform that fits how you work

Canopy uses AI and modern engineering practice to give your operation a platform that fits how it works, instead of a fixed product you have to work around.

  • Live

    Shape it

    Your work types, standards, blocks, crews and roles are your own vocabulary, not a template.

  • Early access

    Build on it

    Your team builds the parts only you have, through the API, the connectors and your own assistant.

  • Early access

    Ask for it, inside the product

    Support, feature and bug requests are built in. An AI guide helps you write a clear request and confirm it before it is filed. It reaches the people building Canopy with the context they need, and you can see everything you have asked for.

Canopy ships continuously, with AI-assisted engineering and modern practice, so a good request can move from your team to the roadmap to a release without waiting for an annual version.

FAQ

Questions growers ask us

Who is Canopy for?

Growing operations, starting with container nurseries, whose crews and conditions change after the plan is made. Canopy is the operations OS for that team, modeled the way you already think about your operation: sites, optional blocks, and the zones inside them.

How does Canopy handle labor?

Hours and units are recorded by work type, and Canopy compares them with your own standards and baselines. Crews are modeled as capacity, not rosters, so Canopy stores no wages, pay rates or personal worker records.

How does work reach the crew?

Tasks are tied to a zone and carry a time window, a duration, a headcount and a priority. Tasks and scheduling are in pilot with early customers, and a crew mobile app for tasks, picks and scouting is in build. Ask us where each stands for your operation.

Do I need Canopy hardware?

Only for the parts that touch the yard. Where Canopy runs irrigation, one Canopy device per site connects to relay boards that switch your existing valves. We pair the device and map each relay to its valve.

What happens if the internet goes down?

Irrigation keeps running. The on-farm device holds its schedule and carries on without a connection, and it serves a local page on your farm network so you can see what it is doing.

How does weather-based scheduling work?

Once a day, Canopy takes yesterday's evapotranspiration and rainfall for your site and scales each zone's runtime from its own leaching-fraction test. Rain is subtracted and the result stays inside the limits you set for the zone. Weather comes from a public forecast service by default, or from your own Ambient Weather station.

Can we ask for changes?

Yes, from inside Canopy. Support, feature and bug requests are built into the product, with an AI guide that helps you write a clear request and confirm it before it is filed. Each request reaches the people building Canopy with the context they need, and you can see what you have asked for. In-product requests are in early access, with the assistant.

Who can see our data?

Only your organization. Every request is checked on the server against the organization it belongs to, and users have viewer, operator or administrator roles. Labor is recorded as hours by work type, so Canopy does not store wages or personal worker details. Your own systems can reach your data through the Canopy API, which is in early access.

How do we get started?

Request a demo and walk us through your operation. If it is a fit, we set up your organization and administrator account, your work types and crews with you, and, where Canopy will run irrigation, install the on-farm device and map your relays to valves.

Something else? Ask us at hello@canopy.ag.

Bring us the shift that keeps breaking

We are bringing a small group of growing operations into the beta. Walk us through your zones and your crew, and we will show you Canopy against them.

See the product