Start free

Greenhouse operations

Greenhouse management software

Manage blocks and crops, growing protocols, plant development, climate, irrigation, and work in one production system.

Try for free
Agronomist inspecting plants in a greenhouse
Block 03 · TomatoFruitingWeek 12 of the cycle
Microclimate24,3 °C within target range
Work today6 / 7one item needs attention
TomatoCucumberLeafy greensSeedlings
One platform

One production context

  • Growing plans
  • Farm registry
  • Task tracker
  • Monitoring
  • Climate
  • Irrigation
  • Crop protection
  • Analytics
  • AI platform

Crop management above automation

The climate computer controls equipment. Gros.farm helps manage production

01

Automation layer

What equipment is doing

  • temperature and humidity;
  • vents, screens, and heating;
  • irrigation cycles and fertigation.
02

Gros.farm

Why it matters to the crop

  • stage, variety, and target regimes;
  • observations and agronomist decisions;
  • team work and cycle outcome.

Instead of disconnected screens and spreadsheets, the team gets one story: plan → actual conditions → action → harvest.

Production records

Mirror the real structure of your greenhouse complex

Record what grows where: area, crop, variety, batch, density, dates, owners, and the planned outcome of every cycle.

  1. 01

    Complex

    Sites, units, zones, and responsible staff.

  2. 02

    Block

    Area, occupancy, crop, and equipment.

  3. 03

    Batch

    Variety, plant count, density, and dates.

  4. 04

    Cycle

    Stages, work, yield, and quality — plan versus actual.

Unified registryarea occupancy, plant count, and yield — plan versus actual

Phenology and stages

Track plant development over time

A stage is the biological and operational context of the crop. Targets, tasks, recipes, photoperiod, and automation setpoints change with it.

  1. 01

    Preparation

    Block, substrate, and cycle plan.

  2. 02

    Planting

    Batch, variety, and density.

  3. 03

    Rooting

    Establishment and starting regimes.

  4. 04

    Vegetative growth

    Growth, training, and nutrition.

  5. 05

    Fruiting

    Load, quality, and forecast.

  6. 06

    Harvest

    Volume, grade, and plan versus actual.

Growing plan

Digitise the growing protocol by stage

Combine stages, indicators, tasks, recipes, and photoperiod in a working growing plan. When the stage changes, the team and automation receive current targets.

  • Stages with biological and operational context
  • Temperature, humidity, VPD, radiation, and other indicators
  • Recurring tasks, targets, and recipes for every stage

Crop protection

Connect observation, agronomist decisions, and crop protection

Record an issue in the context of a block and stage, assign treatment, confirm completion, and preserve the result in crop history.

  1. 01

    Observation

    The issue is marked for a block or zone.

  2. 02

    Context

    Crop, stage, conditions, and history are visible.

  3. 03

    Decision

    The agronomist defines the action and rate.

  4. 04

    Treatment

    The task receives a due date and owner.

  5. 05

    Actual

    Completion is confirmed in the system.

  6. 06

    History

    The decision can be compared with the result.

ObservationAn issue is marked in a specific zone

The agronomist identifies the cause, chooses an action, and assigns treatment.

Production recordCompletion and comments remain in history

A dedicated crop-protection timeline is being developed as a connected monitoring layer.

Daily monitoring

Observe crop development, not isolated numbers

The journal combines manual observations, photos, sensor aggregates, calculated indicators, and stages to show how plants and conditions changed over time.

  • Current, completed, and upcoming cycle stages
  • Manual, calculated, and automatic indicators
  • Photos, comments, and key dates

Climate driven by the protocol

Send stage setpoints to the local control layer

Day and night targets for temperature, humidity, CO₂, and circulation come from the growing plan. A smooth plan limits temperature change while local automation controls ventilation, heating, and other equipment.

Automation system integrations
  1. 01
    The growing plan sets the target

    Climate setpoints change with the crop stage.

  2. 02
    Climate receives the plan

    Day, night, transitions, and permitted temperature rate of change.

  3. 03
    The local node executes

    The controller autonomously operates ventilation, heating, and other equipment.

Professional irrigation

Trigger irrigation by accumulated solar radiation

Gros.farm calculates the plan and sends it to the local node. In RADIATION mode, a new cycle starts when the configured radiation sum is reached through a direct sensor or integrated light data.

RADIATIONSLOTSSAFETY
Radiation periodSum since last irrigation
84of 120 J/cm²

When the threshold and minimum interval are reached, the local node starts the calculated delivery.

  • Technical irrigation

    Morning start based on VPD, radiation, and substrate temperature when a sensor is available.

  • Delivery calibration

    Emitter flow measurement converts the ml/m² target into irrigation duration.

  • Fallback scenario

    If connectivity or a sensor fails, the local node switches to a deterministic schedule.

Gros.farm sets the plan and schedule. The local controller operates pumps, valves, and dosing.

Team and shift

Work starts in the block context, not in a chat

A task already contains the site, crop, operation, due date, and owner. The worker records completion while the manager sees delays before they affect the next stage.

  • Recurring work from the growing plan
  • Urgent tasks from inspections or deviations
  • Completion records, comments, and photos

Cycle analytics

Explain outcomes through the growing protocol, not only the final number

Compare blocks and cycles by timing, output, and quality. The chart shows stages, events, conditions, and completed work that help explain the cause.

plan / actual

Yield

By block, crop, and cycle.

kg / m²

Productivity

Across comparable production cycles.

grade

Quality

Categories and share of off-grade produce.

events

Drivers

Conditions, observations, and completed work.

Gros.farm AI platform

A workspace where the team and AI share one production context

AI sees the farm structure, protocol, indicators, tasks, and events—not an isolated file. It helps find gaps and compare cycles, while crop decisions stay with the specialist.

Explore AI capabilities

Questions you can ask your farm data

  • What threatens the production plan today, and where is a decision needed?
  • Which indicators left the growing-plan ranges, and for how long?
  • What happened to temperature, VPD, irrigation, and light before growth slowed?
  • Is irrigation fully configured for the new stage, and which parameters are missing?
  • How can the next cycle plan improve, and which observations support the changes?
AI prepares a working hypothesisThe agronomist reviews it and makes the decision

First working loop

Start with one block—without a major implementation project

Transfer the current structure and protocol, add the next jobs, and begin recording actuals. Add sensors and integrations when they become useful.

  1. 01

    Add a block

    Recreate the familiar structure down to a zone or row.

  2. 02

    Load the protocol

    Stages, work, and key target indicators.

  3. 03

    Start the current cycle

    Assign the next tasks and begin recording actuals.

Already managing records in Excel?

Use your spreadsheets as source material for import. Data migration does not require a separate module.

Other growing formats

If your production works differently, explore a sector-specific solution

Protected and open field

Berry production

Mother stock, cycles, harvests, and berry quality.

Field production

Open-field vegetables

Plots, weather windows, treatments, and harvest.

Planting material

Nurseries

Batches, transplanting, care, and sale readiness.

Equipment connection

Automation integrations

Data, target regimes, and a reliable local control layer.

Questions and answers

What to know before launch

Does Gros.farm replace a climate computer?

No. Climate computers and local controllers operate equipment. Gros.farm connects their data and regimes with the crop, stage, protocol, work, and production outcome.

Can we start without sensors or automation integration?

Yes. The first workflow can use the block structure, growing plans, tasks, manual observations, and built-in external weather data. Add sensors and automation where they provide practical value.

Can we manage multiple blocks, crops, and cycles?

Yes. Every block keeps its structure, and each production cycle has a crop, variety, stages, growing plan, tasks, indicators, and final result.

Which data can be connected?

Gros.farm can use manual observations, external weather, sensors, and local automation data through available integrations. The exact setup depends on your equipment.

How does solar-radiation irrigation work?

In RADIATION mode, the system accumulates solar radiation from a sensor or integrated light data. After the threshold and minimum interval are reached, the local node executes the calculated irrigation. Interval periods and a fallback schedule are also available.

What is technical irrigation?

It is a separate morning run that can depend on VPD, radiation, and substrate temperature when a sensor is present. Its parameters are configured separately from the main irrigation periods.

Can we record crop-protection applications?

Create a treatment as work tied to the site, crop, and stage, assign an owner, and save completion. A dedicated crop-protection timeline is being developed as a connected monitoring layer.

What should we do with existing spreadsheets and growing plans?

Import and use them as a foundation. Start with one block and the current cycle, validate the structure in daily work, then scale it to other sites. Import does not require an extra paid module.

How does AI work in a greenhouse operation?

AI works with production context: sites, stages, indicators, tasks, and events. It helps find discrepancies and form hypotheses, but it neither replaces the agronomist nor operates equipment independently.

What happens to automation if the internet is lost?

The local layer continues autonomously according to its configuration and fallback scenarios. The cloud system should not be the only execution point for critical commands.

Does the solution suit berries, flowers, and vertical farms?

The platform foundations support different protected-growing formats, but their protocols and key workflows differ. Dedicated sector pages and configurations are available for them.

Next step

Build one greenhouse block in the system your whole team uses

We will show how to transfer your structure, protocol, and current cycle using your operation as the example.

Start for free