Everything a farm actually runs on — fields, crops, livestock, tasks, money — is open source and self-hostable. The enterprise modules sit in a separate directory, licensed for organizations that need them. Same codebase, same data model, no vendored fork.
Not a demo tier. The community edition is the same application our cloud customers use for daily farm work — mapping, records, labour, stock and books — with no seat caps and no telemetry.
Draw plots on a PostGIS-backed map, track soil, rotation and per-field history offline-first.
Plantings, inputs, spray records and harvest yields, from seed lot through to graded output.
Animal registry, breeding and health events, daily milk recording per animal and per shift.
Assign work to team members, track hours and casual labour, weather-aware reminders on spray windows.
Sales, costs, payments and per-field profitability, with M-Pesa statement import and CSV export.
Seed, feed, chemicals and equipment with reorder points and consumption traced back to the field.
The same PWA our cloud users get. Records queue offline and sync when the phone finds signal.
Local accounts, role-based permissions per farm, and a full append-only audit trail of every record change.
The whole data model is reachable over a documented REST API with webhooks — build your own tools on top.
Everything a single farm or co-op needs to operate is in the open tree. What we license is the multi-tenant, marketplace and treasury machinery that only larger networks run.
Community releases follow a six-week train. Every entry below is tagged in the public repository.
Dates are targets, not promises. Items move when field testing in Nakuru and Meru says they should.
Anything released under AGPL stays under AGPL. Enterprise features are added to ee/, never moved out of the core.
Self-hosted instances ship with full export and a documented Postgres schema. Migrating to or from cloud is a supported path, in both directions.
Substantial changes land as RFCs before code. Co-ops running self-hosted instances get a vote in the release train review.
One compose file, a Postgres volume and a domain. Bring the cloud modules in later if your network outgrows them.