Configurable crop-cycle monitoring
Configure a working view around the crop cycle: choose from 149 built-in parameters, add farm-specific rows and key dates, and keep observations, photos, stages, climate, irrigation, and available sensor data in one chronology.
Configured around the operation
The built-in library covers crop development, flowering, yield, climate, irrigation, and resource use. Add your own rows and keep only the parameters that support the production workflow.
Crop biology
Record growth, flowering, fruiting, yield, quality, and visual crop condition.
Environment and resources
Review crop development together with outdoor and indoor climate, substrate, irrigation, light, and resource use.
Cycle context
Key dates, stages, weather, and production location explain each value in the daily chronology.
A tomato cycle may track stem growth, leaf area, fruit set, yield, irrigation, and climate. A mushroom cycle may track mycelium colonization, pinning, mushroom size and weight, substrate conditions, and grow-room climate. The team sees the working set for the cycle, not the full catalog.
How the table is populated
Manual observations, connected measurements, and calculated parameters appear side by side. The source of each value remains clear.
Phenology, morphology, yield, product quality, photos, and specialist comments.
Start without sensors or automationClimate, light, substrate, irrigation, drainage, and weather data from connected sources, aggregated by day, night, or 24 hours.
No manual transfer when a source is connectedGrowth rate, leaf area and LAI, drainage percentage, water use, and light-use efficiency.
Calculated when the required source data is availableSelect the parameters you need, record observations manually, and attach photos. Add automatic sources later when they solve a defined production need.
From daily value to intraday detail
Open an available automatic value to inspect its intraday chart. See when a rise began, how long a peak lasted, and when the metric returned to its usual range.
Two days with the same average may have very different peaks, ranges, and duration of deviation.
History and comparison
Farm history remains available after the cycle. Revisit the same crop from a previous season and see where the current trajectory follows a successful cycle and where it diverges.
For plants, align observations by development stage and BBCH code; for mushrooms, use the production stage. Compare flowering with flowering, not simply July with July.
Review zones, current stages, and timing together to see what is on plan and where a transition is beginning to slip.
Context for people and AI
When crop, zone, stage, dates, observations, and growing conditions share one daily chronology, the current cycle can be compared with past and parallel cycles. That context supports both specialist review and connected AI tools.
A specialist reviews crop development together with conditions and production events.
A model works with cycle history, growing conditions, and production events, rather than an isolated number.
Crop monitoring questions
It is a configurable working view and daily log for an active growing cycle. Select the rows you need, and Gros.farm connects them by date with observations, photos, key dates, stages, and available automatic data.
Gros.farm provides 149 built-in parameters: 69 for crop growth, flowering, fruiting, yield, and photo records, plus 80 for climate, irrigation, light, substrate, and energy. There are also 20 types of key dates, a stage timeline, weather context, and custom parameters. Each monitoring table includes only the rows selected for that cycle.
Yes. Begin with manual observations, photos, comments, key dates, and growing stages. Add sensors and local automation later when they support a defined production task.
For plants, track growth, leaves, roots, flowering, fruiting, yield, and product quality. For mushrooms, track mycelium colonization, pinning, size, and weight. The same chronology can also include climate, light, irrigation, solution, substrate, drainage, weather, resource use, and farm-specific parameters.
Structured cycle history gives a connected model context such as crop, facility, stage, metrics, and events. The model can help compare facts, identify missing records, and formulate hypotheses for review. Assessment and decisions remain with the responsible production specialist.
Yes. Observation, parameter, date, and growing-condition history remains available. Open a previous cycle of the same crop and compare it with the current cycle at an equivalent stage or BBCH code.
Yes. A facility overview can show several cycles, their production zones, current stages, and timing. This helps identify delayed transitions and plan team work or harvest.
Build the monitoring view your operation needs
Select relevant rows from the built-in library, add farm-specific parameters, and begin with the data your team already has.
