LoRa vs. LoRaWAN: Understanding the Critical Differences
If you've spent any time reading about long-range IoT, you've almost certainly seen the terms LoRa and LoRaWAN used interchangeably. They are not the same thing, and confusing them leads to real engineering mistakes, from building a prototype that can never scale to a network, to buying hardware that doesn't support the features you actually need.
This article draws a clear line between the two.
What is LoRa? (The Physical Layer)
LoRa, short for Long Range, is a wireless modulation technique developed by Semtech. It operates at the physical layer (Layer 1 in the OSI model): it defines how bits get encoded into radio waves and transmitted over the air.
The underlying mechanism is Chirp Spread Spectrum (CSS) modulation. Rather than transmitting at a fixed frequency, a CSS signal sweeps across a range of frequencies in a chirp pattern. This has two important consequences:
- The signal is highly resistant to interference and multipath fading, a receiver can decode it even when it's 19.5 dB below the noise floor.
- The spreading factor (SF7 through SF12) trades speed for range: SF7 is the fastest with the shortest range; SF12 is the slowest with the longest range. You tune this parameter to match your deployment environment.
LoRa by itself is just a radio. It gives you a way to transmit bytes over a long distance using very little power. What it does not give you is:
- Any security, packets can be read by anyone with a compatible receiver
- Network management, no concept of devices joining a network, routing, or addressing
- A standardised protocol, you define your own packet format, which means your devices can only talk to other devices running your code
What is LoRaWAN? (The Network Protocol)
LoRaWAN is a MAC layer protocol (Layer 2) that sits on top of LoRa modulation. Where LoRa is a radio technique, LoRaWAN is a network specification maintained by the LoRa Alliance, a global consortium of companies that defines how devices connect to networks, how data is secured, and how networks scale.
LoRaWAN adds everything LoRa alone lacks:
- Standardised protocol: any LoRaWAN-certified device can join any LoRaWAN-compatible network, regardless of manufacturer
- Built-in security: AES-128 encryption at both network and application layers, with device authentication via OTAA or ABP
- Network server management: duplicate filtering, Adaptive Data Rate, roaming support, and over-the-air firmware updates
- Star-of-stars topology: end devices talk to gateways, gateways talk to a Network Server, no mesh routing required
Side-by-Side Comparison
LoRa (Radio Layer)
- Physical radio modulation (CSS)
- Defined by Semtech hardware
- No built-in security
- No network management
- Custom, proprietary packet format
- Point-to-point or custom topology
LoRaWAN (Network Protocol)
- MAC layer protocol built on LoRa
- Defined by the LoRa Alliance standard
- AES-128 dual-layer encryption
- Full network management (ADR, dedup, roaming)
- Standardised, interoperable packets
- Star-of-stars network architecture
When to Use LoRa Alone
Raw LoRa (without LoRaWAN) makes sense when:
- Simple point-to-point links: two nodes communicating directly with no infrastructure, a sensor sending data to a single base station under your control
- Prototyping or hardware bring-up: when you want to verify radio range and signal quality before committing to a full network stack
- Custom protocol control: when you have specific packet timing, frequency hopping, or acknowledgement requirements that LoRaWAN's spec doesn't accommodate
- Military or classified systems: where you implement your own security layer and cannot use a public standard
When to Use LoRaWAN
LoRaWAN is the right choice, and usually the only practical choice, when:
- Large-scale deployments: tens, hundreds, or thousands of devices that need to share network infrastructure
- Security is non-negotiable: enterprise environments, regulated industries, or any deployment where packet confidentiality matters
- Multi-vendor interoperability: using gateways from one vendor, sensors from another, and a cloud platform from a third
- Public network access: deploying on existing public LoRaWAN networks (The Things Network, Helium, Everynet) without managing your own gateways
Real-World Examples
LoRa alone: An engineer building an industrial sensor prototype that sends readings to a Raspberry Pi gateway 3 km away using a custom binary packet format. It works well, but it won't scale beyond that single link without redesigning the entire communication stack.
LoRaWAN: A smart agriculture company deploying 500 soil sensors across 10 farms. Sensors use off-the-shelf LoRaWAN modules, a commercial gateway covers each farm, and data arrives on a cloud dashboard via The Things Network. Any sensor can be swapped for a different vendor's device without changing the software.
The Short Version
LoRa is the radio. LoRaWAN is the network. For simple, small-scale projects or custom protocols, raw LoRa may suffice. For any real enterprise IoT deployment, one that needs security, scale, and interoperability, LoRaWAN is mandatory.
In the next article, we'll move from theory to practice and look at real-world LoRaWAN deployments across smart agriculture, smart cities, asset tracking, utilities, and healthcare.
Back to Blog