Soil and crop sensing
Moisture, temperature and nutrient readings tied to a field and a depth.
Agriculture
Agriculture software that records what was done to which field
Sensors, field records and the platform underneath them. We have built a self-hosted IoT platform a client owns outright, and written up how soil data becomes a decision.
3Years pesticide use records must be kept
100%Of the IoT platform owned by the client
3Deployment modes: on-premise, private cloud, hybrid
40+Developers on staff
What this is
A reading means nothing without its field
Soil moisture, temperature and nutrient sensors produce a number every few minutes. Which field, which depth and what was applied afterwards turn it into a decision, and those are the parts that usually go missing.
Coverage is the constraint
Fields are where the signal is worst. Gateways and queued uploads matter more than the dashboard.
Records are an obligation
Professional users keep a record of every plant protection product used. Sensor data should feed that record and save a second entry.
Services
What we build for growers and agtech teams
Field and application records
Product, time, dose, area and crop captured once, at the moment of application.
Irrigation and weather telemetry
Readings from the field joined to the weather around them.
Self-hosted IoT platforms
Multi-tenant, white-labelled and deployed where you decide.
Offline field apps
Written to the device first and synced when the tractor reaches coverage.
Dashboards and alerts
What is dry, what is late and what needs a person, without a daily login.
Records
What a pesticide record has to hold
Retained EU rules still set the baseline, so check the position for your own farms.
Three-year retentionUnder Article 67 of Regulation (EC) 1107/2009, professional users keep a record of each plant protection product used for at least three years.
What the record holdsProduct name, time and dose of application, and the area and crop treated.
Access on requestThe record has to be made available to the competent authority, and third parties such as the drinking water industry or retailers can request access through it.
Electronic formatNorthern Ireland guidance says the transfer of usage records to electronic format can be deferred to 1 January 2027. Check England and Wales separately.
Case study
A platform the client owns outright
Industrial IoT
IoT Core Engine
The client wanted off third-party IoT SaaS without losing the enterprise features their own customers expected. We built a self-hosted, white-labelled platform on an open-source base, with role-based access, single sign-on and reporting built in, features SaaS vendors usually keep for the top tier.
Self-hostedOn-premise, private cloud or hybrid
Who we build for
The teams who call us
Arable and mixed farms
Where the spray record and the sensor reading should be the same entry.
Growers and cooperatives
Many fields, many members and one reporting obligation.
Agronomy and advisory firms
Teams collecting data across clients and needing it in one place.
Agtech product teams
Companies that need the platform under their own brand.
Related reading: IoT sensors for soil monitoring, IoT development and the IoT platform case study.
FAQs
What buyers ask first
Can you work with our existing sensors?
Usually yes, over a gateway or the maker API. Send the model numbers and we will say which ones we can read.
Do we have to host it ourselves?
No, but you can. The platform we built runs on-premise, in a private cloud or hybrid, and the client owns the whole stack.
Can sensor data feed our pesticide records?
It can, and it should. The record needs product, time, dose, area and crop, so the application event is the entry point.
Who owns the code and the cloud accounts?
You do, from the first commit. Repositories and cloud accounts stay in your name.
Send us one field
Thirty minutes with the engineers on what you sense, what you record and where the two should meet.