Iridium Activates Standards-Based Satellite IoT Using 3GPP NB-IoT Protocols
Iridium's commercial NTN Direct service eliminates proprietary satellite protocols for remote assets. Enterprises gain standardized fallback connectivity without separate device stacks.
Iridium's standards-based satellite service changes remote connectivity economics
Iridium Communications activated commercial service for Iridium NTN Direct on November 17, using 3GPP NB-IoT protocols over its existing L-band low-Earth-orbit constellation. The service marks the first commercial deployment of standards-based direct-to-device narrowband-IoT over an active mobile-satellite-services network. For enterprises managing pipelines, maritime vessels, agricultural equipment, utilities, and remote industrial assets, the development means satellite fallback no longer requires a separate protocol stack, antenna design, or module certification process.
The shift from proprietary satellite IoT protocols to 3GPP NB-IoT eliminates one layer of integration cost. Module makers and platform vendors can reuse existing NB-IoT device designs instead of adopting satellite-specific hardware. That matters for procurement teams balancing cellular connectivity in coverage areas against satellite fallback for assets that move through remote zones. Where terrestrial LTE-M or NB-IoT networks end, Iridium NTN Direct provides continuity without forcing a protocol switch at the application layer.
Iridium operates through its existing L-band LEO constellation, avoiding the capital expense and deployment timeline of a new satellite network. The service supports low-power, wide-area data transmission for land, maritime, and airborne assets. What remains unresolved: public pricing, per-device costs, antenna requirements, message-size limits, latency specifications, and whether existing NB-IoT hardware requires firmware updates or new certification to work with the satellite link. The announcement provides no performance benchmarks, customer deployments, or device counts.
iWire expands Sigfox 0G networks across 12 countries with $34 million
iWire raised $34 million in Series A financing to expand Sigfox 0G infrastructure across 12 countries in Asia, the Middle East, and Africa. Noor Capital led the round, with Bpifrance providing a $25 million buyer credit specifically for Sigfox network development. iWire reports raising more than $47 million over the past three years.
The expansion could close geographic gaps that previously limited Sigfox for multinational deployments. Sigfox 0G competes with LoRaWAN, cellular NB-IoT/LTE-M, and satellite IoT for low-bandwidth asset tracking, metering, environmental monitoring, and industrial telemetry. Its differentiation comes from low-power operation and simplified endpoint connectivity. LoRaWAN typically offers greater ecosystem flexibility through private networks, while cellular technologies provide broader operator integration and higher throughput.
What the announcement omits: subscriber counts, endpoint counts, coverage maps, service pricing, and network-performance data. Procurement teams should not treat the financing as proof of commercial scale. Buyers need country-by-country coverage commitments, roaming terms, device availability, SLA language, and an exit plan if local Sigfox availability proves thinner than LoRaWAN or cellular alternatives in target markets.
NIST begins revision of federal IoT cybersecurity requirements
NIST initiated a revision of Special Publication 800-213A, the IoT Device Cybersecurity Requirement Catalog for federal government procurement, and opened a pre-draft call for comments on November 16. The catalog supports cybersecurity requirements for government IoT acquisition. The activity is at the pre-draft stage, not a finalized standard or compliance deadline.
The revision could increase the importance of security capabilities that differentiate enterprise IoT platforms and device vendors: secure update mechanisms, identity, vulnerability disclosure, logging, cryptographic protections, and lifecycle support. Federal suppliers and enterprises selling into government should monitor the revision before finalizing long-lived device contracts.
The immediate budget impact is limited because no final requirements or deadline were announced. Buyers should preserve contract flexibility around firmware updates, vulnerability remediation, software bills of materials, device identity, and end-of-support obligations. Architecture and procurement decisions made now should accommodate stricter lifecycle-security requirements when the revision is finalized.
What to watch
Iridium NTN Direct is the clearest new option for standardized satellite fallback, but pricing, hardware compatibility, and service-level data remain unresolved. Request module certification timelines, roaming terms, and antenna specifications before committing remote-asset designs to the service.
iWire's financing could improve Sigfox availability across 12 additional markets, but buyers need verifiable coverage and pricing commitments before selecting it over LoRaWAN or NB-IoT. Require country-by-country coverage maps and performance guarantees in contract language.
NIST's SP 800-213A revision is an early warning for federal-facing suppliers. Contract decisions made now should preserve flexibility for stricter firmware-update, vulnerability-disclosure, and end-of-life requirements. The available announcements provide no independent adoption figures, benchmark results, subscriber counts, or customer deployments for the new Iridium service or the expanded Sigfox network.
Technology decisions, clearly explained.
Weekly analysis of the tools, platforms, and strategies that matter to B2B technology buyers. No fluff, no vendor spin.
