LoRaWAN 101: The Complete Glossary & FAQ Guide

LoRaWAN (Long Range Wide Area Network) is a wireless protocol built specifically for low-power, low-bandwidth IoT devices that need to send small amounts of data over long distances. Wi-Fi and Bluetooth trade range for speed - great for streaming video or audio, but limited to a single building and needing frequent recharging. LoRaWAN does the opposite: it sends only a few bytes at a time, but in exchange gets kilometres of range and years of battery life, with no SIM card or cellular contract required.

A LoRaWAN network has three parts. End devices - sensors or trackers - send small encrypted packets over the LoRa radio signal. Any gateway within range picks up that signal and forwards it, unaltered, to the internet. A LoRaWAN Network Server then checks the packet is genuine, discards duplicates if more than one gateway heard it, and passes the decoded data to an application, such as Trackpac's dashboard. For a full step-by-step walkthrough with diagrams, see our Ultimate Guide to LoRaWAN Asset Tracking below.

In dense urban environments, where buildings and other structures interfere with the signal, a single gateway typically covers roughly 2-10 km. In open rural terrain with clear line-of-sight, LoRaWAN can reach considerably further - tens of kilometres has been demonstrated in ideal conditions. Real-world range on any given site depends heavily on gateway height, antenna choice, and obstacles, so a site survey is the only reliable way to know what to expect.

It depends on how often the device reports and what sensors it runs, but LoRaWAN's low power draw means devices commonly last many months to several years on a single battery or coin cell. Some ruggedised asset trackers reporting infrequently can run for a decade or more without a change. This is one of the main reasons LoRaWAN gets chosen over Wi-Fi or cellular for remote or hard-to-reach sensors.

Yes. LoRa's sub-GHz radio signal penetrates walls, floors, and some metal structures noticeably better than the higher-frequency signals Wi-Fi and Bluetooth use. That said, thick concrete, dense metal racking, or basement locations can still weaken the signal, so devices deep inside large buildings sometimes need a nearby or dedicated indoor gateway to guarantee reliable coverage.

LoRaWAN defines three device classes that trade power consumption for how quickly the network can send data back down to the device. Class A is the default that every device must support: it's the most power-efficient, opening just two brief listening windows after each transmission. Class B adds scheduled listening windows synced to a network beacon, so the network can reach the device on a predictable timetable for a modest extra power cost. Class C devices listen almost continuously and can be reached at any time, but need a much larger power supply - so it's typically used on mains-powered devices rather than battery-run ones.

In the UK and the rest of Europe, LoRaWAN runs on the EU868 band, centred around 868 MHz, in license-free ISM spectrum. In the US and Canada, it uses the US915 band (902-928 MHz) instead. Other regions have their own plans too - AU915 in Australia, AS923 across much of Asia - so a device bought for one region generally won't work in another without different RF hardware and firmware.

A public LoRaWAN network - like The Things Network's community tier, or a regional operator's network - is shared infrastructure that any device can, in principle, connect to, similar to how any phone can use a mobile network. A private network uses gateways your organisation owns or leases exclusively, giving guaranteed coverage, guaranteed capacity, and full control over where the data goes. Many real deployments use a mix: private gateways where coverage is business-critical, public network coverage as a fallback everywhere else.

Not always. If a public or community network already covers your site, you may not need one at all. But for guaranteed indoor coverage, remote locations, or any deployment where "the signal might be there" isn't good enough, installing one or more private gateways removes that uncertainty entirely.

A single indoor gateway typically costs somewhere in the low hundreds of pounds, with outdoor, industrial-grade units costing more. Hardware is usually the smaller part of the bill, though - installation, antennas, mounting, backhaul, and running a network server all add to the total, and costs scale with how many sites and how much coverage redundancy you need. Because this varies so much project to project, it's worth getting a proper site-specific scope rather than working from a rule of thumb.

The LoRaWAN Network Server (LNS) is the software layer that sits between the gateways and the application. It authenticates devices, filters out duplicate packets picked up by more than one gateway, manages Adaptive Data Rate (which balances speed against range and power automatically), and routes decoded data on to whichever application needs it - Trackpac's dashboard, in our case. Popular LNS options include ChirpStack, The Things Stack, and AWS IoT Core for LoRaWAN.

There's no fixed number - it depends on how often each device reports, how big its payload is, and what data rate it uses. As a rough guide, commercial gateways are commonly rated to handle from several hundred up to a couple of thousand devices reporting periodically, though the practical ceiling can be much higher for infrequent, small messages and lower for frequent, data-heavy ones. For a large rollout, it's worth checking expected traffic against a specific gateway's rated capacity rather than assuming.

Yes. Every LoRaWAN message is encrypted with AES-128, using two separate keys generated when a device joins the network: a Network Session Key that protects the network layer, and an Application Session Key that only your application server can decrypt. That separation means a network operator - even a public one - can route your data without being able to read the payload itself.

It depends what you value most. NB-IoT and LTE-M run on licensed cellular spectrum, so you get a SIM and a subscription but also near-nationwide coverage from a carrier rather than needing to install anything yourself. LoRaWAN generally wins on running cost (no recurring per-device SIM fee) and often on battery life, but needs gateway coverage in place first. For assets that roam nationwide - vehicles crossing the whole country, for instance - cellular IoT is often simpler; for site-based or regional tracking, LoRaWAN's flat running cost usually works out cheaper at scale.

Amazon Sidewalk is a shared network built by pooling the Bluetooth and Wi-Fi range of millions of consumer Echo and Ring devices to relay small amounts of data. It's a clever idea, but as of 2026 it's only available in the US, with Canada and Mexico added in early 2026 - it isn't available in the UK or Europe, and Amazon hasn't given a firm timeline for when, or whether, that will change. LoRaWAN, by contrast, is an open global standard that any business can deploy dedicated coverage for anywhere, which matters if you need reliable, business-critical connectivity rather than best-effort coverage riding on somebody else's home network.

A sensor platform like Trackpac is built to get specific classes of LoRaWAN sensors and trackers online fast, with dashboards, alerts, and geofencing ready out of the box and no infrastructure to configure. A general-purpose IoT application platform like ThingsBoard or TagoIO is a much broader toolkit for building custom dashboards, rules, and integrations across many device types and protocols, but it typically needs more setup time and in-house technical know-how to reach the same result.