Long-range, low-power IoT deployments — smart meters, agricultural sensors, asset trackers, environmental monitors — have two dominant wireless protocol options in 2026: LoRaWAN and NB-IoT (Narrowband IoT). Both can cover kilometres per base station and run on small batteries for years. The choice between them comes down to your deployment model, data requirements, and who controls the infrastructure.
Protocol Fundamentals
LoRa (Long Range) is a physical layer modulation technique developed by Semtech; LoRaWAN is the network protocol on top of it, governed by the LoRa Alliance. It operates in unlicensed spectrum (868 MHz in Europe, 915 MHz in the US), so any organisation can deploy its own network — buy gateways, connect them to a network server, and own the infrastructure. Range is 2–15 km line of sight (1–5 km urban), data rate is 0.3–50 kbps, typical payload is 50–250 bytes, and battery life is 5–10+ years for low-duty-cycle sensors. The Things Network and Helium provide shared networks for deployments that don’t want to own infrastructure.
NB-IoT is a 3GPP standard that runs on licensed spectrum, delivered by mobile network operators using existing LTE infrastructure. Range matches LTE coverage — 10–15 km rural with strong indoor penetration. Data rate is 20–250 kbps, latency is typically 1–10 seconds, and battery life exceeds 10 years using PSM (Power Saving Mode) and eDRX.
Head-to-Head Comparison
| Characteristic | LoRaWAN | NB-IoT |
|---|---|---|
| Spectrum | Unlicensed (868/915 MHz) | Licensed cellular |
| Infrastructure control | Your own or community | Carrier-managed |
| Upfront cost | Gateway hardware required | No infrastructure needed |
| Recurring cost | Low (self-hosted) or usage-based | Per-device SIM/subscription |
| Data rate | Very low (< 50 kbps) | Low-medium (up to 250 kbps) |
| Latency | Seconds to minutes | Seconds |
| Downlink support | Limited (Class B/C devices) | Full bidirectional |
| Indoor penetration | Good | Very good (20 dB link budget advantage) |
| Roaming | Limited/community networks | Global (SIM roaming) |
| Security | AES-128 end-to-end | 3GPP cellular security |
| Regulatory risk | Low (unlicensed spectrum generally stable) | Depends on carrier network longevity |
Where LoRaWAN Wins
Private network deployments. If you’re deploying across a factory, farm, or campus, LoRaWAN gateways (£200–600 each) give you complete control, no recurring connectivity fees, and no dependency on carrier coverage. A single gateway covering a 2 km radius can support thousands of sensors.
Ultra-low-cost per-device. LoRaWAN modules cost £3–8 in volume. Without SIM cards or carrier contracts, the per-device total is lower for large sensor populations.
Very low data rate applications. Temperature readings every 15 minutes, soil moisture hourly, door open/close events — these fit comfortably within LoRaWAN’s duty cycle and payload limits. No need for NB-IoT’s broader bandwidth.
Community and open ecosystems. The Things Network provides free uplink for low-volume applications. For pilot projects, you can test at near-zero cost using community gateways before investing in infrastructure.
Where NB-IoT Wins
Wide-area deployments without infrastructure investment. If your sensors are spread across hundreds of square kilometres — agricultural land, a utility’s distribution network — installing LoRaWAN gateways everywhere is expensive and operationally complex. NB-IoT uses existing carrier infrastructure.
Mobile and roaming assets. Vehicle trackers, freight sensors, and any device that moves beyond a fixed coverage area need carrier-managed roaming. LoRaWAN’s roaming story is improving but remains fragmented.
Deeper indoor penetration. NB-IoT’s enhanced coverage mode (ECL 2) can reach deep-indoor locations — basement meters, underground infrastructure — that LoRaWAN struggles with.
Firmware over-the-air (FOTA) updates. NB-IoT’s downlink capability and higher data rates make pushing firmware updates to deployed devices more practical. LoRaWAN FOTA is technically possible but slow and constrained by duty cycle limits.
Mission-critical reliability requirements. Cellular networks have SLA-backed reliability. LoRaWAN community networks don’t, and self-hosted LoRaWAN requires your own network management.
Cost Modelling Example
For 500 temperature sensors across a 10 km² industrial site:
LoRaWAN:
- 2 gateways @ £400 each = £800 (single-time)
- Network server hosting = £50/month
- Sensor modules @ £6 each = £3,000
- Total year 1: ~£4,400 | Year 3: ~£5,600
NB-IoT:
- No gateway infrastructure
- SIM cards + connectivity @ £1.50/device/month = £750/month
- Sensor modules @ £12 each = £6,000
- Total year 1: ~£15,000 | Year 3: ~£33,000
At this scale, LoRaWAN has a substantial cost advantage if you can deploy your own gateways. The calculation changes for geographically dispersed deployments where gateway density becomes the bottleneck.
Hybrid Approaches
Large-scale deployments increasingly use both protocols: LoRaWAN for high-density, fixed-location sensor clusters within controlled areas, NB-IoT for outlying or mobile assets where LoRaWAN coverage is impractical. The device data normalises at the application layer regardless of transport.
Both protocols coexist with shorter-range options: Zigbee, Thread, BLE, and Wi-Fi 6 handle local mesh networks, while LoRaWAN or NB-IoT provides the backhaul. Gateway-layer edge compute increasingly pre-processes sensor data before forwarding summaries over LPWAN, reducing bandwidth and battery consumption.
The 2026 Landscape
LoRaWAN 1.1 addressed the most serious early security gaps, and commercial coverage from operators like Orange, KPN, and Swisscom has expanded. Helium’s move to a commercial model in 2023 reduced community coverage in some areas, which is why private gateway deployments have become the default for fixed-site applications.
NB-IoT is broadly available on all major carriers in Europe, Asia, and increasingly North America. Cat-M1 (LTE-M) — a sibling standard with higher data rates and voice support — is often deployed alongside NB-IoT on the same carrier infrastructure. If your devices need bidirectional data or firmware OTA update capability, LTE-M is worth comparing directly before you commit to NB-IoT.
Neither technology is going away, and neither is universally better. The cost model in this article illustrates where the crossover point sits for a mid-size deployment. If your use case lands near that crossover, run a small pilot on each before committing to fleet-scale procurement.