Products
FuroTrack
Livestock traceability and herd operations: animal identity, movement, health and the national-registry integrations that make an animal's history portable.
01
A peer, not a host
FuroField and FuroTrack sit on the shared platform at the same level. Neither is built inside the other, and neither inherits the other's naming, defaults or release schedule — a distinction that matters most to whichever product is added next, because it is the difference between joining a platform and becoming a guest of an incumbent.
They share the platform and share nothing else: separate deployments, separate databases, separate credentials. A crop customer never sees livestock functionality, and the reverse holds. That separation is enforced in code and tested, not merely intended, which is why the two can be sold to different customers in the same market without either becoming a compromise.
02
What the record actually holds
An animal, and the history that has to travel with it. Identity that survives a change of owner, movements and the permits that authorise them, health and treatment events with the interval each one starts, and the national-registry integrations that make the history portable rather than trapped in one operation's spreadsheet.
The subject of a livestock statement is an animal or a batch, which is why the regulatory work landed here first rather than on the crop side.
03
How far the regulatory work is built
The same rows published on the obligations page, in the product's own context. Two are server-backed today; the rest says what it says.
- A grazing polygon held as geometry, per site, on the serverDone — Stored in the projection the regulation is read in, with area computed from the boundary rather than typed in beside it.
- A due diligence statement that freezes the boundary it was made againstDone — The statement carries a hash binding that boundary to its subject and period, so a later edit cannot be presented as the original.
- Lodging a filing with TRACES, or with the GLOBALG.A.P. databasePartial — The seam exists and a submission is recorded as queued. Without provisioned gateway credentials it stays queued and is never marked accepted on our own say-so.
- Issuing a certificate, or a determination that an audit is metRefused — Certificates come from accredited bodies. A system of record that certifies its own output is worth nothing to the party relying on it.