Start free
Multi-level racks with plants on a vertical farm

Vertical farm software

Manage your vertical farm as one production system

Connect racks and tiers, batches, crop protocols and recipes, lighting, microclimate, irrigation, shift work, and each cycle’s result.

Try for free

One production context

From seeding to dispatch—for every batch and zone

  • Racks and tiers
  • Batches and cycles
  • Protocols and recipes
  • Photoperiod
  • Climate
  • Irrigation and solution
  • Automation
  • Shift tasks
  • Analytics
  • AI platform

Every tier has its own microclimate

A room average cannot show what happens to lettuce on the fifth tier

Airflow, light, humidity, and solution delivery vary by zone and height. Link data to rack, tier, tray, batch, and stage.

01

Location and batch

Room, line, rack, tier, tray, crop, variety, and seeding date.

02

Stage recipe

Photoperiod, climate ranges, nutrition, irrigation, and recurring work.

03

Production actuals

Environmental readings, observations, photos, and completed shift tasks.

04

Cycle result

Harvest date, actual output, and lessons for the next batch.

Vertical farm registry

Map the farm down to each tier and batch

Recreate the hierarchy from site and room to rack, tier, and tray. Store crop, variety, seeding, density, planned output, stage, and owner for each batch.

  • Room, zone, line, rack, tier, and tray
  • Crop, variety, seed lot, and production cycle
  • Seeding, transplant, planned and actual harvest dates
  • Area, plant count, output, and variance from plan
FarmRoom 2Line BRack 07
Rack 07 · basil4 batches at different stages
Tier 04
BAS-2407-AFinishing
day 12
Tier 03
BAS-2407-BVegetative growth
day 9
Tier 02
BAS-2407-CAfter transplant
day 5
Tier 01
BAS-2407-DGermination
day 2

Crop protocol and growing recipes

A separate light, climate, and nutrition recipe for every stage

The protocol runs from germination to harvest. Each stage combines photoperiod, climate, pH and EC, irrigation, and shift work. Adapt it to the variety, equipment, and batch target.

How crop protocols work

Lighting is part of the protocol and cost

Change the lighting by stage, not with one timer for the room

Connect photoperiod and target and actual light to the batch and recipe. Gros.farm preserves modes, compares tiers, and can send supported setpoints locally.

Validate economics with actual resultsCompare the lighting recipe, batch outcome, and energy use before scaling changes.
Batch BAS-2407Vegetative growth · day 9
Photoperiod
18 h
Day starts
22:00
Light intensity
actual / target
Mode change
by stage

Move the day to favorable tariff hours only when the crop protocol allows it.

Hydroponics and irrigation

Connect the nutrient recipe to the batch and actual delivery

Set target pH and EC, solution temperature, duration, and irrigation frequency. Enter actuals manually or through an available integration.

Protocol

Nutrition recipe by stage

  • Target pH and EC
  • Irrigation duration and frequency
  • Solution temperature
  • Shift instructions
Production actual

What the batch actually received

Solution pHlatest observation6.1
ECavailable data1.7
Irrigationlatest event09:40
Production layerGros.farmstage · targets · tasks · history · analytics
Local controlControllers and equipment
  • LED lighting
  • HVAC and dehumidification
  • Pumps and valves
  • CO₂ and ventilation

Climate and local automation

The protocol sets the mode; local automation executes it reliably

Gros.farm links readings to zones and batches, compares them with the recipe, and can send setpoints. Controllers and safety logic remain autonomous.

  • Temperature, humidity, CO₂, VPD, and dew point
  • Lighting, ventilation, cooling, drying, and humidification
  • Setpoint, mode, and event history by stage
  • Integration is assessed for specific equipment
Automation system integrations

Shift work and production result

The shift gets specific work; the grower gets an explainable result

Tasks connect to location, batch, worker, and deadline. After harvest, compare output with the recipe, actual conditions, and completed work.

Today · Room 2Shift tasks

  • Check uniformity on upper tiersLine B · by 10:30

  • Check pH and EC after adjustmentSolution unit 2 · grower

  • Transplant batch LET-184Rack 12 · 14 trays

Batch LET-181Plan / actual
Cycle
24 daysplan 23
Harvest
Actualas entered
Output
Comparisonwith batch plan

ProtocolConditionsWorkResult

GFAi

Gros.farm AI platform

Ask AI about growing cycles, not another spreadsheet

Tiers, batches, recipes, actual modes, tasks, and output form one context. AI compares cycles and finds exceptions and gaps; specialists decide changes.

Explore AI capabilities

Questions for vertical farm data

  • Which tiers had light exceptions at the same time as batch delay?
  • How did the recipe of a strong basil cycle differ from a weak one?
  • Which batches stayed in finishing longer than planned?
  • Where did pH or EC exceptions coincide with loss of uniformity?
  • Which shift tasks are most often completed late?
  • Which data is missing to improve the next cycle’s protocol?
Answer formatFacts, unknowns, and a hypothesis for specialist review

Not one template for every crop

Lettuce, microgreens, and seedlings need different recipes

Crops differ in cycle length, density, light, nutrition, and work. Keep a separate protocol and proven recipe for each crop and variety.

01

Leafy greens

Lettuce and baby leaf

Batches · transplant · multi-tier finishing · harvest · output
02

Herbs

Basil, arugula, and other crops

Variety · photoperiod · biomass · aroma and quality · harvest
03

Short cycle

Microgreens

Seed lot · density · germination · light · harvest · sanitation
04

Plant material

Seedlings and young plants

Trays · growth stages · hardening · transfer readiness

First working loop

Start with one line and the current batch

Add one rack, the current batch and recipe, and upcoming work. Scale the loop after the first cycle.

  1. 01

    Build the structure

    Add one line, racks, tiers, and current batches.

  2. 02

    Import the recipe

    Set stages, targets, photoperiod, nutrition, and upcoming work.

  3. 03

    Run the shift

    Record actuals and compare the first cycle with plan.

Already have sheets, procedures, and recipes?

Import the structure and use the current recipe as the first cycle’s base. Import is free.

Related solutions

Go deeper into the production layer you need

Technology foundation

Crop protocols

Stages, recipes, metrics, photoperiod, and tasks.

Engineering layer

Automation integrations

Data and setpoints above autonomous local controllers.

Work with context

AI in agriculture

Questions for connected batch and cycle data.

Adjacent format

Greenhouse farms

A separate production loop for protected cultivation.

Questions and answers

About software for vertical and indoor farms

How does a vertical farm differ from an urban or indoor farm?

A vertical farm usually uses multi-tier crops. Indoor farming is broader, while urban farm can include greenhouses or local production. Gros.farm follows the real structure: zones, lines, racks, tiers, and batches.

Which crops can use Gros.farm?

Managed cycles for leafy greens, herbs, microgreens, seedlings, and other indoor crops. Protocols, metrics, and work adapt to the farm.

What is a growing recipe in Gros.farm?

A repeatable set of stage parameters and work: photoperiod, climate ranges, target pH and EC, irrigation, and shift tasks. Compare it with actual conditions and output.

Can we start without sensors and automation?

Yes. Start with the registry, protocol, batches, shift tasks, and manual observations. Add sensors when their practical value and engineering design are clear.

Can existing controllers, lighting, and climate systems connect?

It depends on equipment and available integration. Gros.farm connects to a local control node while local controllers remain autonomous. Contact us to review the design.

Does Gros.farm control the nutrient dosing unit?

Targets and irrigation modes live in the protocol, while actual pH, EC, and events link to the batch. Direct control depends on verified equipment integration.

Can the software reduce energy costs?

Gros.farm does not promise a fixed saving. It links photoperiod, modes, actuals, and batch results so the team can test changes on its own equipment.

Does AI replace the agronomist or grower?

No. GFAi compares cycles, finds exceptions, and frames testable hypotheses. Specialists decide changes to light, nutrition, climate, or protocol.

Next step

Run one batch through Gros.farm

We will show how to connect farm structure, growing recipe, actual data, and batch result.

Start for free