IoT connectivity: why we don't choose between WiFi, LTE, and LoRa

Every IoT project eventually runs into the same question: which radio technology should we use? The answer you get in a lot of advisory conversations is a single winning technology — usually whichever one the advisor happens to know best. We see it differently. IoT connectivity isn't a choice between WiFi, LTE, and LoRa — it's a design question in which they complement each other. That's not a neutral observation — it's a conviction we bring back into every integration project.

This article covers the trade-off between WiFi, LTE (including LTE-M and NB-IoT), and LoRa/LoRaWAN for IoT sensor data, and how that choice relates to the rest of your system landscape. It does not cover 5G network build-out, satellite connectivity, or the choice between public and private LoRaWAN networks — those are separate follow-up questions.

In this article:

• There Is No Best Radio Technology, Only the Best Match
• Why "Which Technology" Is the Wrong Question
• Our View: Connectivity Is Infrastructure, Not an Endpoint
• It's Not About Which Technology Wins
• Frequently Asked Questions

There Is No Best Radio Technology, Only the Best Match

We call this the connectivity trade-off: every wireless technology has to pick between four variables — range, bandwidth, power consumption, and cost. No technology scores well on all four — which is exactly why several exist side by side.

WiFi delivers high bandwidth over short distances, at relatively high power consumption. As soon as a sensor moves out of a router's range, WiFi is no longer an option.

LTE — and its IoT-specific variants LTE-M and NB-IoT — provide coverage where WiFi can't reach: outdoors, on the move, in remote locations. Dutch providers like KPN Business and Odido Business describe this distinction in similar terms: LTE-M for mobile applications that occasionally need bandwidth, NB-IoT for sensors that mainly need to report efficiently and predictably.

LoRa, and the LoRaWAN network protocol built around it, takes the opposite extreme: extremely long range and extremely low power consumption, in exchange for very limited bandwidth. Because LoRa operates on the free 868 MHz ISM band, European ETSI regulation (EN 300 220) imposes a duty-cycle limit — typically a maximum of 1% transmit time per channel — that caps hourly data volume; see the technical explanation from the LoRaWAN Alliance and the similar explanation from Eurofiber. A LoRa sensor can run for years on a single battery and cover tens of kilometers in a rural area — but it can't send camera footage.

None of these three is "better." They're built for different points in the connectivity trade-off.

Why "Which Technology" Is the Wrong Question

The real mistake we often see in IoT projects: an organization picks a single radio technology at the start of a project, then discovers afterward that some of the use cases don't fit it. A facilities company rolling out sensors across hundreds of locations has different requirements indoors than it does on the outdoor grounds. A logistics company tracking assets needs different coverage on the road than it does at its own warehouse.

The question that matters isn't "WiFi, LTE, or LoRa" but: what problem am I solving, at what location, with what power budget, and how often does data need to come in? From those four answers, the technology often follows on its own — and just as often, the answer is "a combination."

That's also why vendors like Blues Wireless explicitly build modules that can switch between cellular, WiFi, LoRa, and satellite without the application code changing. Decoupling the radio technology from the rest of the system — so a change at the physical layer doesn't mean rebuilding the whole stack — is exactly the mindset we hold, regardless of which vendor you ultimately choose.

Our View: Connectivity Is Infrastructure, Not an Endpoint

At too many IoT initiatives, the radio technology becomes the first decision instead of one of the last. That reverses the order. We treat connectivity as an infrastructure choice that serves the system behind it: the data has to land somewhere, get processed, and deliver value inside the systems an organization already uses. A sensor that's perfectly connected but delivers no data to the ERP, asset, or maintenance system solves nothing.

In practice, that means:

• Start with the problem, not the protocol. Range, power budget, and data needs per location determine the technology — not the other way around.
• Keep the radio choice reversible. An architecture that can handle WiFi, LTE, and LoRa side by side prevents a scale-up or a new location from requiring a redesign of the whole system.
• Security is weighed per technology. LoRa runs on free frequencies and is, by default, less well secured than cellular networks on licensed spectrum — for sensitive business data, that's a real trade-off to weigh, not a footnote.
• Radio technology is the start of the chain, not the end. What happens to the data once it arrives determines whether the project delivers value.

It's Not About Which Technology Wins

WiFi, LTE, and LoRa don't compete with each other — they serve different points in the same connectivity trade-off. Organizations that take IoT seriously stop searching for "the best" radio technology and start designing an architecture that can work with several. That's why we approach radio technology with enthusiasm: not because one chip is better than another, but because the combination — well designed — lets an organization scale without starting over every time.

Frequently Asked Questions

What's the difference between LTE-M and NB-IoT? Both are IoT variants of the mobile 4G network and run on licensed spectrum. LTE-M supports more bandwidth and mobility (handover between cell towers), which makes it suitable for moving assets such as vehicle trackers. NB-IoT is more power-efficient and slower, built for stationary sensors that only send a small message a few times a day.

Is LoRa secure enough for business data? LoRaWAN has encryption by default, but it runs on a free, unlicensed frequency band that anyone can use and listen in on. For sensitive business data, a cellular technology on licensed spectrum (LTE-M, NB-IoT) is usually a safer foundation; LoRa remains strong for use cases where battery life and range matter more than the security level.

Can WiFi, LTE, and LoRa coexist within the same IoT project? Yes, and in practice that's often the best solution. An architecture that can handle multiple radio technologies — without having to rebuild the rest of the system — prevents a new location or a scale-up from requiring a full redesign.

Why doesn't every company choose LoRa, given its low power use and long range? Because LoRa's limited bandwidth and statutory duty-cycle limit make it unsuitable for anything beyond small, occasional messages. Camera footage, firmware updates, or high-frequency data streams simply don't fit within that constraint — that's what WiFi or LTE is for.