Why build a sovereign agricultural IoT satellite constellation rather than simply contracting Spire, Kepler or Orbcomm?

Commercial providers offer coverage today but on their terms: pricing, data retention policies, and service continuity can change at will, and your national agricultural telemetry flows through foreign infrastructure subject to their governments' laws. A sovereign constellation locks in coverage obligations, keeps farm data within national jurisdiction, and gives the state a platform it can task for emergency response or food-security monitoring without renegotiating a contract. The incremental cost of ownership is typically recovered within a decade through avoided subscription fees and the downstream economic value of precision-agriculture yield gains.

What is the minimum constellation size for useful national agricultural IoT coverage?

For a mid-sized agricultural nation (roughly 50–200 million hectares of farmland), a constellation of 18 to 36 nanosatellites in polar or sun-synchronous LEO can achieve a revisit interval of under two hours for store-and-forward messaging across the entire territory. Real-time or sub-15-minute latency demands 80-plus satellites. Spire operates approximately 110 satellites to serve global customers; a national-only system can be a fraction of that size because it covers one territory, not the whole Earth.

Which frequency bands are best suited to satellite agricultural IoT, and how difficult is spectrum access?

L-band (1–2 GHz) offers the best balance of link budget, device antenna size, and weather penetration for agricultural IoT, and is the basis of established services like Iridium SBD. VHF/UHF bands (the basis of Lacuna Space and similar systems) enable smaller, cheaper end-nodes but suffer more interference. ITU-R coordinates international frequency use; a new sovereign system must file for coordination under the ITU Radio Regulations, a process that can take two to five years and requires demonstrating non-interference with incumbents.

Can existing LoRaWAN or NB-IoT ground sensors be reused with a satellite backhaul?

Yes, with gateways. LoRaWAN sensors already deployed on farms can feed data to a satellite-enabled gateway that aggregates and upllinks packets — this is exactly the architecture used by Lacuna Space and Actility partnerships. NB-IoT sensors are less compatible because they require two-way cellular sessions, but next-generation direct-to-satellite NB-IoT (3GPP Release 17 NTN specifications) is changing that. A sovereign programme should specify gateway hardware that supports both legacy LoRaWAN aggregation and future direct-to-satellite NTN operation.

How does satellite IoT compare with drones or aircraft for farm monitoring?

Drones and crewed aircraft provide very high spatial resolution but are event-driven, weather-constrained, and expensive at scale. Satellite IoT does the opposite: it provides continuous, low-bandwidth telemetry (soil moisture, temperature, valve states, livestock GPS) from thousands of cheap ground sensors simultaneously, across an entire nation, in any weather. The two are complementary: satellite IoT handles persistent sensor telemetry, while satellite imagery (from Planet, ICEYE, or sovereign EO assets) handles periodic crop-condition mapping.

What ground infrastructure does a sovereign agricultural IoT constellation require?

At minimum: two to four national ground stations for telemetry, tracking and command (TT&C); a national mission-control centre; a data-processing and API platform to ingest sensor messages and deliver them to farm-management software; and a network of satellite-enabled field gateways deployed across agricultural zones. The gateway network is the most capital-intensive ground component and should be co-funded with the national agriculture ministry, which already has extension-service infrastructure in rural areas.

How should a national programme handle the transition from a commercial IoT satellite provider to a sovereign system?

Plan for a three- to five-year parallel-operation period. Continue purchasing commercial data during constellation development and launch; use that period to build the ground segment, certify the data platform, and migrate sensor firmware to support the sovereign air interface. Contractual break-clauses with commercial providers should be negotiated before the parallel period begins. Nations that have attempted hard cut-overs without a transition phase — in both space and terrestrial telecom contexts — have consistently suffered service gaps that erode farmer and ministry trust in the new system.

Can a sovereign agricultural IoT constellation serve non-agricultural applications to improve its economics?

Absolutely — and it should. The same nanosatellite constellation that collects soil and livestock telemetry can carry pipeline sensor data, environmental monitoring nodes, and remote weather-station readings on the same link layer. This multi-sector demand aggregation is critical to justifying constellation scale and reducing per-message costs. Nations should design the constellation from the outset as a national IoT backbone rather than a single-sector asset, with the agriculture ministry as anchor tenant rather than sole customer.

1.5.2Live

Smart Agriculture IoT

Farmer crouching in a crop field checking a handheld device connected to a soil sensor stake — An Indian farmer examining cotton crops gains new precision through satellite IoT systems delivering real-time field intelligence.

Satellite IoT Loop for Smart Farm Decisions

1
IoT Constellation
Low-orbit satellites receive soil sensor uplinks
2
Ground Station
Telemetry decoded and forwarded to cloud
3
Agronomic Analytics
AI models flag drought stress or over-irrigation
4
Farmer Alert
SMS or app triggers precise irrigation action

Soil and crop sensors relay data via satellite constellation to cloud analytics, delivering actionable irrigation alerts to farmers.

Page in the build queue

This application has its place in the atlas. The full page — short and long descriptions, what-matters bullets, sovereignty rationale, and the eight-field architecture block — is being written next.

Maturity reading: Operational systems exist with paying customers. Phase 1 built §4.1 (Maritime Intelligence) end-to-end as the depth-and-format reference. Section 4 is the next section to graduate from scaffold to full content; the rest follow on the roadmap.

Related applications

1.5.1 · Previous

Industrial IoT Connectivity

All in space-based iot networks

1.5.3 · Next

Pipeline Sensor Networks

Bring this into your sovereign programme.

All solutions Speak with engineering