Room → line → rack → tier → tray
Represent the structure at the level where crops and work differ.
Gros.farm for vertical and indoor farms
Manage the farm by crop batch—not by room average
Connect rooms, lines, racks, tiers, trays, crop batches, stage recipes, light, climate and nutrient context, shift work, harvest, and output. Keep local automation in control of equipment while the production team manages the crop.
01
Lines, racks, and tiers
02
Crop batches and stage recipes
03
Light, climate, pH, and EC context
04
Output and energy-relevant history
Each tier has its own crop context
A room average can hide a weak batch
The same room can contain batches at different ages and stages. The production record should connect each batch to its actual tier, recipe, observations, work, and result.
Crop, variety, seed lot, and sowing date
Keep every active batch tied to its actual location.
Light, climate, nutrition, and work
Targets change after germination, transplanting, and during finishing.
Cut date, output, and quality
Review the batch outcome with its production history attached.
Farm registry
Model the operation before you measure it
Keep facilities, production areas, active crops or lots, and growing cycles in one structure. The registry gives tasks, observations, metrics, and analytics a shared place and production context.
Explore the farm registry
Stage recipes
Use a different recipe for every meaningful crop stage
Photoperiod, climate targets, irrigation, nutrient targets, and shift work should follow the crop stage and farm technology—not one timer for an entire room.
- 01
Sow
Record the crop, variety, seed lot, density, tray count, and date.
- 02
Germinate
Track emergence, uniformity, and the first controlled conditions.
- 03
Transplant
Record the batch move, new tier, actual quantity, and stage change.
- 04
Grow
Follow photoperiod, climate and nutrient context, and recurring crop work.
- 05
Finish
Assess uniformity, quality, biomass, and harvest readiness.
- 06
Harvest and reset
Record output and quality, then complete sanitation and the next setup.
Cultivation plans
The farm’s production standard—adapted to the real site
A cultivation plan can hold stages, target ranges, recurring work, recipes, photoperiod, and other production parameters. Templates are starting points, not universal recommendations: review every plan for the crop, facility, equipment, and production objective.
Explore digital crop plansShift work by batch
Give operators the exact line, tier, and instruction
Uniformity checks, pH and EC measurements, transplants, sanitation, maintenance checks, and harvest work should remain connected to the affected batch.
Inspect the tier, not just the room
Record the batch, stage, observation, photo, and follow-up work.
Keep pH and EC with the batch history
Manual or connected values need the correct source, unit, place, and time.
Assign work across lines and batches
Use dates, priorities, instructions, and responsible people.
Close the cycle with reset work
Keep cleaning and preparation tasks in the production sequence.
Work stays connected to production
Tasks carry the facility, growing cycle, cultivation-plan stage, date, priority, instruction, and assignee—not just a title and deadline.
Explore tasks and team →Monitoring and crop observations
Keep the biological event beside the operating data
Add manual observations, key dates, photos, comments, and available automatic or calculated values to the active growing cycle. A shorter, consistently updated monitoring set is more useful than a large table the team cannot maintain.
Production analytics
Compare crop recipes with actual batch results
Use connected stage, lighting, climate, nutrient, work, and output data to investigate performance. Do not treat correlation as proof of causation.
Days by stage and harvest date
Compare batches of the same crop and route.
Yield per tray or production area
Use stable area, tray, and harvest definitions.
Uniformity and marketable share
Keep consistent product and grading criteria.
Clear control boundary
Production management above reliable local automation
Gros.farm does not replace PLCs, controllers, SCADA, or local safety scenarios. The local layer remains responsible for physical operation and safe autonomous control.
Operate and protect equipment
Pumps, valves, ventilation, lighting, dosing, interlocks, and emergency scenarios.
Connect the crop plan and result
Stages, targets, schedules, tasks, data history, analytics, and supported configuration exchange.
Fit the production model
Different crops need different indoor production routes
Configure the stages, recipe parameters, work, and quality checks around the crop and facility.
Lettuce and baby leaf
Batches, transplanting, multi-tier growing, harvest, and output.
Basil, arugula, and others
Variety, photoperiod, biomass development, aroma, quality, and cutting.
Microgreens and young plants
Seed lots, density, germination, lighting, harvest, and sanitation.
GFAi with farm context
Ask questions across connected indoor crop cycles
GFAi can help compare batches and surface missing evidence. It does not replace a grower, plant scientist, or controls engineer.
It does not replace the grower, agronomist, technologist, or controls engineer responsible for the decision.
Questions to investigate
- Which tiers stayed outside the stage target most often?
- How did the recipe differ between two comparable basil batches?
- Which pH, EC, or work records are missing before we compare output?
Start with one working production contour
Prove the daily workflow before scaling the farm
You do not need to digitize every site, crop, and integration at once. Start with one active cycle that the team can keep current.
- 01
Add one production line
Create its racks, tiers, and current batch locations.
- 02
Adapt one crop recipe
Add stages, target ranges, photoperiod, nutrition context, and work.
- 03
Run the active batch
Record the next shift and compare the first plan-versus-actual result.
Related production systems
Explore another sector
Controlled grow roomsMushroom farms
Connect grow rooms, compost or substrate lots, biological phases, climate context, shift work, flushes, yield, and quality.
Protected cultivationGreenhouse farms
Connect crop stages, climate targets, irrigation, crop work, observations, and harvest results by greenhouse block.
Cut flowers and ornamentalsFloriculture
Coordinate flower batches to a target market date with crop stages, climate context, work, cutting, grade, and actual output.
Propagation and planting materialPlant nurseries
Track plant lots, provenance, locations, transplants, recurring care, grading, losses, and readiness for sale or transfer.
Questions before setup
What to know about this sector solution
What is the difference between a vertical farm and an indoor farm?
Vertical farms usually use multi-tier crop placement. Indoor farming is broader. Gros.farm follows the actual structure—rooms, lines, racks, tiers, trays, and batches—rather than relying on the label.
Can Gros.farm manage lighting and nutrient recipes?
Cultivation plans can store stage targets, photoperiod, nutrient context, irrigation, and work. Sending settings to equipment depends on an assessed integration; local controllers remain responsible for physical operation and safety.
Can we start without automation?
Yes. Start with the registry, batches, cultivation plans, tasks, and manual observations. Connect sensors and local systems when the value and compatibility are understood.
Will Gros.farm guarantee lower energy use or higher yield?
No. The platform helps connect operating context and crop results so the team can test changes on its own facility. Outcomes depend on the crop, equipment, process, data quality, and decisions.
Controlled-environment production
Build one connected production history
Manage rooms, lines, racks, tiers, crop batches, recipes, light, nutrient context, shift work, output, and quality.