Smart Tech
Smarter Tomorrow
Smart Tech  ·  Smarter Tomorrow
Wireless RF September 10, 2026 12 min read

LoRaWAN vs. NB-IoT: Which Wireless Network Should Your IoT Project Use?

Two sensors, the same job, wildly different results — the wireless network underneath is why. A practical, plain-language guide to choosing between LoRaWAN and NB-IoT, from the basics through to real deployments.

LoRaWAN vs. NB-IoT comparison illustration: a private LoRaWAN gateway serving clustered sensors beside an NB-IoT cellular tower network
LoRaWAN, a network you own, versus NB-IoT, a network you rent from a cellular carrier.

Quick takeaways

  • LoRaWAN = you own the network (unlicensed radio, your own gateway). NB-IoT = you rent the network (a SIM card on a carrier's cellular towers).
  • LoRaWAN is the stronger fit for many low-power sensors clustered in one place — a farm, a factory, a campus. NB-IoT is the stronger fit for a few devices spread across a wide area, wherever cellular coverage already reaches.
  • Both are built for stationary, battery-powered sensors sending small amounts of data — neither is meant for anything that moves around while transmitting.
  • Cost tends to follow whichever technology already fits technically — treat it as a tiebreaker, not the starting point.
  • Real-world proof: a 500+ acre farm cut irrigation water use by 34% on a single LoRaWAN gateway — see the smart-farming case study.

Imagine two identical temperature sensors, each buried in an underground utility pit, each running on the same coin-cell battery. One is still reporting readings five years later. The other's battery is dead within five months. The sensors aren't different — the wireless network carrying their data is.

If you're building anything that sends small bits of data — a temperature reading, a water level, a tank pressure — from a remote or hard-to-reach location back to the internet, you've probably run into two popular answers: LoRaWAN and cellular NB-IoT. Both are built for exactly this job: long range, tiny data packets, years of battery life. But they get there in very different ways, and picking the wrong one shows up later as dead batteries, missed readings, or an unexpectedly complicated rollout.

This guide starts simple — what each technology actually is — and works up through how they're built, where each one is already being used in the real world, and how cost and complexity should (and shouldn't) factor into your decision.

1. Meet the two technologies

What is LoRaWAN?

LoRaWAN is a private radio network that you build and own. It's an open standard maintained by the LoRa Alliance, and it runs on free, unlicensed frequencies — 865–867 MHz in India (the IN865 band), 863–870 MHz in Europe (EU868), and 915 MHz in North America — so there's no carrier involved and no bill for airtime. You buy a gateway (think of it as a long-range Wi-Fi router built for whisper-quiet, battery-powered devices), mount it on a rooftop or tower, and every sensor within several kilometres can talk to it directly. A single gateway can typically support anywhere from a hundred to several thousand devices, which is why LoRaWAN shows up so often in smart agriculture, utility metering, and industrial monitoring — anywhere you have many sensors in one general area.

LoRaWAN data path: end nodes send readings over an RF LoRa link to gateways, which forward them over IP backhaul to a LoRaWAN network server and application dashboards
LoRaWAN: end nodes → your gateway → your network server → dashboards.

What is NB-IoT?

NB-IoT (Narrowband IoT) is a cellular technology — part of the 3GPP family of standards that also defines LTE and 5G. It uses the same towers, spectrum, and infrastructure as your phone, just optimised for small, infrequent data instead of video calls. Every device needs its own SIM (or eSIM) and a data subscription, exactly like a phone plan. In return, you get coverage almost anywhere a phone gets signal, with no network of your own to design, build, or maintain. This makes NB-IoT the natural choice when devices are spread out — utility meters scattered across a state, sensors on isolated infrastructure — where installing your own gateway network wouldn't make sense.

NB-IoT data path: end devices send readings over a narrowband cellular signal to carrier base stations, which forward them over the EPC core network to application servers and IoT dashboards
NB-IoT: end devices → carrier base station → carrier core network → application servers.

2. How they're actually built

The "own it vs. rent it" distinction above is the business-model difference. The engineering difference goes deeper — into network topology, radio spectrum, and how each technology squeezes a usable signal out of a noisy environment.

Network topology: a star pointing at you, or a star pointing at the carrier

Both networks are technically "star" topologies — every device talks directly to one central point rather than hopping through neighbouring devices. The difference is who operates that central point. In LoRaWAN, it's your gateway, feeding into a network server you control end-to-end — either self-hosted with open-source software like ChirpStack, or a hosted service. In NB-IoT, the central point is the carrier's base station, feeding into infrastructure you'll never touch. You're a tenant on someone else's network, not the landlord.

Radio spectrum and regulation

LoRaWAN operates in unlicensed ISM bands, which is what makes it free to use — but "unlicensed" comes with a catch: most regions cap how much airtime and power a device is allowed on those frequencies, to keep the shared spectrum usable for everyone. India's IN865 band happens to allow noticeably more transmit power than Europe's EU868 band, which is a real, practical advantage for Indian deployments — more on that in the next section. NB-IoT runs on licensed spectrum the carrier has paid for and controls exclusively: no airtime limit to worry about, but also no access without going through their network and their billing.

Modulation: trading speed for range

LoRaWAN's physical layer uses Chirp Spread Spectrum (CSS) — it spreads each bit of data across a wider slice of spectrum and repeats it, the radio equivalent of saying a word slowly and repeatedly until someone across a noisy room can piece it together. That's what lets a LoRaWAN signal be decoded even when it's technically weaker than the background noise, at the cost of a low data rate — typically well under 50 kbps. NB-IoT uses a narrowband LTE waveform instead, which moves more data per second (up to roughly 250 kbps on paper, though real-world throughput is usually much lower) but needs a cleaner signal to do it, since it doesn't spread nearly as aggressively.

Security: how each one keeps your data safe

LoRaWAN encrypts payloads with AES-128, split across two keys — a network session key that protects the link to your gateway, and a separate application session key that only your own application server can read, so no single party in the chain sees everything. Both are normally provisioned automatically when a device joins the network (OTAA), rather than hard-coded at the factory. NB-IoT leans on the same security model as your phone: authentication happens through the SIM itself, using the cellular network's built-in mutual-authentication scheme, with encryption over the air baked into the standard. Neither is the weak link in a typical deployment — the more common failure mode for both is a device shipped with default or reused keys, not the protocol itself.

3. Which signal travels further through walls, soil, and metal

The modulation difference above shows up physically the moment your device ends up somewhere hard to reach — underground, inside a metal enclosure, or deep in a basement.

It's not really about which technology uses a "lower" frequency — NB-IoT is frequently deployed on similarly low cellular bands (India's Airtel and Jio NB-IoT rollouts, for example, use 850–900 MHz), so the two aren't as far apart on raw frequency as it might seem. What actually differs is how each one claws back a signal that's been weakened by walls, soil, or metal: LoRaWAN's chirp spreading lets a single transmission be decoded well below the noise floor without being sent twice, while NB-IoT reaches a comparable depth by repeating the same message many times over — which works, but burns through battery a lot faster in the process.

There's also a distinctly Indian wrinkle worth knowing: India's LoRaWAN band (IN865) permits noticeably higher transmit power than Europe's equivalent band, which meaningfully extends real-world range and penetration for deployments here compared to the same hardware running under European rules.

4. Where each one actually gets used

Both technologies are already running at real scale, not just in pilots. As of December 2025, the LoRa Alliance reports 125 million LoRaWAN end devices deployed worldwide across more than 170 network operators, with smart metering, buildings, and cities as the leading categories. NB-IoT's footprint is harder to sum up in one number since it rides on existing carrier networks in dozens of countries rather than a single tracked ecosystem — but individual rollouts, like the case below, make the scale obvious on their own.

Specs matter, but the fastest way to know which technology fits your project is to look at what's already been built with each one.

Where LoRaWAN shows up

  • Smart agriculture: soil moisture, irrigation scheduling, and livestock tracking across a farm — one gateway can cover an entire property, and battery-powered sensors can run for years between site visits.
  • Private and campus utility metering: water and electricity meters for a housing society, industrial park, or university campus, wherever the deployer already controls the land the gateway sits on.
  • Industrial and factory monitoring: vibration, temperature, and conveyor-belt sensors across a plant floor, often in spots where metal enclosures or underground routing would otherwise block a cellular signal.
  • Smart buildings: leak detection, occupancy sensing, and equipment monitoring across a single building or campus.
  • Municipal infrastructure a city runs itself: streetlights, waste bins, and parking sensors, wherever the municipality is willing to install and maintain its own gateways.
Case study: multiple farms, single gateway
  • The challenge: continuous soil telemetry across 500+ acres of irregular farmland, with no Wi-Fi and no mains power available at any sensor location.
  • The build: ESP32-based sensor nodes paired with SX1276 LoRa radios, reading soil moisture, NPK, pH, EC, and temperature, running entirely on battery for the life of the deployment.
  • The network: a single central gateway, with relay routing between nodes so uneven terrain and long line-of-sight distances didn't leave any dead zones across the property.
  • The result: irrigation water use dropped 34% once watering decisions were driven by real-time soil-moisture thresholds instead of a fixed schedule.
Read the full write-up

Where NB-IoT shows up

  • National utility rollouts: in 2023, Bharti Airtel partnered with Secure Meters to deploy 1.3 million NB-IoT-powered smart electricity meters across Bihar — exactly the kind of project where meters are scattered across an enormous area and a private gateway network was never going to be practical.
  • City infrastructure spread across many municipalities: smart parking and street sensors for operators who don't want to run their own network — a single carrier SIM per sensor means no local infrastructure to maintain.
  • Stationary asset tracking: shipping containers, vending machines, and retail cabinets scattered across a state or country, wherever cellular coverage already exists.
  • Remote environmental and safety sensors: flood gauges, gas-leak detectors, and other infrastructure in genuinely isolated locations, where a wide-area carrier network makes more sense than building and maintaining a gateway.
  • Wearables and remote health monitoring: consumer or clinical devices that need to work anywhere a phone does, without the user ever needing to be near a gateway.

Notice the pattern: LoRaWAN clusters wherever you already control the site; NB-IoT spreads wherever a carrier's tower already reaches. That's really the whole decision, restated as examples instead of specs.

5. Key technical differences at a glance

Characteristic LoRaWAN NB-IoT
Spectrum Unlicensed ISM (865–867 MHz in India, 915 MHz in N. America) Licensed cellular band
Modulation Chirp Spread Spectrum (CSS) Narrowband LTE waveform
Typical open-air range 2–5 km urban, 10–20+ km rural line-of-sight (higher still under India's IN865 power rules) Roughly 1 km urban, up to ~10 km rural, commonly cited figures
Typical data rate 0.3–50 kbps Up to ~250 kbps on paper, often far lower in practice
Latency Seconds, longer with retries Roughly 1.6–10 seconds typical
Security AES-128, split network/application keys SIM-based cellular authentication
Best device profile Stationary, ultra-low-power sensor, many per site Stationary, deep-coverage sensor, few per site or spread wide

One nuance worth knowing: most LoRaWAN sensors use what's called Class A, which is where that "seconds, longer with retries" latency comes from. Mains-powered devices can instead run Class C, trading battery life for near-instant response.

6. Pros and cons at a glance

LoRaWAN

Pros: no recurring airtime cost, long battery life, strong penetration through walls and soil, full control over the network, and an open multi-vendor standard so you're not locked to one supplier.

Cons: low data rate, someone has to design and maintain the gateway network, and coverage is only as good as the gateways you've installed — there's no fallback to a carrier's existing towers.

NB-IoT

Pros: no gateway to design or maintain, coverage wherever the carrier already reaches, higher data rates than LoRaWAN, and the same cellular-grade authentication model your phone already relies on.

Cons: an ongoing subscription per device, dependency on one carrier's coverage and roadmap in your deployment region, and higher power draw than LoRaWAN once a device leans on repetition for deep coverage.

7. Cost: a useful tiebreaker, not the starting point

Once you know which technology actually fits — based on range, power, and how your devices are laid out — cost is worth one more look, mainly to confirm the decision or break a tie between two options that are both technically viable.

The two options carry fundamentally different cost shapes, and it's the shape that matters here more than any specific figure. LoRaWAN is almost entirely a one-time hardware purchase — a gateway, plus a small addition to each sensor's bill of materials — after which airtime is free for the life of the deployment. NB-IoT spreads cost out instead: no gateway to buy, but every device needs an ongoing subscription for as long as it's deployed, so the total bill grows with both device count and time.

As a rule of thumb: the more devices you deploy in one place, the more that upfront LoRaWAN hardware cost gets divided across, which usually tips the scales toward LoRaWAN. The fewer devices you have, and the further apart they're spread, the less that upfront gateway cost makes sense — and a small recurring per-device fee usually wins instead. Notice that this is really the same conclusion you'd reach from the application examples in Section 4, simply confirmed by the economics rather than driven by them.

8. Full comparison at a glance

Factor LoRaWAN NB-IoT
Network Your own private gateway Carrier's cellular towers
Ownership model You build and operate it You subscribe to it
Cost shape One-time hardware purchase Ongoing per-device subscription
Underground / indoor signal Strong, especially under India's higher-power IN865 rules Comparable via repetition, but drains battery faster
Setup complexity High (RF planning, network server) Low-to-moderate (carrier/SIM logistics)
Best fit Many devices, one site Few devices, spread far apart

9. How to choose

  • Choose LoRaWAN when: you have a dense cluster of stationary sensors in one area, want to avoid ongoing data costs, and can invest in the upfront network design.
  • Choose NB-IoT when: devices are stationary but scattered far apart, or the deployment needs the reach of an existing carrier network more than it needs a private one.

Frequently asked questions

No — only the gateway needs internet access. Sensors just need to be within radio range of the gateway; the gateway handles forwarding everything to the cloud.
LoRaWAN generally wins on pure battery life for the same reporting frequency, thanks to its shorter transmit time and simpler radio. NB-IoT can close much of that gap in good coverage using Power Saving Mode (PSM) and extended DRX — but in its deep-coverage mode, where it leans on repetition to match LoRaWAN's penetration, its battery life drops well below LoRaWAN's.
No — it operates in unlicensed spectrum, so there's no carrier contract or spectrum license required. You do still need to respect local regulations on transmit power and duty cycle.
To a growing but still limited degree. LoRaWAN Roaming, defined in the LoRaWAN Backend Interfaces specification, now works in more than 25 countries, letting a device roam onto a partner network the way a phone roams between carriers. It's newer and less universal than cellular roaming — so if your devices cross borders often, NB-IoT is still the safer default today.
Then this comparison doesn't really apply to you. Both LoRaWAN and NB-IoT are built around stationary sensors — a vehicle or a mobile tracker that needs to keep transmitting while moving between cell towers needs a technology built for handover, which is a different conversation from the one this guide is having.
Start small. A LoRaWAN evaluation kit — an indoor gateway plus one or two sensor nodes — typically costs a few hundred dollars and can be running end-to-end in an afternoon. For NB-IoT, request an IoT SIM from your carrier's developer program and pair it with an evaluation board that has a cellular module on it. Either way, prototype on the bench before committing to a site design — a week of hands-on testing usually settles the question faster than any amount of spec-reading.

The bottom line

There's no universally "better" technology — only a better technical fit for a given range, power budget, and device density, with cost and complexity acting as tiebreakers once that fit is clear. Stationary sensors clustered in one place point to LoRaWAN. Stationary sensors scattered wide apart point to NB-IoT.

LoRaWAN NB-IoT IoT Connectivity Embedded Systems Wireless Networks
Architectural validation

Scoping a deployment and want a second opinion?

Our Wireless RF & Network Integration Group at Semconix Technical R&D reviews architectures like this regularly — range, power budget, and site layout. Reach out and we'll help you get it right the first time.