Skip to content
RenoktaRenokta

LoRa vs NB-IoT: what is the difference?

LoRa/LoRaWAN runs in unlicensed spectrum on gateways you install; NB-IoT uses the mobile operator's cellular network. The difference shows in who owns the network, in coverage and in the cost model.

Request a demo

Renokta Ekibi ·

A pole-mounted LoRaWAN gateway with an antenna.
How to choose the technology
DevicelayoutCoveragecheckCost modelPilotmeasurementSelection
  1. 1. Device layoutCheck whether devices sit in one area or are scattered.
  2. 2. Coverage checkTest LoRaWAN and the operator signal at the target points on site.
  3. 3. Cost modelCompare the gateway investment with per-device subscriptions.
  4. 4. Pilot measurementVerify transmission interval and battery behaviour with a few devices.
  5. 5. SelectionPick the technology based on coverage, management preference and cost.

The main difference between LoRa and NB-IoT is who owns the network. With LoRaWAN you or a service provider install the gateways and work in unlicensed spectrum. With NB-IoT the device connects to a mobile operator's licensed cellular network. Both are low-power wide-area technologies that carry small amounts of data.

When choosing between them, the first question is not which is better but where your devices are and how often they will send data. As the answer becomes clear, the choice narrows by itself.

What are LoRa and NB-IoT?

LoRa is a radio modulation designed for long range and low power use, and LoRaWAN is the network protocol on top of it. NB-IoT (Narrowband IoT) is a technology defined within cellular standards for low-power devices.

For how LoRaWAN works in general, see our article on what LoRaWAN is. Here we only compare the two technologies.

NB-IoT runs inside the cellular network, so the device needs an operator subscription card. LoRaWAN devices, by contrast, connect to the platform through the network server they are registered with, without a subscription card. This difference affects both installation and operation.

Who owns the network and how is coverage provided?

In LoRaWAN, coverage depends on where your gateways are; in NB-IoT it depends on the operator's base stations. This changes the balance between control and dependence.

  • LoRaWAN: coverage can be extended with gateways you install; an extra gateway can be placed for hard spots such as basements or enclosed buildings.
  • NB-IoT: no gateway to install; coverage depends on the operator's infrastructure and the signal at that point.

Keep in mind that both technologies can suffer signal loss indoors. Whichever you choose, measure at the target points. Doing so before the investment decision lowers the cost of fixing problems later.

How does the cost model differ?

LoRaWAN has an upfront cost for gateways and installation, while a recurring per-device connection fee is mostly absent or low. NB-IoT has no gateway investment but needs an operator subscription for each device. For current tariffs, talk to the relevant providers.

When there are many devices concentrated in one area, the gateway investment is spread out. When devices are few and scattered, an operator subscription can be simpler.

When calculating total cost, consider installation, subscriptions, devices and maintenance together. Looking only at the initial investment can mislead; it is more sound to calculate a five-year running cost for both options under the same assumptions.

Which one fits which situation?

If your devices are concentrated in a building, plant or campus, LoRaWAN is usually the stronger candidate; if they are scattered across many locations, NB-IoT often is. The final decision should rest on a coverage test at the site.

  • Meter and sensor networks inside a site (for example water meters in a housing estate): a single LoRaWAN gateway can collect many devices.
  • Scattered, individual devices: NB-IoT can connect without installing a gateway.
  • Places where you want the network fully under your own control: a private LoRaWAN network can be built.
  • Scenarios with good operator coverage where you do not want to manage a network: NB-IoT may be simpler.

What should you check on data frequency and the device side?

Both technologies suit small data packets and infrequent transmission; they are not designed for video or continuous large data streams. Battery life and range depend on the device, the transmission interval and the environment, so verify them with the manufacturer's data and a pilot measurement.

Updates and device management also deserve attention. Whether a device can receive remote configuration or a firmware update differs by model in both technologies. If you want to reduce physical visits by the field team, ask about it during selection.

In the end the two are not rivals but tools for different situations. The right choice weighs device density, coverage, management preference and cost together. If you would like to work out which suits an on-site measurement such as water meters, you can reach us through our water consumption monitoring solution page.

Frequently asked questions

Are LoRa and LoRaWAN the same thing?
No. LoRa defines the physical radio layer, while LoRaWAN defines the network protocol and architecture that runs on top of it. In everyday speech the two are often used interchangeably.
Do I need to install my own gateway for NB-IoT?
No. NB-IoT devices connect to the operator's base stations. In return, the operator subscription and the coverage at that spot become the deciding factors.
Which gives longer battery life?
A general answer would not be accurate. Battery life depends on the device, transmission interval, signal conditions and the battery; rely on manufacturer data and a pilot measurement.
Which suits meters in a building basement?
Both can be tried, but coverage is critical indoors. With LoRaWAN a gateway can be placed in or near the basement; with NB-IoT the operator signal at that spot has to be checked.
Can I use both technologies in the same project?
Yes. LoRaWAN can serve devices inside a site and NB-IoT remote single points. The platform only needs to collect data from both sources in one place.

Let's plan the right solution for you, together.

Request a demo