Home · Estate Operations
Pillar 1 of 2Running the estate, not just reporting on it.
Every task, every tree, every kilogram of fertiliser, and every rupiah of cost is tied to one and the same land registry: estate, block, plot, down to the individual tree. Every consolidation stands on that.
Three gaps that keep estate decisions late.
Decision latency
On average 14–21 days from an event in the block to its appearance in a management report. By the time the information arrives, the chance to correct has passed.
Fragmented data
Harvest, HR, warehouse, weighbridge, and sensor systems each stand alone. Nothing keys them back to the block.
No feedback loop
Fertiliser recommendations get issued, but neither the execution nor the response is ever measured back against the same block next season.
Twelve modules that close the estate work cycle.
Switch on what you need. All of them share the same master data and land registry.
Command Center & Estate Map
One screen that answers the first question of every morning: what is off today. The land hierarchy — estate, block, cluster, plot — stands on a single geospatial registry, so every figure can be traced down to its own land object.
Tree Registry & Digital Passport
Tree crops are recorded as individuals, not merely as block aggregates. Each tree holds its own passport: identity, treatment history, latest condition, and photos — through to replanting progress.
Plant Census
Population recording runs end to end, from the field to the reviewer's desk: tag generation, direct submission from the device, progress tracking per crew, and a review queue before the figures are used.
Work Planning & Work Orders
The annual plan comes down into weekly plans and work packages, then into tasks that demand evidence. Scenarios can be simulated first, before labour and materials are locked in.
Workforce
The worker database, assignments, and attendance all flow into a working-day recap approved through the proper levels. Job rates are stored as versioned rules, not in one person's head.
Crop Health & Pest Surveillance
Field findings become cases that age and move, not notes that evaporate. Pest thresholds, the cultivation library, and weather forecasts sit in the same flow as the action taken.
Harvest & Material Inventory
Harvest records per land unit meet warehouse stock and actual fertiliser application on the same block. Input consumption always has a counter-record in the field, not merely a warehouse issue slip.
Water & Facilities Management
Reservoir readings, water networks, and the condition of estate facilities are recorded from the field — including while the device has no signal at all.
Cost, Alerts & Reporting
Budgets stand on the same land objects as the work itself. Alerts carry a full life cycle — disposition, verifier, and a recorded closure — so a warning never stops at being a notification.
Offline Field Mode
Ten field screens work fully without a network: tasks, attendance, inspections, readings, and the map. Idempotent sync keeps a duplicate submission from ever becoming duplicate data.
Cultivation Library & SOP Compliance
The right way to work is kept as a living document, not a folder of PDFs. Every SOP carries a version, an author, a reviewer, and a final approver — and its checklist drops straight into field work orders as inspection items.
Soil & Fertilisation
Fertiliser dosage starts from test results, not habit. Lab and portable test results are stored per zone along with their age — past 120 days they are flagged for renewal, past 180 days they count as expired — and the effectiveness of each treatment is re-assessed after application.
How a single working day flows through VarmOS.
Download the field pack
The map, task list, and land objects to be visited that day are downloaded to the device. After this the app needs no network at all until the data is sent back.
Attendance & task start
Attendance and task execution are recorded straight onto the device. Every record carries its time, its location, and who performed it — with no dependence on a signal.
Inspection, scouting & census
Crop health findings, reservoir readings, and tree records are captured where they happen — attached to the block, plot, or tree concerned.
Send field data
As soon as the signal returns, the queue goes out. A submission repeated because the network dropped never becomes two records on the server.
Verification & action
Submissions enter the review queue before they are used. Alerts that pass the threshold appear with a disposition and a verifier, then come back down as tomorrow's tasks.
Clean operations are the foundation. Precision agronomy is what lifts the yield.
Once field data is clean and tied to the block, the sensing layer and agronomic models finally have something worth working with — and their recommendations can drop straight into work orders in the same modules.
Satellite Monitoring
Vegetation index time series per land unit.
Cadence follows the imagery providerAnomalies & Alerts
Changes outside the expected range are flagged for review.
Thresholds are configurableSoil Sensors & Weather
Field readings and weather risk forecasts.
Optional, added in stagesField Verification
Sensing findings are proven on the spot, with photos.
Feedback is recordedTry it on a single pilot estate.
We use your own block structure, commodities, and cost chart — not demo data.