What Is LoRaWAN®? How It Works, and When to Use It

Three hundred soil moisture probes across forty square kilometres of farmland. None near a power outlet. Nobody is driving out to swap batteries, because at that count it becomes a full-time job. WiFi dies at the edge of the first field, and a SIM in every probe would cost more than the probes did. That combination is ordinary in agriculture, utilities and industry, and it is what LoRaWAN was built for: a few dozen bytes, a few times a day, over kilometres, on batteries that last years. So what is LoRaWAN, and when is it the right choice?

What Is LoRaWAN?

LoRaWAN^® is an open low-power wide-area network (LPWAN) protocol. It lets small battery-powered sensors send short messages several kilometres to a gateway, which passes them to a network server and on to your application. The trade is deliberate: almost no bandwidth, in return for range and years of battery life.

That trade is the whole idea. You are not streaming video over LoRaWAN. You are sending a temperature, a fill level, or a door state, a few dozen bytes at a time, from somewhere a power outlet and a WiFi router will never reach.

LoRa^® and LoRaWAN Are Not the Same Thing

Almost every LoRaWAN misconception starts here.

LoRa^® is the radio. A physical-layer modulation technique, built so a signal survives the distance and weakness that would defeat most radios. On its own it gives you a raw link between two of them. Nothing more.

LoRaWAN^® is the network built on top of that radio. It handles joining, encryption and routing. It also settles a question a bare radio cannot answer: when three gateways all hear the same device, which one replies?

You can use LoRa without LoRaWAN. Point-to-point LoRa, often written LoRa P2P, sends raw payloads directly between two radios with no protocol above them. In the RAKwireless WisDuo walkthrough, setting a module up for LoRa P2P takes about two AT commands, while a LoRaWAN setup takes around eight. Those six extra commands are the network: the device identity, the region, the join procedure, and the security keys.

Control both ends and want the simplest link possible? Use P2P. Once you need many devices, managed identity and a route to the cloud, you need the protocol.

How Does LoRaWAN Work? The Four Parts

Answering what is LoRaWAN in practical terms means looking at four pieces. Every LoRaWAN network, from a single building to a national deployment, is built from the same ones.

1. The end device

The end device is the sensor or actuator in the field, usually a microcontroller paired with a LoRa transceiver on one stamp-sized module. RAK's WisDuo modules run from 1.8 to 3.6 volts, low enough to sit directly on a small battery, and hold their configuration in flash, so settings survive a reboot, a power cycle, and a firmware update.

Devices come in three classes, and the choice sets battery life.

2. The gateway

A gateway is the antenna-equipped box that hears whatever devices are transmitting nearby and passes their packets onward. It does not interpret your data. It is a bridge between the radio world and the internet.

Not all gateways listen the same way. A half-duplex unit transmits or receives, never both at once. Full-duplex models do both, which cuts latency on busy networks. They also differ in backhaul, the internet connection reaching the server. Multi-backhaul models let you set Ethernet as primary with WiFi or cellular as automatic fallback, returning to primary on recovery, so a cut cable does not mean lost data.

3. The network server

The network server is the brain. It deduplicates packets when several gateways hear the same device, checks security, manages join requests, adapts data rates, and decides which gateway sends any reply. Gateways reach it in one of three modes: Basic Station, Packet Forwarder, or a network server hosted on the gateway itself. That last option matters for small deployments, letting you run a complete network without a third-party subscription.

4. The application

The application is where data finally becomes useful. A dashboard, a maintenance ticket, a row in a database. It receives decoded payloads from the network server, usually over MQTT or a webhook.

What Is the Range of a LoRaWAN Network?

Range depends on terrain, antenna placement, and data rate, so treat any single number with suspicion. Open rural line of sight is measured in kilometres, while dense urban environments with walls and interference are considerably shorter. Height helps more than power: a rooftop gateway routinely outperforms a stronger radio at ground level.

Coverage scales differently than people expect. Because gateways listen rather than pair, one new gateway extends coverage for every device in range.

When Should You Use LoRaWAN Instead of WiFi or Cellular?

The decision comes down to four questions. How far from infrastructure are the devices? How long must they run without service? How much data does each message carry? And who pays the recurring bill?

Choose LoRaWAN for many sensors spread over a campus, farm, or city, sending small readings, where you want to own the infrastructure rather than pay per device per month. Choose WiFi when devices sit near power and need real bandwidth. Choose cellular when assets move across regions with no gateway coverage.

A peer-to-peer mesh such as Meshtastic solves a different problem. Nodes relay for each other with no central server, which suits off-grid communication between people. LoRaWAN is a star topology built around managed infrastructure, suiting fleets of sensors that feed a system of record.

What Do You Need to Build a LoRaWAN Network?

Less than most people assume. You need end devices, at least one gateway, a network server, and somewhere for the data to land.

The device side is where teams over-engineer. A module containing both the microcontroller and the radio removes most of the RF work, and integration can be as simple as power, ground, and a serial connection to a host controller. Open-source firmware frameworks such as RUI3 handle the LoRaWAN stack, so your engineers write sensor logic instead of protocol code.

If you are scoping hardware, start with RAK's WisGate Edge gateways and the WisDuo module range, and read Things to Consider When Picking a LoRaWAN Gateway before committing. For the specification itself, the LoRa Alliance maintains the standard.

Frequently Asked Questions

What is LoRaWAN?

LoRaWAN is an open LPWAN protocol that connects battery-powered sensors to the internet over long distances using small, infrequent messages. It defines device identity, encryption, and routing on top of the LoRa radio.

What is the difference between LoRa and LoRaWAN?

One is the radio, the other is the network. LoRa carries the bits over distance. LoRaWAN decides what happens to them once they land: joining, security, routing to a server.

How far can a LoRaWAN device transmit?

Kilometres in open rural conditions. Considerably less in a dense city, where walls and interference cut it down. Gateway height matters more than transmit power.

Is LoRaWAN free to use?

Partly. The specification is open and the spectrum unlicensed, so nobody bills you per device. Hardware still costs money, and so does a hosted network server if you choose not to run your own.

Can LoRaWAN work without internet?

Yes. A gateway running a built-in network server can operate a local network with no external connection, which suits isolated sites.

How many devices can one gateway handle?

There is no fixed number. It comes down to channel count, how often devices report, and at what data rate. Sensors sending twice a day scale much further than ones sending every minute.

Do I need to write LoRaWAN protocol code myself?

No. Modules with AT command interfaces or an API such as RUI3 implement the stack for you, so you write application logic instead.

TL;DR

• What is LoRaWAN: an open low-power protocol for sending small sensor messages over kilometres, on batteries that last years.
• LoRa is the radio, LoRaWAN is the network. Keep the two separate.
• Four parts: end device, gateway, network server, application.
• Choose it when you have many low-bandwidth sensors spread over a wide area and want to own the infrastructure.
• Do not choose it when devices need real bandwidth or sit next to power and WiFi.