Integrations
Terra reads the estate you already own.
Interoperability is the product decision this platform is built on. Devices are connected over the protocols they already speak, records already kept are imported, and nothing has to be replaced for the first insight to arrive.
Compatibility, stated plainly
Terra is designed to integrate with compatible hardware, protocols and data sources. Compatibility is not universal and is not assumed: which of your devices can be connected, and what each of them can contribute, is established during the farm assessment before anything is committed.
No platform is compatible with every device ever sold into agriculture, and any page claiming otherwise is describing an intention rather than a capability. What follows is the shape of what Terra connects to, by category.
Sources 01
Cameras & imaging
Any imagery Terra can reach can be analysed. Framing, resolution and capture frequency set what is detectable, not the badge on the housing.
- IP cameras
- Fixed cameras already installed over blocks, greenhouses, packhouses and access points.
- RTSP streams
- Continuous streams sampled on a schedule, so a stream becomes a series of comparable observations.
- ONVIF-compatible devices
- Discovery and stream access through a standard interface rather than a vendor-specific one.
- Agricultural imaging systems
- Purpose-built crop imaging hardware, where it exposes imagery through a supported interface.
- Drone imagery
- Flight imagery imported per survey and aligned to the zones it covers.
- Handheld and scouting capture
- Images captured during scouting, attached to the zone they were taken in.
Sources 02
Sensors & instrumentation
Terra reads instrumentation a farm already owns. Which measurements exist is a property of that instrumentation, and the platform never reports a channel it was not given.
- Soil probes
- Moisture, temperature and, where fitted, EC and pH at the depths the probe reports.
- Environmental sensors
- Air temperature, humidity, light and other above-ground conditions per zone.
- Weather stations
- On-site stations, preferred over remote data wherever they are available.
- Rain gauges
- Rainfall logged against the zone, so a moisture response can be attributed to it.
- IoT field devices
- Battery-powered field nodes reporting through a gateway on their own schedule.
- Pest monitoring hardware
- Third-party monitoring traps and counters that expose imagery or counts. Terra supplies no traps.
Sources 03
Connectivity & protocols
The transport matters less than the fact that it is open. If a device can publish or be polled through one of these, it can usually be connected.
- MQTT
- Subscription to farm brokers, which is how most gateway estates already move telemetry.
- HTTP / REST
- Polling of device and platform endpoints on a defined interval.
- Webhooks
- Push delivery for systems that would rather report an event than be asked.
- Compatible IoT gateways
- Existing gateway hardware acting as the bridge between field devices and Terra.
- LoRaWAN-compatible infrastructure
- Long-range field networks, ingested through their network server rather than device by device.
- On-site collectors
- A local collector for sites with limited connectivity, forwarding when a link is available.
Sources 04
Data & farm systems
Records the farm already keeps are part of the picture. History is what allows a reading to be judged against the same ground rather than a general expectation.
- Third-party agricultural APIs
- Weather, satellite and agronomic services already in use on the farm.
- Farm management systems
- Zone definitions, crop records and operational history from an existing FMS.
- CSV and spreadsheet imports
- Historical measurements and records, including years kept outside any system.
- Irrigation records
- Applied water by zone and date, which is what makes a moisture curve interpretable.
- Scouting observations
- Field notes and manual counts, held in the same record as automated detections.
- Laboratory results
- Soil and tissue analyses imported against the zone and date they were sampled from.
Where a source ends up
From a device on a pole to a ranked risk.
Connecting a source is the beginning of the path, not the end of it. This is what happens to a reading after it arrives.
Yours
Existing farm hardware
Whatever is already in the field. Terra begins here rather than with a purchase order.
- Cameras
- Sensors
- Weather stations
- Drones
- Gateways
- Farm APIs
Ingestion
Terra Connect
Devices, streams and data sources are connected over the protocols they already speak, with credentials and access scoped per source.
- MQTT
- RTSP / ONVIF
- REST & webhooks
- Imports
Ingestion
Data normalisation
Units, sampling intervals, timestamps and identities are reconciled, and every reading is bound to the zone and crop it belongs to.
- Unit alignment
- Time alignment
- Zone binding
- Quality flags
Reasoning
Terra Intelligence
Computer vision, sensor fusion, analytics and prediction run over the combined record rather than over one feed at a time.
- Computer vision
- Sensor fusion
- Analytics
- Prediction
Model
Farm digital twin
The farm as a structured, continuously updated model: fields, zones, crops, instruments, conditions, history and open risk.
- Fields & zones
- Crops
- Instruments
- State & history
Output
Risks, insights, recommendations
Ranked and explained. Every output names the signals behind it, states its confidence, and says what it recommends confirming.
- Risk scores
- Anomalies
- Predictions
- Priorities
Before anything is committed
Compatibility is established, not assumed.
The farm assessment goes through the estate device by device. It is the only honest way to answer whether a particular camera or probe can be connected, and it is free of any obligation to proceed.
What the assessment establishes
- Which of your cameras expose a stream Terra can sample, and at what framing and resolution.
- Which sensors report through a gateway or API, and which are read manually today.
- What each installed instrument actually measures, and at what depth and interval.
- Whether the site's connectivity supports continuous ingestion or needs a local collector.
- Which records already exist: irrigation logs, scouting notes, laboratory results, past seasons.
- What would have to change for a capability the farm wants but the current estate cannot support.
Next step
Request a Farm Assessment
Every agricultural operation has a different data footprint. Terra deployments are scoped according to the farm, existing hardware and required intelligence capabilities.
The assessment establishes what your existing hardware can support before anything is committed.