What Hardware Are Companies Actually Using for Satellite IoT in Production?

Industrial satellite IoT devices and trackers deployed across remote locations and mobile assets

You’ve seen the announcements. Thirty-plus satellite IoT devices launched (or “launched”) in the last two years. Partnership press releases with logos from companies you’ve half-heard of. Trade show demos where everything works perfectly over a conference center’s Wi-Fi backhaul. Delivery timelines that say “available Q4” without specifying which year.

And yet when you actually try to buy satellite IoT hardware for a production deployment, thousands of units, real assets, real reporting intervals, the list of options that are certified, shipping, and connected to an operational constellation shrinks to a disturbingly small number.

This isn’t a research failure on your part. The satellite IoT hardware market is genuinely cluttered with pre-production announcements masquerading as products. This article cuts through it. We’ll name specific devices, modules, and chipsets, tell you which constellation each depends on, and give you an honest read on what’s actually deployed at scale versus what’s still a slide deck. If you’re evaluating satellite asset tracking use cases, this is your shortlist starting point.

Three Lanes of Satellite IoT Hardware You Need to Understand

Before we get to specific products, a quick framing. Satellite IoT hardware falls into three distinct lanes, and confusing them is where most bad purchasing decisions start.

Lane 1: Legacy Mobile Satellite Services (MSS). This is Iridium, Globalstar, and Orbcomm. Their constellations are operational, in some cases for decades. Device ecosystems are mature. Nothing flashy, but they work.

Lane 2: Proprietary LEO newcomers. Companies like Swarm (now SpaceX), Kinéis, Astrocast, and Myriota (now OQ Technology) that launched their own small-satellite constellations with their own proprietary protocols. Maturity varies. Some have commercial devices in the field; others are still filling out their constellation.

Lane 3: 3GPP NTN / Direct-to-Device. Standards-based satellite connectivity from chipset vendors like Qualcomm, MediaTek, and Sony Altair, plus network operators like Skylo. This is the future everyone’s betting on, but the device ecosystem is early.

This article focuses on end devices and modules, the hardware you actually procure and deploy, not the satellite business models behind them.

Production-Proven Satellite IoT Devices and Modules Actually in the Field

This is the section you came for. Each entry names the device, what’s inside it, which constellation it rides, and whether it’s genuinely deployed at production scale.

Iridium Ecosystem: The Workhorse

Iridium’s 66-satellite LEO constellation has been operational since the early 2000s (current generation: Iridium NEXT, fully deployed since 2019). The Iridium Short Burst Data (SBD) service is the backbone of most production satellite IoT deployments today. The module you’ll find inside most devices is the Iridium 9603N, a compact SBD transceiver that’s been integrated into dozens of third-party products.

Queclink GL600MG: A dual-mode cellular + Iridium asset tracker built around the Iridium 9523 module. Designed for intermodal container and trailer tracking. Shipping and deployed in commercial fleets. This is one of the few purpose-built satellite asset trackers you can order in volume today.

NAL Research AT6 series: Ruggedized Iridium SBD trackers used heavily in government and defense asset tracking. Not consumer-facing, but battle-tested in the most literal sense.

Ground Control RockBLOCK 9603: An Iridium SBD modem built for OEM integration and developer prototyping. If you’ve seen a custom satellite IoT project in the wild, there’s a decent chance a RockBLOCK is inside it. Production-ready, well-documented, and available off the shelf.

The honest truth about Iridium: the hardware works, global coverage is real (pole-to-pole), and the ecosystem is deep. The tradeoff is cost. Iridium SBD data plans are expensive per byte compared to terrestrial, and the 9603N module itself isn’t cheap. But if you need something that works today with true global coverage, this is where most production deployments land.

Globalstar Ecosystem: High Volume, Regional Coverage

SPOT Trace: One of the highest-volume satellite asset trackers ever sold. Simple, battery-powered, consumer/prosumer grade. Reports GPS position via Globalstar’s simplex network. Deployed widely for boat tracking, vehicle theft recovery, and equipment monitoring. It works, but don’t expect bidirectional communication or high update rates.

SmartOne C: Globalstar’s purpose-built commercial asset tracker for containers and trailers. Simplex (uplink-only) with multi-year battery life. Deployed at meaningful scale in logistics and intermodal operations.

The Globalstar caveat: coverage is not truly global. Globalstar’s constellation has known coverage gaps at extreme latitudes and mid-ocean regions. If your assets stay within North America, Europe, and major shipping lanes, this is fine. If you need polar or deep-ocean coverage, it’s not.

Orbcomm: The Reefer Container Standard

CT 3000 and ST 6100 series: Orbcomm has quietly become the dominant satellite IoT provider for refrigerated container monitoring. Major shipping lines deploy Orbcomm devices at massive scale. We’re talking hundreds of thousands of units on containers worldwide. The CT 3000 monitors temperature, door status, and GPS position via Orbcomm’s OG2/OGx constellation and also supports cellular fallback.

If your use case is intermodal container tracking, particularly reefer monitoring, Orbcomm hardware is the production benchmark. It’s not glamorous. It works.

The Reference Table

Here’s where every device lands in terms of production readiness. Bookmark this.

Device / ModuleManufacturerConstellationProduction StatusPrimary Use Case
GL600MGQueclinkIridium✅ ProductionAsset tracking
RockBLOCK 9603Ground ControlIridium SBD✅ ProductionOEM / developer
NAL Research AT6NAL ResearchIridium SBD✅ ProductionDefense / gov’t
SPOT TraceGlobalstarGlobalstar✅ ProductionAsset tracking
SmartOne CGlobalstarGlobalstar✅ ProductionContainer / trailer
CT 3000OrbcommOrbcomm OG2/OGx✅ ProductionReefer container
ST 6100OrbcommOrbcomm OG2/OGx✅ ProductionFleet / asset
M138 ModemSwarm (SpaceX)Swarm LEO⚠️ UncertainOEM integration
Astronode SAstrocastAstrocast LEO⚠️ Early productionOEM integration
KIM1 ModuleKinéisKinéis LEO⚠️ Early productionMaritime / ag
Myriota ModuleOQ TechnologyMyriota LEO⚠️ Post-acquisitionAgriculture / asset
Skylo (via partners)Skylo / OEMsGEO NTN🔶 ScalingMaritime telemetry

The ⚠️ Category: Shipping But With Caveats

Swarm M138 (SpaceX): Swarm’s tiny VHF satellite modem was one of the most exciting new entrants: low cost, low power, novel protocol. SpaceX acquired Swarm in 2021. The M138 modem shipped to developers and OEM integrators, but SpaceX has been opaque about the product’s long-term roadmap. The concern is that SpaceX may fold Swarm’s capabilities into Starlink Direct-to-Cell and sunset the standalone product. If you’ve built a product around the M138, you need to get clarity from SpaceX on continuity, in writing.

Astrocast Astronode S: A small, low-power satellite module designed for OEM integration. Astrocast has launched satellites and has commercial partners integrating the module. However, the constellation is still growing, which means coverage windows (time between satellite passes) can be long. Honest assessment: it’s technically in production, but coverage-dependent latency may not meet your operational requirements yet. Ask for real-world P95 latency data before committing.

Kinéis KIM1: The French company launched its 25-satellite constellation in 2024. The KIM1 module is available for integration. This is genuinely early production: the constellation is new, the partner device ecosystem is still forming, and real-world deployment data is limited. Worth watching closely, particularly for European and maritime use cases, but verify current coverage density before deploying.

Myriota Module (OQ Technology): Myriota built a clever LEO uplink-only protocol and had promising integrations, including Ceres Tag (satellite-connected livestock ear tags) and Digital Matter’s Yabby Edge tracker. Then OQ Technology acquired Myriota. Post-acquisition, the product roadmap and availability of the Myriota module are unclear. If you were evaluating Digital Matter’s Myriota-based devices, confirm current availability and long-term support directly with the manufacturer before ordering.

The Emerging NTN/3GPP Layer: Worth Watching, Not Worth Betting On Yet

This is where the industry wants to go: standards-based satellite connectivity using the same 3GPP protocols as terrestrial LTE/5G, so a single chipset can fall back to satellite when cell towers aren’t available.

Qualcomm 212S / 9205S: NTN-capable modem chipsets designed for IoT. Qualcomm has announced partners, but finding a shipping end device built on these chipsets for IoT asset tracking today is difficult. The chipsets exist. The devices mostly don’t, yet.

MediaTek NTN chipsets: Primarily targeting smartphones (the satellite SOS feature in consumer phones). IoT variants are coming, but the timeline is fuzzy.

Sony Altair ALT1350: Supports NTN in its feature set. We could not verify production IoT devices built on this specific chipset for satellite asset tracking at time of writing.

Skylo: Takes a different approach, using GEO satellites with an NTN-compatible network layer. Skylo has announced paying customers in maritime (partnering with existing satellite operators rather than launching its own constellation). This is one of the more credible NTN entrants, but the device ecosystem is still developing through partners.

Honest assessment: 3GPP NTN is almost certainly the long-term winner for satellite IoT. The economics and ecosystem effects of standards-based hardware are too powerful. But the device ecosystem is 12–24 months behind the press releases. If you need to deploy this year, NTN isn’t your answer.

Eight Questions That Separate Real Hardware from Vaporware

Before you commit budget to any satellite IoT hardware, run the vendor through these questions. Their willingness to answer, and the specificity of their answers, tells you everything.

  1. How many devices are deployed in production (not pilot) today? Ask for a number. Ask for a reference customer you can contact.
  2. How many satellites in your constellation are operational right now? Not launched. Operational. There’s a difference.
  3. What is the certified regulatory status? FCC, CE, ISED at minimum. No certification means no legal deployment.
  4. What’s the real message latency? Not the theoretical best case. The P95 latency measured in actual field deployments. For LEO newcomers with partial constellations, this number might be hours.
  5. What does the data plan cost per device per month at 1,000-unit scale? Many satellite IoT business models look reasonable at 10 units and break down at scale. Get the volume pricing in writing.
  6. If the constellation company gets acquired or shuts down, what’s my hardware fallback? This is not hypothetical. Swarm was acquired by SpaceX, Myriota by OQ Technology. Your hardware investment needs a continuity plan.
  7. Is the module single-source? If there’s only one chipset from one supplier, you’re carrying supply chain risk. Ask about second-source options or multi-constellation support.
  8. What’s the field-proven battery life at your recommended reporting interval? Datasheet battery life and real-world battery life are different things. Ask for field data, not lab data.

Any vendor that bristles at these questions is a vendor you should walk away from.

Boring Hardware Wins Deployments

Here’s the uncomfortable truth that no trade show keynote will tell you: the satellite IoT hardware that’s actually working in production, at scale, right now, is mostly the “boring” stuff. Iridium SBD devices. Orbcomm container trackers. Globalstar’s SPOT Trace. These products aren’t new. They aren’t exciting. They are deployed on hundreds of thousands of assets and they report reliably.

The newer options, Astrocast, Kinéis, and eventually NTN-based devices, are genuinely promising. But they carry real deployment risk today: partial constellation coverage, evolving product roadmaps, post-acquisition uncertainty, and thin field data.

The smart approach is tiered. Deploy proven hardware for your production fleet now. Run a parallel pilot with one or two promising newcomers on a small asset subset. Monitor the NTN standards ecosystem for when it matures, because it will.

Your assets can’t wait for the perfect satellite IoT device. But they also can’t afford a deployment built on a press release. Start with what’s shipping, validate what’s emerging, and keep your options open for satellite IoT connectivity options as the market matures. The vaporware will sort itself out. Your job is to not be the one who funded the sorting.


Hubble Network enables Bluetooth-to-satellite connectivity for standard BLE devices — no specialized hardware, no deployment risk. See how it works →