Farm records kept at the source
Every rule ends up as a line in a farmer's field book. Koru is where that line is written: the farmer records the work, Koru checks each treatment against Spain's MAPA product register and warns about problems, and the field book comes out as a PDF. We have not built tools for regulators — this page says what exists today.
Records tied to official parcels.
In Spain the farmer picks a parcel from SIGPAC or uploads the PAC declaration as a PDF, and Koru reads the parcels with their SIGPAC code, area and crop — in minutes. In Slovakia parcels are looked up in the cadastre. Koru reads these sources; it sends nothing back to them.
- SIGPAC lookup and PAC PDF import for Spanish farms
- Cadastre lookup for Slovak farms (early access)
- Compliant with EU GDPR and national data-protection rules
The Cuaderno de Explotación, checked and exported as a PDF.
On Spanish farms Koru checks the field book against a set of rules — applicator without a card, product not authorised for the crop, dose above the maximum, pre-harvest interval — and lists what to fix. The checks warn; they do not block saving. The farmer exports the CUE as a PDF. Nothing is submitted to SIEX or to any portal. Programme delivery, deadline reminders and evidence submission are not built — talk to us.
- Rule checks with a list of issues to fix
- CUE exported as a PDF, farm by farm
- CUE logbook switched on per farm, on request
Built, and not built.
What a public body or advisory service can use today, and what Koru does not do. The interface is in Spanish, English and Slovak.
Hub for a group of farms
An organisation that runs several farms sees them in one list, with counters, an activity feed, members, equipment and licences.
Programmes: not built
No programme requirements, deadlines or evidence submission in the app, and no regional dashboards. Talk to us.
GDPR by default
Stored in the EU. AI providers receive only what each answer needs. Audit logs for every access.
Reports per farm
Parcel, worker and product-usage reports on each farm, exported as CSV or PDF.
Field book export
Each Spanish farm exports its own Cuaderno de Explotación as a PDF. Nothing is submitted to SIEX.
SIGPAC and cadastre
Parcels are picked from SIGPAC in Spain and looked up in the cadastre in Slovakia.
Read-only access
A farm can invite a person with a read-only role, who then sees that farm's records. There is no inspector tool.
Registers: read only
Koru reads Spain's MAPA product register, synced weekly, and SIGPAC. It does not submit to MAPA, REGA, ROPO or any registry.
What each can do today.
Local authority
A local authority or its advisory service can work with farms that use Koru: the farm invites your adviser with a read-only role, and the adviser sees that farm's records. Delivering local programmes through the app — water restrictions, subsidy schemes — is not built.
Regional government
A regional body or advisory service that manages a group of farms can keep them in one hub: a list of farms with counters, an activity feed, members, equipment and licences. There is no region-wide view of other people's farms and no scheme tracking.
National ministry
Koru sends nothing to national registries: it reads Spain's MAPA product register and SIGPAC, and Spanish farms export their Cuaderno de Explotación as a PDF. If a ministry needs data flows or programme tooling, that is a project to scope with us, not a feature we have.
Public-sector work — let's scope it together.
Today Koru serves farms: in Spain with CUE checks and the MAPA register, in Slovakia in early access with the Slovak interface and cadastre lookup. Anything at programme or regional level is not built and would be scoped with you from scratch. We work under the EU's GDPR framework and national data-protection rules.
Start from what exists.
Book a demo and we'll show you the field book, the PDF export and the hub in the product — and tell you plainly what would have to be built for your case.
