FAQs

Fallow is currently in validation on a working farm in KwaZulu-Natal. We're not accepting new users until the validation period is complete. Join the waitlist to be notified when early access opens.

Yes. Fallow is offline-first by design. All data saves to your device immediately using a local database. Synchronisation happens automatically when you have connectivity. You'll never see a loading spinner blocking field work.

Fallow is designed for diversified operations running multiple crop types. Current validation covers sugarcane, avocados, macadamias, and timber. The system is crop-agnostic — activity types and phase definitions are configurable per crop.

Fallow captures GlobalG.A.P.-aligned data by default: weather conditions at application time, operator certifications, PPE confirmation, chemical batch numbers, GPS coordinates, and photo evidence. The fuel system is specifically designed for SARS reconciliation requirements.

Yes. Your operational data stays on your device until you choose to sync. When synced, data is encrypted in transit and at rest. We do not sell data to third parties, advertisers, or other ag-tech companies.

Fallow runs on iOS and Android phones and tablets. The interface is mobile-first, optimised for phone use in the field. We recommend a rugged case for field conditions. Web and desktop interfaces are planned for office-based reporting.

Every action saves locally first. When connectivity is available, Fallow synchronises in the background using a conflict-resolution system that handles multiple devices editing the same data. You can work for days offline and sync when you're back in range.

Yes. Fallow imports GeoJSON boundaries from QGIS or other GIS tools. The current validation farm imported ~500 fields with boundaries, centroids, and metadata. CSV import for field lists is also supported.

No. Fallow is designed for supervisor-mediated labour. Supervisors log work; workers don't need phones or logins. This is intentional to separate responsibility from execution.