Frequently asked questions about VarmOS.

VarmOS is an estate management platform for enterprise-scale plantations and horticulture. It brings together two things usually kept apart: the daily operational modules — work planning, harvest, workforce, logistics, warehouse, cost — and an agronomy layer built on sensing and artificial intelligence. Both stand on the same data core: the block.

VarmOS is built and developed by Elevarm, an Indonesian agricultural technology company. The full background and product principles are on the About Elevarm.

varmos.id is the platform site — where you learn about capabilities, compare modules, and request a demo. Open to everyone, no account needed. app.varmos.id is the daily working application where registered users actually manage their estates, and it requires access rights granted by your company.

VarmOS primarily supports perennial fruit orchards—avocado, durian, longan, and mango—along with open-field horticulture, packing houses, and cold chains. Details are on the Commodities.

Yes. The foreman app is offline-first: harvest records, attendance, and input applications are stored on the device, then sync automatically once the network returns. This is not an add-on feature but a founding design assumption — most blocks genuinely have no signal.

Conflict resolution happens server-side, not on the device. Every record carries a timestamp, the identity of who recorded it, and its originating device. When two records collide on the same object, the system keeps both and flags them for the assistant to verify — no data is silently overwritten.

A mid-range Android phone is enough. No special hardware needs to be bought. For estates that want QR markers at collection points, weatherproof printed labels are all that is added.

Usually yes. Integration is done either by reading the weight indicator directly or through the database of the weighbridge system already running. We check the make and configuration during the initial assessment, before implementation begins.

From output actually recorded in the field, not from a manual month-end tally. Base quota, above-quota bonus, penalty, and overtime schemes are configured to your company's rules — not to built-in rules that force you to adapt.

Base models are available and usable straight away. But calibration against your estate's historical data happens during implementation so results reflect your soil types, varieties, and local weather patterns. Prediction quality usually only stabilises after one full harvest cycle.

No. Every operational module runs fully without a single sensor. Sensors become useful once you want the precision agronomy layer, and can be rolled out gradually starting with your highest-value blocks.

An existing subscription can be connected to VarmOS via API or scheduled files, and the imagery component of your plan adjusted accordingly. The same applies to sensors and drones you already own.

The figures shown on this site are illustrative, not a promise. Real accuracy depends on the quality of historical data, how consistently harvests are recorded, and how stable weather patterns are at your location. In a demo session we would rather compute it on your own data than quote a single generic number.

No. Every model finding passes four stages: the finding, a confidence threshold check, agronomist review, and only then a work order. The agronomist can approve, reject, or adjust it with reasons — and those reasons are recorded as training material for the next model round.

A pilot estate typically goes live in 8–12 weeks for the operational modules, plus 8–12 weeks for the sensing layer and agronomic models. Rolling out to further estates is much faster because the data structure already exists.

Block boundaries matter most. If your block map is already clean and verified, every later stage runs far more smoothly. Beyond that: crop master data, the organisational structure, and the cost account chart. We help tidy all three in the first phase.

VarmOS is designed to coexist, not replace. Cost and stock data can be pushed to SAP, Oracle, Odoo, or Accurate; attendance and bonus data to your existing payroll system. All that is needed is agreement on the data keys.

Our field operations team, on the estate itself, not through online video. Support continues until foreman adoption is genuinely stable — not until the training session ends. This is part of the implementation fee.

By default in data centres located in Indonesia. For groups with stricter security policies, private cloud and on-premise deployment in your own data centre are both available.

Your company. For data inside app.varmos.id, Elevarm acts as a processor handling data on your instructions, not as an owner. The details are set out in the data processing agreement and explained in the Privacy Policy.

No, unless you give written consent. The models working on your estate are calibrated on your own data, and that calibration is not carried across to another customer's account.

Yes, in open formats, at any time during the subscription and at termination. We treat the ability to leave as part of trust, not as something to make difficult.