Anywhere in agriculture, the records exist. They're just not in any single place.
It doesn't matter whether you run a 50-hectare vineyard, a mid-size mixed enterprise, or a 5,000-head station — the shape of the problem is the same. NLIS movements live in one app. The spray diary lives in another — the one the agronomist insists on using. The treatment records the vet uploaded sit as PDFs in an email thread. The workforce onboarding paperwork is in a Google Drive folder. The bank reconciliation lives in Xero. The compliance report due next Friday will be a Word document, typed up by hand the Thursday before.
Six apps, six logins, six exports, six places where the same operation's own records can disagree with each other. The smaller operations run fewer apps but carry the same compliance burden. The larger ones run more apps with more people maintaining the seams between them. Both end up re-keying the same data.
Agriculture, despite being the original economy of trust — paddock to plate, season to season — has drowned in the tooling that was supposed to support it. It runs on spreadsheets that don't talk to spreadsheets, paper diaries that get re-typed into compliance PDFs, ledgers that arrive months after the fact, and a value chain where every party — the farmer, the lender, the buyer, the processor, the carrier — maintains their own private record of the same load.
We think it's time to fix this. Not with another app. With an operating system.
The point-tool trap
The agtech market is full of best-of-breed software. Genuinely good products, built by genuinely good teams, each solving one slice of the operation well.
A spray diary that does ChemCert and APVMA withholding periods properly. A livestock tracker with NLIS integration baked in. A standalone accounting package with biological asset valuations. A compliance reporter that exports clean LPA paperwork. A workforce app for managing onboarding and Fair Work awards. A driver app for carriers. A buying platform for grain.
Picking the best of each and gluing them together with CSV exports, webhooks and Zapier feels like it should work. In practice, three things go wrong — and they go wrong reliably.
Records drift apart. When the spray diary lives in App A and the financial entries live in App B, the version that ends up in the audit pack is whichever you re-keyed most recently. Every gluing point — every CSV download, every webhook, every “let me just paste this in” — is a place for the records to disagree. By the time the auditor or the buyer asks, you're not sure which version is true.
The seams cost you the value chain. Your bank can't see your livestock register. Your buyer can't see your compliance status before they bid. Your processor can't push the settlement entry into your accounting. None of the stitched-together apps were designed to talk to your lender, your buyer or your processor — so they don't. The friction between your operation and the people you transact with is the friction between your apps.
Every integration is a relationship you maintain. When App A pushes an update and breaks the CSV format, you find out the morning you're trying to generate an audit pack. The total cost of ownership of “best of breed, stitched together” is not the per-app license bill. It's the licence bill plus the hours you spend re-aligning the data, plus the deals you didn't close because the proof wasn't there, plus the compliance moments that cost you weeks of preparation instead of one click.
The point-tool model isn't a bug of the agtech market. It's the natural outcome of how SaaS economics work. You can fund a small team to build the world's best spray diary, charge $50 a month for it, and have a viable business. You can't fund a team to build the world's best operating system unless you're willing to underwrite the much-longer arc it takes to get the connected piece right.
We are, and we are.
What an operating system actually means
Operating systems do three things that apps don't.
They provide one place where the records live. Not “App A's records, with App B pulling a daily export of them” — one place, one ledger, one set of identifiers. When you record a treatment, that record is the same record the audit pack reads, the same record the buyer's quality filter reads, the same record the processor's settlement statement reads.
They give you primitives, not products. Apps ship features; operating systems ship verbs. A spray diary is a feature. The verb is “record a chemical application against this paddock, with this delta-T and this wind reading, with these withholding periods enforced at task assignment, and the result available to anyone with a stake in the produce that comes off it.” The verbs compose. Once you have them, the features fall out for free.
They make the connections cheap. When the bank wants a real-time view of biological asset positions for a covenant check, that's not a project — it's a permission. When the buyer wants to bid on the next shipment with the assays and chain of custody attached, that's not a separate marketplace integration — it's the listing the producer already created. When the carrier delivers and the settlement should post to both ledgers, that's not a manual reconciliation — it's the next transaction.
This is what we mean when we say RedEarthOne is the operating system for agriculture. Not the slogan. The actual structure.
Five connected workspaces, one ledger
The platform ships as five workspaces that share the same tenant, the same identity model and the same ledger.
For the farm itself: fields, paddocks and crop assignments drawn on the map; livestock with pedigree, breeding and welfare records; spray diary with ChemCert, delta-T and APVMA withdrawal periods enforced at task assignment; workforce with Fair Work award awareness; compliance and audit packs generated on one click.
For the bank or lender: a read-only window into the borrower's operating data — by the borrower's permission — with AASB 141 biological asset positions, live debt service coverage, livestock movements and compliance status sourced directly from the records the farmer already maintains. No annual document chase.
For the buyer and the marketplace: live listings of grain, livestock, dairy, fish, fibre and produce with the assays, the certifications and the chain of custody attached before the bid. In-platform contracts. Settlement that flows back into the producer's books in the same transaction.
For the processor: gins, packers, abattoirs, dairies and fisheries with lot receival, through-plant tracking, settlement statements and a back-channel to the producer's accounting that closes the loop end-to-end.
For the logistics carrier: a driver app, a dispatcher console, geofenced GPS tracking, shipment-level event ledger, and auto-settle on delivery into both the producer's books and the carrier's revenue ledger.
The capability set is broad and we'll keep saying that. But the differentiation isn't that we ship all five workspaces. It's that they're all reading and writing to the same record set. Every kilo through the plant ties back to the paddock it came from. Every shipment ties back to the lot it carries. Every record carries provenance, every change is hashed into a Merkle root, and the chain of custody from paddock to plate is verifiable end-to-end.
Where we are
We're early. RedEarthOne is in early access right now. We're onboarding farmers, lenders, buyers, processors and carriers in waves through the rest of this year. Pricing for farmers is published on the site; pricing for the rest of the value chain is bespoke and we'd rather talk to you than guess at it.
We're launching first against the regulators we know best — APVMA, NLIS, LPA, MSA, Fair Work, AASB 141, the state EPAs, the Pastoral / Horticulture / Wine awards — because we're Australian, and because Australian agriculture has some of the most demanding compliance environments in the world. If we can ship a platform that's audit-ready for Australian beef and Tasmanian salmon, it'll be audit-ready for nearly anywhere we go after.
The platform underneath is region-agnostic. Multi-region by design. Data is pinned to a home region with cross-region writes blocked by default. When we're ready to launch in another jurisdiction, what changes is the compliance pack we ship with it — not the operating system.
We're not pretending we have all the modules, all the integrations, or all the case studies yet. We don't. What we have is a clear shape of what an operating system for agriculture looks like, the architecture to make it real — one tenant, one ledger, five connected workspaces, designed against the regulators from day one — and an early-access program where the first cohorts get to shape what we build next.
If you're with us
If you've read this far, you're either an operator who's tired of re-keying spreadsheets, a lender who'd rather see what's happening than ask for it once a year, a buyer who wants to verify what you're bidding on, a processor whose settlements would be a lot easier if the producer's books were the same books, or a carrier who'd like to be paid by proof of delivery instead of by invoice — and you've recognised that we're describing something you've wanted for a while.
We want you on the waitlist. Not because the marketing funnel demands it, but because the first cohorts are going to define the shape of every release after them, and we'd rather build with you than for some imaginary “user.”
You'll find us at redearthone.com. You can follow what we're shipping at redearthone.com/updates. You can hit reply to anything we send you.
We think agriculture deserves its operating system, finally. We're going to build it.
— The RedEarthOne team