Connectivity Layer

The connectivity layer is where most IoT projects succeed or fail quietly, months after launch: not because the technology doesn’t work, but because it was chosen for the demo environment rather than the real one. This page explains the main connectivity categories, what each is genuinely good at, and what to check before you commit a device design to one of them.

What the connectivity layer actually does

Every IoT device needs a way to get data off itself and onto a network, and, in most designs, a way to receive commands or configuration back. The connectivity layer is the combination of radio technology, network infrastructure and (for cellular and satellite options) commercial relationship that makes that possible.

The choice affects far more than data speed. It determines battery life, hardware cost, coverage, how easily the product can be sold into other countries, and how much ongoing operational risk you’re carrying with a network operator or connectivity provider.

The main connectivity categories

Cellular IoT (LTE-M, NB-IoT, 5G RedCap)

Cellular IoT technologies use existing mobile networks rather than infrastructure you build yourself. As of January 2026, LTE-M is available on more than 60 commercial networks with particularly strong coverage in North America and Europe, while NB-IoT has broader global reach with over 110 commercial networks, especially across China and Asia-Pacific (Hologram, 2026). Both are designed for battery-powered devices that need to run for years on a single charge and send small amounts of data infrequently, such as meter reading, asset tracking and environmental sensors.

5G RedCap is a newer addition, positioned between full 5G and LTE-M/NB-IoT. It supports higher throughput (up to 220 Mbps downlink) at 50-70% lower device cost than full 5G, aimed at mid-tier applications, including industrial cameras, wearables and some healthcare devices, that need more bandwidth than NB-IoT offers but don’t justify full 5G hardware. Commercial availability is still early: around 30 operators across 21 countries supported RedCap as of January 2026, with broader rollout expected through 2027-2028 (Telecom Review, 2026).

Good fit for: devices that need wide-area coverage without you building any infrastructure, and where the unit economics support a SIM (physical or eSIM) and ongoing airtime cost.

LPWAN (LoRaWAN, Sigfox)

Low Power Wide Area Network technologies trade throughput for very low power consumption and, in LoRaWAN’s case, the option to run your own network rather than paying an operator. LoRaWAN is the current market leader outside China, and its share is projected to converge with LTE-M by around 2027 as both settle near 35% of the global LPWAN market (Mordor Intelligence, 2026).

Sigfox is a more mixed picture. It still covers roughly 95% of the population across the 70-plus countries it operates in, but its market share is declining, and a number of former Sigfox deployments have migrated to LoRaWAN or NB-IoT. Semtech’s move to integrate Sigfox’s 0G technology with LoRa Edge points to a broader shift towards hybrid LPWAN approaches rather than Sigfox standing alone (DFRobot, 2025).

Good fit for: low-frequency, small-payload use cases such as agriculture, asset tracking and utility metering, particularly where you want to control your own network rather than depend on a mobile operator.

Wi-Fi and Wi-Fi HaLow

Standard Wi-Fi remains the default for high-bandwidth, mains-powered or frequently-charged devices operating within range of existing infrastructure, such as cameras, smart displays and hubs. Its limitation for IoT has always been range and power draw.

Wi-Fi HaLow (802.11ah) addresses both: longer range and substantially lower power consumption than conventional Wi-Fi, while staying within the Wi-Fi ecosystem rather than requiring a separate gateway technology. Adoption is still building; device shipments are forecast to pass 100 million units annually by the end of the decade, with early traction in smart buildings, healthcare and industrial automation (Wi-Fi NOW Global, January 2026), so component availability and cost are worth checking carefully before committing a product design to it today.

Good fit for: local, high-bandwidth applications, and increasingly for longer-range sensor deployments where staying inside the Wi-Fi ecosystem, rather than adding LPWAN, simplifies the stack.

Bluetooth and Bluetooth LE

Bluetooth LE remains the default for short-range, battery-powered devices such as wearables, personal health devices and smart home sensors, and currently accounts for around 24% of connected IoT devices worldwide, more than any other single radio technology (TechFonts, 2026). It typically uses an order of magnitude less power than Wi-Fi, at the cost of range and the need for a nearby gateway or smartphone to bridge data onward.

Good fit for: short-range, low-data, battery-constrained devices where a phone, hub or gateway is already part of the product experience.

Satellite and Non-Terrestrial Networks (NTN)

Satellite IoT has moved from a specialist niche to a mainstream fallback option. The 3GPP’s NTN standard (from Release 17 for NB-IoT NTN, extending through Releases 18 and 19) allows the same SIM and the same carrier relationship to work over satellite when terrestrial cellular coverage isn’t available: genuinely useful for remote agriculture, mining, energy and logistics assets that spend part of their life outside network coverage. Iridium’s NTN Direct service, going live in 2026, is positioned as the first globally available 3GPP-standard NB-IoT satellite service, and Deutsche Telekom plans to offer four satellite connectivity options across two orbital regimes to its IoT customers by the end of 2026 (Hubble Network, 2026).

Good fit for: assets that operate outside reliable terrestrial coverage, where satellite is used as a fallback or primary layer rather than the everyday connectivity for a mass-market product.

Comparing the options at a glance

Technology	Typical power use	Typical range	Typical data volume	Infrastructure
LTE-M / NB-IoT	Low	Wide-area (operator network)	Small, infrequent	Operator-provided
5G RedCap	Moderate	Wide-area (operator network)	Moderate to high	Operator-provided
LoRaWAN	Very low	Long-range (km, line-of-sight dependent)	Very small, infrequent	Operator or self-hosted
Sigfox	Very low	Long-range	Very small, infrequent	Operator-provided (declining)
Wi-Fi	Higher	Short (tens of metres)	High	Self-hosted (existing)
Wi-Fi HaLow	Low	Long-range for Wi-Fi (up to ~1km)	Moderate	Self-hosted
Bluetooth LE	Very low	Short (tens of metres)	Small	Gateway or phone required
Satellite / NTN	Moderate to high	Global	Small	Satellite operator

Treat this as a starting point for narrowing options, not a final answer: real decisions depend on your specific power budget, coverage requirements and unit economics. Choosing IoT connectivity: cellular, LPWAN, Wi-Fi and satellite compared walks through a fuller decision framework with worked scenarios.

What to check before you commit

Coverage in the actual deployment environment, not just the nearest city. Rural, indoor and underground coverage can differ sharply from operator coverage maps.
Total cost over the device’s lifetime, including airtime, hardware, and any network or platform fees, not just the unit cost of the module.
Regulatory approval in every country you intend to sell or deploy into. Radio approvals and, for cellular, operator certification, can add months to a launch timeline.
What happens if the connection fails. Locally cached data, retry behaviour and graceful degradation matter as much as the happy path.
Vendor and operator lock-in. Understand what it takes to change connectivity provider later, before you need to.

About this page

Written by Mark Searle, founder of IoT Heart and an IoT connectivity professional with more than 20 years’ experience across network engineering, solution architecture and commercial connected services. This page is based on publicly available industry data and standards documentation, current as of August 2026; connectivity markets move quickly, so figures and operator availability should be checked against current sources before a purchasing decision.

Want the practical version of updates like this delivered twice a month? Join the IoT Heart Briefing.