What Is Satellite IoT? A Field Guide for 2026

Terrestrial cellular networks cover roughly 20% of Earth’s surface. If your assets move through the other 80% (ocean transit, remote pipelines, cross-border freight routes), every gap in visibility is a gap in operational control. That is the problem satellite IoT exists to solve.

Satellite IoT is the use of satellite communications to connect sensors, trackers, and industrial devices to remote monitoring and management systems. It’s not satellite internet. It’s not broadband. It’s small, low-power data transmissions (GPS coordinates, temperature readings, tank levels, equipment status) relayed through orbiting satellites instead of cell towers. The output is an operational decision that would otherwise be made blind.

The market crossed 7 million subscribers in 2025 and is projected to reach 42 million by 2030. But subscriber counts don’t tell you whether satellite connectivity is right for your assets. This guide does. And it’s written from the deployer’s side of the table, not from a constellation operator selling its own network. Satellite IoT deployments increasingly support Industry 4.0 initiatives by extending connectivity to previously unreachable industrial assets.

How Satellite IoT Works

Every satellite IoT deployment solves the same core problem: get operational data from a remote asset to a system where someone can act on it. The difference is in the data path between the device and the satellite.

A 2026 tutorial review published in Frontiers in Communications and Networks maps these three patterns in detail, including the intermittent-access challenges that most vendor brochures skip.

One naming issue trips people up. A product described as “LoRaWAN over satellite” might mean sensors communicating directly with a satellite, or it might mean a standard LoRaWAN gateway connected to a VSAT terminal on the ground. The GSMA’s hybrid cellular/NTN guide describes both arrangements under the same umbrella. The label alone doesn’t reveal the architecture. Ask which one you’re buying.

Beyond the data path, a working satellite IoT device requires more than a modem. Antenna gain, polarization, and placement determine the link budget (whether a usable signal actually reaches the receiver). Power supply, GNSS-based timing, firmware behavior, and secure credential provisioning all need to be right. A technically capable modem paired with a poorly positioned antenna produces nothing.

Orbits and What They Mean for Your Deployment

Three orbital altitudes dominate the satellite IoT conversation. Each involves engineering trade-offs, not competitive rankings.

Here’s the counterintuitive part. Lower orbit does not automatically mean faster data delivery. A sparse LEO constellation using store-and-forward can deliver your sensor reading hours after the event. A continuously available GEO service might deliver it in seconds. Viasat, for example, advertises IoT Nano latency typically under 15 seconds for small event messages, and that’s a GEO-powered service.

The orbit type matters less than whether the service provides continuous or intermittent access for your use case. A tank-level reading arriving every four hours works fine for chemical dosing. A stolen-vehicle alert arriving four hours late is worthless. Match the delivery timeline to the operational decision, not to the orbit brochure.

Three Radio Ecosystems Worth Knowing

Satellite IoT isn’t one technology. It’s at least three distinct radio ecosystems, each with different device requirements, coverage models, and integration paths.

Proprietary satellite messaging is the oldest and most proven. Iridium’s Short Burst Data (SBD) runs on a meshed 66-satellite LEO constellation with pole-to-pole coverage. Viasat’s IoT Nano offers two-way, non-IP L-band messaging powered by ORBCOMM’s OGx platform. These systems work and have worked for years. The trade-off: you’re locked into specific hardware and a specific network operator.

3GPP IoT-NTN is the standards-based path. Release 17 (finalized in 2022) introduced satellite support for NB-IoT and LTE-M, the same low-power protocols used in billions of terrestrial IoT devices. The promise: use familiar cellular hardware and SIM-based connectivity, but over satellite. The reality in 2026: compatibility depends on which 3GPP release your device supports, the certified hardware list of each operator, and whether automatic terrestrial-to-satellite switching has been implemented at the firmware level. Promise and deployment are still converging.

LoRa-based satellite connectivity offers a third low-power option. EchoStar’s EM2050 module supports LoRa and LoRa-FHSS across licensed satellite S-band and terrestrial sub-GHz bands. The target: ultra-low-power, massive sensor deployments sending tiny packets, the same use cases LoRaWAN serves on the ground, extended to places where ground infrastructure doesn’t exist.

These are not interchangeable options. Proprietary messaging gives you proven reliability now. 3GPP NTN gives you standards-based integration with the cellular ecosystem. LoRa-based satellite gives you density and ultra-low power. Choose based on what your asset needs to communicate, how often, and how much integration friction your engineering team can absorb.

Where Satellite IoT Delivers Measurable ROI

The business case for satellite IoT is never about bandwidth. It’s about the cost of not knowing.

Latin American oilfields. EDGE embedded Myriota satellite modules into Xpert controllers across operations in Argentina, Colombia, Brazil, and Bolivia. Cellular coverage was virtually nonexistent. Without connectivity, inaccurate chemical dosing caused blockages, corrosion, and unplanned shutdowns. After deployment, EDGE reported halving unplanned downtime, accelerating well surveys by 60%, and reducing maintenance costs by up to 12%. Small telemetry messages. Big operational dollars recovered.

Australian farms. Farmbot partnered with Pivotel to monitor water quality, level, pressure, flow, and rainfall on remote properties via Globalstar satellite connectivity. The published case study reports over 1,300 monitors deployed and savings of up to 200 hours per farmer annually in water-asset checks. The value isn’t complex analytics. It’s not driving two hours to check a tank that turns out to be full.

Indonesian fisheries. ORBCOMM and PT SOG Indonesia deployed satellite vessel monitoring systems on commercial fishing boats, transmitting position, speed, and heading hourly to enable fisheries oversight and regulatory compliance from shore. Different value proposition: not predictive maintenance, but legal visibility into assets operating entirely beyond coastal cell coverage.

The pattern across these cases: a modest, low-bandwidth satellite link changes expensive operational decisions. You don’t need streaming video from a wellhead. You need a temperature reading, a GPS fix, a tank level, or a “still here” confirmation. That is what satellite IoT delivers, and that is where the ROI lives.

Market Reality: 7 Million Subscribers, 17 Commercial Operators

The market numbers look impressive until you read the fine print.

Berg Insight’s October 2026 report counts more than 7 million satellite IoT subscribers globally in 2025, projecting 42 million by 2030 at a 43.1% CAGR. Separately, Juniper Research estimated $2.9 billion in revenue for 2024 and forecasts $9.3 billion by 2030. These are different metrics from different firms. Subscriber growth and revenue growth don’t track the same curve.

The number that should shape your vendor evaluation: Berg Insight assessed 44 satellite IoT operators but found only 17 offering commercial service. The other 27 sit at various stages of constellation development, technical demonstration, or pre-commercial testing. The competitive pipeline far exceeds the operational supply base.

Among incumbents, Iridium leads with 2.1 million subscribers. Globalstar follows at 540,000. New entrants like Kinéis (commercial services launched June 2025 on a 25-satellite constellation) and Sateliot (11 cumulative satellite launches as of October 2026) are building capacity but remain earlier in their commercial maturity. These numbers are directionally useful for procurement; they are not a recommendation to wait.

When a provider says “global coverage,” ask whether that means operational commercial service in your geography today, or planned coverage pending additional launches and regulatory approvals. Those are fundamentally different answers.

What the Satellite IoT Brochures Leave Out

Most published guides on this topic are written by companies selling satellite connectivity. That creates predictable blind spots. Here are the ones I encounter most in the field.

Real cost is hard to benchmark, but not invisible. Deutsche Telekom published one of the few transparent satellite IoT tariffs: EUR 211.50 per month for a VSAT-backed IoT connection (including 1 GB satellite data, 5 GB cellular, equipment, installation, and service), with a separate narrowband offer at EUR 0.90 per kilobyte. These are published prices for specific products, not universal benchmarks, but they establish the order of magnitude. Budget for device, antenna, installation, airtime, integration, power, and maintenance together. Comparing isolated “per message” rates between providers tells you almost nothing.

Latency depends on architecture, not just orbit. Store-and-forward systems (common in sparse LEO constellations) hold your data until the satellite passes within range of a ground station. That delay can be minutes or hours. A continuously available GEO service can deliver the same message in under 15 seconds. If your application needs near-real-time alerts (geo-fence violations, theft detection, safety alarms), confirm the actual delivery timeline of the service you’re buying. Theoretical orbital latency and practical message delivery time are different things.

“Global coverage” does not mean it works everywhere. emnify’s satellite IoT documentation explicitly states that its service requires line of sight to the sky and is unavailable indoors. Skylo notes coverage is not complete or uniform worldwide. National licensing, physical obstructions, antenna orientation, and device certification are all separate from the network footprint on a coverage map. A satellite that covers a region doesn’t mean your device, in your enclosure, at your site, will connect.

Constellations can fail. In October 2021, Hiber abandoned plans to build a 24-satellite IoT network after technical problems with its early satellites made repairs cost-prohibitive. Two were decommissioned; two others couldn’t support commercial service. Separately, the FCC imposed a $900,000 settlement on Swarm for unauthorized satellite launches and ground-station operations. Technical ambition doesn’t guarantee network continuity or regulatory compliance. When evaluating a provider, look at the replenishment plan, financial backing, and licensing status alongside the constellation size.

More satellites mean more debris risk. ESA’s 2026 Space Environment Report recorded over 4,000 new payloads launched in 2025 alone, warning about growing collision risk from insufficient end-of-life removal. This is a sector-wide concern, not specific to IoT constellations, but it affects the long-term sustainability of the LEO environment where most new IoT satellites operate.

A satellite link is not end-to-end security. Data traveling through space is not inherently secure. Device-to-cloud authentication, credential provisioning, and application-layer encryption remain your responsibility. The GSMA’s IoT SAFE framework uses the SIM or secure element as a root of trust and supports mutual TLS/DTLS authentication. It’s a starting point for the security architecture, not an optional extra.

How to Decide If Your Assets Need Satellite Connectivity

The simplest decision filter I’ve found after 15 years deploying IoT in industrial environments: does the value of recovering visibility into a remote asset exceed the full cost of connecting and maintaining it?

If your containers, ground support equipment, or field instruments spend meaningful time in cellular dead zones, and the cost of that blindness (lost assets, missed maintenance windows, compliance gaps, delayed decisions) is real and quantifiable, satellite IoT belongs in your architecture.

If those same assets operate primarily within cellular coverage with occasional gaps, hybrid terrestrial-satellite connectivity is the practical answer. In February 2026, Deutsche Telekom demonstrated a commercial NB-IoT device roaming across terrestrial, GEO, and LEO satellite networks without manual intervention. That’s the direction this market is heading: connectivity that follows the asset across coverage boundaries automatically.

Before choosing a module or signing a connectivity contract, specify these parameters first:

• Payload size and frequency: How many bytes, how often? A daily GPS ping is a different problem than hourly multi-sensor telemetry.
• Delivery deadline: Does the data need to arrive in seconds, minutes, or hours? This determines whether store-and-forward is acceptable.
• Power budget: Battery-only, solar, or vehicle-powered? This constrains which satellite modems are feasible.
• Physical environment: Indoor, outdoor, enclosed in metal, mounted on a moving vehicle? Line of sight to the sky is non-negotiable for satellite links.
• Coverage map: Where exactly does the asset travel? “Global” from the provider may not include your specific geographies or regulatory jurisdictions.
• Switching behavior: If hybrid, does the firmware handle terrestrial-to-satellite handoff automatically, or does it need manual configuration?

The satellite IoT market is real, growing, and increasingly standardized. It is also a market where the gap between a vendor’s coverage map and your device’s actual connectivity can be wide. Test in the field. Validate delivery timelines under real conditions. And choose providers who show documented operational outcomes, not just constellation diagrams.

At Datanet, we build asset tracking solutions that work across connectivity types because the asset doesn’t care which network it’s on. It just needs to report. If you’re evaluating how satellite IoT fits into your fleet, aviation, or industrial tracking architecture, reach out to our team. We’ll help you figure out what the right connectivity path looks like for your actual deployment, not a theoretical one.

Frequently Asked Questions

Is satellite IoT the same as satellite internet?

No. Satellite IoT connects devices and sensors for small operational data transmissions: GPS fixes, temperature, status alerts. Satellite internet provides broadband access for users. A satellite internet terminal can serve as backhaul for an IoT gateway, but they are different services solving different problems at different price points.

Does satellite IoT replace cellular connectivity?

Rarely. It complements it. Cellular networks are more cost-effective wherever they exist. Satellite fills the gaps: remote sites, ocean transit, cross-border freight routes, and areas where terrestrial infrastructure is absent or unreliable. Hybrid architectures that switch automatically between both are rapidly becoming the default approach.

Can existing NB-IoT devices connect to satellites without modification?

Only if they support the correct 3GPP release and have been certified for the specific satellite service. Telenor and Sateliot condition their compatibility claims on device-level support for Release 17 IoT-NTN features. A standard cellular NB-IoT SIM alone does not make a device satellite-ready.

Is satellite IoT communication real-time?

It depends entirely on the service. Continuously available GEO services like Viasat IoT Nano claim latency under 15 seconds for small messages. Sparse LEO constellations using store-and-forward may deliver data minutes or hours after capture. Always confirm the actual message delivery timeline, not just the theoretical latency of the radio link.

How much does satellite IoT cost?

There is no single answer. Deutsche Telekom’s published 2024 tariff charged EUR 211.50/month for a VSAT-backed IoT connection and EUR 0.90/KB for narrowband satellite data. Your actual cost depends on device hardware, antenna, installation, airtime plan, integration effort, and ongoing maintenance. Compare total lifecycle cost, not isolated per-message rates.

Does “global coverage” mean satellite IoT works indoors?

No. Satellite IoT requires line of sight to the sky. Most documented services explicitly exclude indoor operation. “Global coverage” from a provider may also exclude specific countries (due to spectrum licensing) or specific locations (due to obstructions). Validate connectivity at your actual deployment sites before committing to a contract.