Satellite on a Chip and the 2030 Quantum Deadline: Two IoT Leaps This Week

Introduction

Two announcements this week land on the same fault line in the Internet of Things: the gap between where a device is deployed and where its security assumptions were made. On October 16, 2026, Iridium Communications announced that Altair Semiconductor is integrating Iridium NTN Direct satellite capability into the ALT1350 and next-generation ALT1550 cellular IoT chipsets, giving device makers a single chip that can speak both terrestrial LTE-M/NB-IoT and low-Earth-orbit satellite. A day earlier, IoT Business News published a detailed engineering analysis of post-quantum readiness for long-lived IoT devices, arguing that the decisions made before a hardware design is frozen — flash size, bootloader, trust anchor storage — determine whether a device can still receive secure firmware updates after 2030.

Together, the two stories describe the same industry at two different altitudes: connectivity that now reaches anywhere on Earth, and cryptography that has to survive the next decade. For manufacturers, the practical question is no longer whether a remote asset can phone home, but whether the device they ship this year will still be cryptographically trustworthy when a quantum computer finally arrives.

Altair and Iridium: Satellite Connectivity on a Single IoT Chip

The Altair–Iridium partnership is a consolidation play in the non-terrestrial network (NTN) market. Until now, connecting an IoT device beyond terrestrial cellular coverage required a separate satellite modem, with the cost, power, and board space that implies. By integrating Iridium NTN Direct into Altair's ALT1350 and ALT1550 platforms, device manufacturers, module makers, and mobile network operators get both terrestrial cellular and satellite connectivity on one chipset.

The ALT1350 is Altair's ultra-low-power LTE-M/NB-IoT platform, aimed at asset tracking, logistics, smart metering and utilities, agriculture, vehicle telematics, and industrial monitoring. The ALT1550 extends the same idea to 5G reduced-capability (RedCap) devices — wearables, smart glasses, and AI-enabled consumer products that need to stay connected wherever they go. Iridium NTN Direct is built on the company's fully operational LEO constellation and globally coordinated L-band spectrum, and it is designed to support NB-IoT and direct-to-device applications using compatible 3GPP standards-based chipsets.

The strategic logic is straightforward. Iridium's Tim Last framed the deal as giving device manufacturers "a powerful new way to develop connected products" by pairing Altair's low-power IoT silicon with Iridium's "truly global satellite network." Altair's Dima Feldman put it in engineering terms: adding Iridium NTN Direct to the ALT1350 and ALT1550 gives customers "greater flexibility in how and where their IoT devices connect." Altair joins a growing ecosystem of chipmakers, module manufacturers, OEMs, and IoT developers building NTN-cellular integration around Iridium NTN Direct.

The catch, as the second source reporting on the same announcement notes, is that the practical benefits depend on service availability, device compatibility, and the power and cost requirements of individual applications. A satellite-capable chip is not automatically a satellite-connected product. But the direction of travel is clear: the boundary between terrestrial and satellite IoT is dissolving into a single radio, and the next generation of cellular IoT silicon will be expected to cover both.

For context on why this matters, the IoT industry already passed 7 million satellite IoT subscribers, with Berg Insight projecting 42 million by 2030. Cellular IoT module shipments are rising 15 percent year-over-year, with Cat 1 bis taking the lead. Adding satellite as a fallback on the same die removes the single biggest friction in remote deployments — the need to design, certify, and power a second radio. Read more about the broader connected-device landscape in our IoT coverage.

Post-Quantum Readiness: Why Long-Lived IoT Devices Face a 2030 Design Freeze

The second story is less visible but arguably more consequential. Once a hardware design is frozen, flash size, boot code, and key storage are fixed for the entire product line. Today, manufacturers protect firmware updates and network connections with RSA and elliptic-curve cryptography. A cryptographically relevant quantum computer — a machine that can solve the mathematical problems behind both schemes — would break that protection, and the device would have no way to recover unless its trust anchor was designed to be replaceable.

The most immediate risk is not traffic recorded today and decrypted later. It is forged firmware. A device that verifies its firmware with ECDSA trusts that algorithm until its trust anchor is replaced. If the trust anchor cannot be changed, the device will accept a forged update from the day ECDSA is broken. The manufacturer may then have no choice but to replace devices in the field. As the engineering analysis puts it, a little more flash on the bill of materials costs less than a service call for every unit.

The regulatory timeline is tightening around the same date. NIST proposes deprecating RSA and ECDSA at the widely used 112-bit security level after 2030 and disallowing classical algorithms after 2035. The European Commission recommends that member states begin the transition to post-quantum cryptography by the end of 2026 and move high-risk use cases over by the end of 2030. Starting in December 2027, the EU's Cyber Resilience Act requires every manufacturer to set a support period during which it handles vulnerabilities in its product — for a device launched in 2028 with support into the 2030s, the EU and NIST deadlines fall inside the years its maker is still responsible for security updates. Manufacturers supplying U.S. national security systems face even earlier dates under NSA's CNSA 2.0 suite.

The physics of the transition is unforgiving. NIST has standardized ML-DSA for firmware signatures and ML-KEM for key exchange. Even the smallest ML-DSA parameter set needs 1,312 bytes for the public key and 2,420 bytes for each signature. Image headers, certificate fields, and key slots in today's designs cannot hold values of that size, so manufacturers must add extra flash before design freeze. Boot takes longer too: verifying a post-quantum signature took 34 milliseconds in one documented project, versus 3 milliseconds for the previous hardware-accelerated check, requiring a dedicated accelerator that took longer to source and integrate than planned.

The radio impact is even more significant. In the smart home standard Matter running over the Thread radio protocol, a drop-in post-quantum handshake grows from 1.6 kB to 22.8 kB, while a Thread radio frame carries at most 127 bytes. A hybrid key exchange — pairing a classical algorithm with a post-quantum one while keeping existing certificates — stays within Matter's message limit, so makers of Matter devices can protect session keys without changing radio technology. Dual-signed images will be larger and must still be transmitted over existing low-bandwidth links such as NB-IoT or Thread, so operators should plan for longer transfers, more retries, and staggered rollouts.

Crypto agility is the way out: a device that can switch algorithms and trust anchors through a signed update, with no new hardware. On a microcontroller, that requires a bootloader supporting more than one signature algorithm and a protected, updatable store for trust anchors. The draft European standard ETSI EN 304 623 requires bootloaders with a replaceable trust anchor to support combined verification — for example a classical and a post-quantum signature on the same boot stage, which runs only if both signatures are valid. Manufacturers should have their signing systems, including suitable hardware security modules, in place before the first device checks the new signatures. Stateful hash-based signature schemes suit firmware signing, but NIST allows them only inside certified HSMs at security level 3 or higher, and the signing software has to track every one-time key it has used.

Conclusion

The week of October 14–16 shows two sides of the same industrial maturation curve. On one axis, Altair and Iridium are making it easier to connect devices anywhere on Earth by collapsing the radio stack into a single silicon solution. On the other, NIST, the EU Cyber Resilience Act, and early engineering projects are forcing manufacturers to think about quantum threats at the point where they lock in component choices. The decisions made before design freeze in late 2026 will determine which devices are still getting security updates in 2031.

For IoT operators and enterprise buyers, the message is practical: ask suppliers whether their cellular modules will survive a switch to post-quantum key exchange, and whether their satellite-capable chips have a path to low-power handover between terrestrial and satellite links. The next major firmware update should account for handshakes that are twenty times larger than today, and for boot times that may be ten times slower.

References

• Altair Semiconductor and Iridium Communications press releases, October 16, 2026
• Post-Quantum Readiness for Long-Lived IoT Devices, IoT Business News, October 15, 2026
• NIST IR 8547 Draft Transition Plan, National Institute of Standards and Technology, 2024
• ETSI EN 304 623 Draft European Standard on post-quantum firmware verification
• Iridium NTN Direct technical overview, Iridium Communications Inc.
• Connectivity Standards Alliance Matter 1.5 release notes, March 2026
• Thread Group, Thread 1.4 specification, October 2025