Lacuna Space vs Plan-S vs EchoStar: Comparing Satellite LoRa Operators

Comparing satellite LoRa operators for low-power IoT connectivity beyond cellular coverage

Your LoRaWAN pilot works beautifully on the test bench. Then you ship 2,000 trackers to a customer whose containers cross the Sahara, the South China Sea, and three Australian mining sites with no terrestrial gateways for 400 km in any direction. The cellular quote came back at $14/device/year with patchy roaming. Someone in the room mentions satellite LoRa.

Three names come up: Lacuna Space, Plan-S, and EchoStar Mobile. Their websites all promise global IoT coverage, but their architectures are wildly different. Pick the wrong vendor and you’ll quietly ship a fleet with the wrong battery life and the wrong message cadence, and your firmware team will end up rewriting the MAC layer.

This is a vendor-neutral look at the three satellite LoRa operators as of April 2026, what they’re actually good at, and where they break down. We’ll also be honest at the end about why satellite LoRa might be the wrong answer entirely.

Why Satellite LoRa Is Suddenly on the Table

Three forces converged.

First, the 2G/3G sunsets kept coming. AT&T finished in 2022, T-Mobile in 2024, and the European operators are clearing 3G through 2025 and 2026. NB-IoT roaming is technically possible and operationally miserable: SIM swaps, carrier-by-carrier negotiations, and coverage maps that disagree with reality.

Second, cellular IoT in remote regions is just expensive. A mining site in Western Australia or a wind farm off Scotland pays roaming premiums that make a $3 LoRa node feel ridiculous against a $40/year connectivity bill.

Third, Semtech’s LR-FHSS modulation closed the gap. A 1 W transmitter on the ground can now reach a satellite 550 km up. The same SX1262 chip in your existing tracker can reach orbit with a firmware change.

The broader satellite IoT category includes Astrocast, Swarm (acquired by SpaceX), Iridium, Myriota, and a dozen others. We’re focused on the three that speak LoRa, because if you’ve already deployed LoRaWAN, the migration cost is the lowest.

The Three Operators at a Glance 

+------------------+------------------+------------------+------------------+
| Criteria         | Lacuna Space     | Plan-S Connecta  | EchoStar Mobile  |
+------------------+------------------+------------------+------------------+
| Orbit            | LEO (~550 km)    | LEO (~500 km)    | GEO (~36,000 km) |
| Constellation    | ~8 operational   | ~12 operational  | EchoStar XXI     |
| Spectrum         | Unlicensed ISM   | Unlicensed ISM   | Licensed S-band  |
| Protocol         | LoRaWAN-compat   | LoRaWAN-compat   | LoRa-based,      |
|                  |                  |                  | proprietary stk  |
| Coverage Model   | Intermittent     | Intermittent     | Continuous       |
|                  | (4-8 passes/day) | (6-10 passes/day)| (regional GEO)  |
| Latency          | Minutes to hours | Minutes to hours | Near real-time   |
| Device Power     | Very low         | Very low         | Higher (GEO link)|
| Footprint        | Global           | EMEA/APAC focus  | EU + select rgns |
+------------------+------------------+------------------+------------------+

Numbers above reflect publicly disclosed status as of early 2026. Plan-S has been the most aggressive launcher, EchoStar’s footprint hasn’t changed (it’s a single GEO bird), and Lacuna’s growth has been steady but slower than originally promised in 2021.

Lacuna Space: The Standards-Based Pioneer

Lacuna spun out of the UK Satellite Applications Catapult in 2017 and made an early bet that being a card-carrying LoRa Alliance member mattered. It does. Their service hooks directly into The Things Network, ChirpStack, and Actility, which means your existing application server doesn’t care whether a packet came from a rooftop gateway in Munich or a satellite over the Pacific.

Strengths: Standards alignment, developer ergonomics, genuine global coverage (their satellites are polar-orbit). Integration is the closest thing to “flip a switch” in this category. They publish honest pass-prediction tools.

Weaknesses: The constellation is still small. If you need more than a handful of uplinks per day per device in mid-latitudes, you’ll feel it. Pricing has crept up since 2023 as they shifted from research-friendly to commercially serious.

Best fit: Existing LoRaWAN deployments needing satellite backfill, especially environmental monitoring, livestock, and intermodal cargo where one position fix every few hours is plenty.

Plan-S Connecta: The Fast Follower

Plan-S is Turkish, vertically integrated (they build and operate their own satellites), and has launched faster than most analysts predicted. Connecta is their IoT service. They’re the price aggressor in EMEA and increasingly APAC, with a constellation that’s now denser than Lacuna’s over Turkey, the Gulf, India, and Southeast Asia.

Strengths: Aggressive launch cadence, competitive per-device pricing, owning the full stack means they can iterate quickly.

Weaknesses: Smaller integration ecosystem. Fewer public case studies. North American coverage is real but lower priority commercially. Documentation in English has improved a lot but still trails Lacuna’s.

Best fit: Greenfield deployments in EMEA or APAC, cost-sensitive projects at scale, and customers who value a single vendor relationship over standards purity.

EchoStar Mobile: The GEO Outlier

EchoStar Mobile is the odd one out, and that’s the point. The service runs on EchoStar XXI in geostationary orbit at ~36,000 km, offering continuous coverage over Europe and select adjacent regions in licensed S-band spectrum, using a LoRa-based proprietary stack rather than vanilla LoRaWAN. That architecture buys you something the LEO operators can’t: if you need to send a command to a device and get an ack within seconds, this is the only LoRa-flavored option that delivers it. Licensed spectrum means interference protection (no ISM band drama), and EchoStar is a 40-year-old satellite operator, not a startup.

The trade-offs are direct. GEO link budget means more transmit power, more current draw, and either bigger batteries or shorter device lifetimes. Your firmware team will need to integrate EchoStar’s stack rather than reusing a standard LoRaWAN one. The footprint is regional, not global. The fit is applications in covered regions needing low-latency downlink confirmations: utility grid sensors, regulated asset tracking, anything where licensed spectrum is a procurement requirement.

LEO vs GEO LoRa Satellite: The Geometry That Matters 

        GEO (EchoStar) ~36,000 km
              ★
              |
              |  continuous view of ~1/3 of Earth
              |
   ~~~~~~~~~~~|~~~~~~~~~~~~~~~~~~ Earth
       \      |      /
        \     |     /
         ★ ★ ★ ★ ★    LEO (Lacuna, Plan-S) ~500-550 km
         passes overhead intermittently

GEO trades latency for power. LEO trades power for latency. If your device runs on a coin cell and reports once a day, LEO wins. If your device is on a utility pole with grid power and needs sub-minute response, GEO wins. Most IoT applications fall on the LEO side, which is why the LEO operators have more customers.

Decision Framework: Lacuna vs Plan-S vs EchoStar 

Pick Lacuna if      -> You have existing LoRaWAN gear,
                       need global coverage, dev simplicity matters,
                       and 4-8 passes/day is enough
Pick Plan-S if      -> You're deploying in EMEA/APAC,
                       price-sensitive at volume, greenfield project,
                       OK with younger ecosystem
Pick EchoStar if    -> You need continuous regional coverage,
                       licensed spectrum compliance, low-latency
                       downlink, and have power budget for GEO
Pick none if        -> You need >10 msg/min per device, kilobyte
                       payloads, true global SLA, or your devices
                       are already battery-constrained on terrestrial LoRa

The three variables that determine the answer are latency tolerance, message cadence, and geographic footprint. Everything else (price, ecosystem, spectrum) is secondary.

Where Cellular Still Wins

Cellular IoT still beats satellite LoRa on:

  • Throughput. NB-IoT does ~60 kbps, satellite LoRa does dozens of bytes per pass.
  • Latency SLAs. A cellular network commits to milliseconds. Satellite LoRa commits to “next pass.”
  • Mature roaming. Painful, but it exists and works in 180+ countries.
  • Downlink reliability. Sending firmware updates over satellite LoRa is technically possible and operationally awful.

Satellite LoRa complements cellular for the 5-15% of your fleet that drifts outside coverage. It doesn’t replace it for the rest.

A Different Path Worth Considering

If you’re reading this because cellular hurts and LoRaWAN is half-deployed, there’s a third option that didn’t exist two years ago: Bluetooth Low Energy direct-to-satellite. Hubble’s satellites detect standard BLE advertising packets from off-the-shelf devices, no LoRa modem required. Power draw is roughly an order of magnitude lower than satellite LoRa uplink, and BLE silicon is cheaper and more available than LR-FHSS-capable LoRa parts.

It’s not the right answer for every use case (continuous downlink, large payloads, and licensed-spectrum mandates still point elsewhere), but for asset tracking and intermittent telemetry it’s worth a serious look. The Hubble device SDK and asset tracking integration guide cover the firmware path, and the reference applications on GitHub show what an integration actually looks like in code.

Run the Numbers Before You Sign

Visit the three operators’ sites for current pricing and pass schedules. Those numbers move quarter to quarter, and any figure in this article will be stale by the time you negotiate. Then run the decision framework against your actual requirements: how often must each device report, how quickly must a downlink land, and where on Earth are these things?

If the answers point to satellite LoRa, pick the operator that fits your geography and your firmware team’s tolerance for proprietary stacks. If the answers reveal that you mostly need low-power, low-cadence uplink from cheap devices that already exist, BLE-to-satellite is probably the cheaper and simpler path.

Hubble Network turns existing BLE devices into globally trackable assets—no proprietary radios, no pass scheduling, no firmware rewrites. See how it works →