Satellite IoT has an obvious pitch: coverage anywhere on earth, including the oceans, deserts, and mountains where no cellular tower will ever stand. New low-orbit constellations have dropped the price and the device size to the point where it is a real option, not a last resort.
The problem is that “works anywhere” gets read as “use everywhere,” and that is a costly mistake. For the large majority of deployments, satellite is slower, pricier, and more limited than the LoRaWAN or cellular link you already have. So the useful skill is knowing how it works and recognizing the narrow set of cases where it actually wins.
How satellite IoT works
A device sends a small message to a satellite passing overhead. The satellite relays it to a ground station, which forwards it to the internet and on to your platform. Some systems need the satellite in view at the moment you transmit; others store and forward when a satellite next passes.
The result is a link built for small, infrequent messages from places nothing else reaches. It is not built for streaming or for chatty devices.
LEO versus GEO
Two orbit types shape the trade-offs. Low Earth Orbit satellites fly close, so latency is lower and devices can be smaller and cheaper, but you need many satellites for steady coverage and a given one is only overhead briefly. Geostationary satellites sit fixed over a region, so coverage is constant, but they are far away, which raises latency and power needs.
LEO is where most new IoT capacity is going. It is the reason satellite IoT is suddenly affordable for battery-powered sensors.
The trade-offs that decide it
- Cost. Per-message pricing is higher than cellular or LoRaWAN. It adds up fast if your devices are talkative.
- Latency. Messages can take seconds to minutes depending on satellite passes. Real-time control is off the table.
- Payload. Messages are small. Send a few readings, not images or logs.
- Power and placement. The device often needs a clear view of the sky, which rules out deep indoor or underground use.
Hold a candidate use case against these four. If any one is a dealbreaker, satellite is not your link.
When satellite actually wins
Satellite earns its cost in a specific shape of problem: assets that are remote, mobile, or both, sending small amounts of data where no other network reaches. Think shipping containers crossing oceans, pipelines and tanks in empty country, agricultural equipment far from any tower, and environmental sensors in the wilderness.
It also works well as a backup link for critical sites, quietly carrying data when the primary cellular or LoRaWAN connection drops.
Pairing satellite with a platform
Satellite handles the journey from a remote device to the internet. Your platform handles everything after: storing the readings, showing them, alerting on them, and feeding them to other systems. The two are separate jobs, and the platform should accept satellite-delivered data the same way it accepts anything else, over HTTP or MQTT.
TagoIO ingests data regardless of how it arrives, so a satellite link for your most remote assets can sit alongside cellular and LoRaWAN sites in the same dashboards and alerts. The connectivity can be mixed; the view stays single.
See how mixed-connectivity data looks in one place on the free plan, or book a demo to talk through a remote-asset deployment.
