What are LoRa and LoRaWAN? A Developer Guide

Key Takeaways
- LoRa is the radio, LoRaWAN is the network. LoRa is Semtech's chirp spread spectrum modulation; LoRaWAN is the open networking protocol the LoRa Alliance defines on top of it.
- Long range, low power, small payloads. LoRaWAN reaches kilometers from a single gateway and supports multi-year battery life, at the cost of low data rates (~0.25–50 kbps in EU868) and limits on how often a device can transmit.
- Every LoRaWAN device needs gateway coverage, from a public network such as The Things Network or from gateways you install yourself.
- Blues Notecard for LoRa brings the same JSON API and Notehub integration used by cellular and WiFi Notecards, with ~8 µA idle draw.
What Is LoRaWAN?
LoRaWAN (Long Range Wide Area Network) is an open networking protocol that connects battery-powered devices to the internet over LoRa radio in unlicensed sub-GHz bands. The LoRa Alliance maintains the specification. A LoRaWAN device sends a small message, usually a few dozen bytes, to any gateway in range, often kilometers away. The gateway forwards it over the internet to a network server, which checks it, removes duplicates, and passes it on to your application.
LoRa, short for Long Range, is the radio technology underneath. It's a chirp spread spectrum modulation from Semtech that trades data rate for range and low power.
LoRaWAN suits devices that send small, infrequent readings from places without WiFi, where installing a gateway costs less than a cellular data plan for every device: soil moisture sensors, water meters, parking sensors, and building monitors. The tradeoffs are low data rates, strict limits on how often a device can transmit, and the need for gateway coverage wherever your devices are.
This guide covers how LoRaWAN networks work, the numbers that matter in each region, how to choose a network and a gateway, and how Blues Notecard for LoRa and Notehub fit in.
LoRa vs LoRaWAN
LoRa and LoRaWAN are often used interchangeably, but they're different layers of the stack. LoRa defines how bits travel over the air. LoRaWAN defines everything above that: how a device joins a network, how its messages are encrypted, which frequencies and data rates it may use in each region, and how gateways and servers relay its data.
| LoRa | LoRaWAN | |
|---|---|---|
| What it is | A radio modulation (the physical layer) | A networking protocol and network architecture |
| Defined by | Semtech, which owns the technology | The LoRa Alliance, as an open specification |
| What it specifies | Chirp spread spectrum, spreading factors, bandwidth | Device classes, joining, AES-128 encryption, regional data rates, adaptive data rate, gateway and server roles |
| Can it be used alone? | Yes, for point-to-point links between your own radios | No, it always runs over a radio layer: LoRa, plus FSK and LR-FHSS at some data rates |
To summarize: LoRa is the radio, LoRaWAN is the network.
A Brief History of LoRa and LoRaWAN
LoRa began in the early 2010s at Cycleo, a French startup. Semtech acquired Cycleo in 2012 and began commercializing the LoRa chipsets. In 2015, the LoRa Alliance formed to standardize LoRaWAN and promote its adoption. Its members range from chipset makers and device manufacturers to network operators and cloud providers.
How LoRaWAN Works
Network Architecture
LoRaWAN uses a star-of-stars topology. End devices talk to gateways over LoRa, and gateways talk to a network server over an ordinary internet connection.
- End devices are the sensors and actuators. A device doesn't connect to a particular gateway the way a phone attaches to a cell tower: it simply transmits, and every gateway in range hears the message.
- Gateways forward every LoRaWAN message they receive to the network server, and send the server's replies back to devices.
- The network server checks each message's integrity, discards the duplicates that arrive through several gateways, manages each device's data rate, and chooses the best gateway for any reply.
- The join server holds each device's root keys and handles devices joining the network.
- The application server decrypts the payload and delivers it to your application.
Because any gateway that hears a device can carry its message, adding gateways improves coverage and reliability without reconfiguring devices.
Joining a Network: OTAA and ABP
A device joins a LoRaWAN network in one of two ways. With over-the-air activation (OTAA), it sends a join request when it's deployed or reset, and the network answers with a join accept. The device and the network then each derive fresh session keys from the device's root key and the values in that exchange, so the session keys themselves never travel over the air (The Things Network). With activation by personalization (ABP), the session keys are programmed into the device ahead of time, which ties it to one network and skips the join. Because an ABP device keeps the same session keys for its whole life, the LoRaWAN specification recommends OTAA for higher-security applications (LoRaWAN L2 1.0.4).
Device Classes
Every LoRaWAN device implements Class A, and some add Class B or Class C. The class decides when a device listens for messages from the network, which sets both its power draw and how long a downlink waits to reach it (LoRaWAN L2 1.0.4).
| Class | When the device listens | Power | Typical use |
|---|---|---|---|
| A | Two short receive windows after each uplink it sends | Lowest | Battery-powered sensors that report readings and occasionally take a new setting |
| B | Class A windows, plus extra windows at times set by a beacon from the gateways | Moderate | Battery-powered devices that need commands on a known schedule |
| C | Almost continuously, except while transmitting | Highest | Mains-powered actuators that must respond quickly, such as lighting controls |
A message sent to a Class A device waits on the network server until the device next transmits, so a sensor that reports once an hour may take up to an hour to receive a new setting.
Data Rates, Spreading Factors, and Airtime
LoRa's main tradeoff is set by the spreading factor (SF), usually SF7 through SF12; the latest Regional Parameters also allow optional SF6 and SF5 rates. Each step up spreads every bit over twice as many chips, so the signal carries farther and survives more noise, but it takes about twice as long to send. At SF12, a LoRa receiver can decode a packet with a signal-to-noise ratio as low as -20 dB, well below the noise floor (Semtech).
Airtime grows quickly with the spreading factor. In EU868, a 10-byte payload (23 bytes on air with LoRaWAN's overhead) takes 61.7 ms at SF7 and 1.48 seconds at SF12, 24 times as long (The Things Network airtime calculator). Airtime is what regional duty-cycle rules and network fair-use policies limit, and it's most of what a transmission costs in battery.
LoRaWAN maps each combination of spreading factor and bandwidth to a numbered data rate (DR), and the numbering differs by region, as the next table shows. With adaptive data rate (ADR), the network server watches the signal quality of a stationary device's uplinks and moves a device with a strong signal to a faster data rate and lower transmit power, which saves battery and frees airtime for other devices.
Frequency Plans and Regional Limits
Because LoRaWAN runs in unlicensed sub-GHz bands, each region has its own plan, defined in the LoRa Alliance's Regional Parameters (RP002-1.0.5, October 2025). The two most common plans compare like this:
| EU868 | US915 | |
|---|---|---|
| Frequency band | 863–870 MHz | 902–928 MHz |
| Uplink channels | 3 default 125 kHz channels at 868.1, 868.3, and 868.5 MHz; the network can add more | 64 channels of 125 kHz (902.3–914.9 MHz) and 8 of 500 kHz |
| Required uplink data rates | DR0 (SF12, 250 bit/s) to DR5 (SF7, 5.47 kbps) | DR0 (SF10, 980 bit/s) to DR3 (SF7, 5.47 kbps), plus DR4 (SF8 at 500 kHz, 12.5 kbps) |
| Optional uplink data rates | DR6 (SF7 at 250 kHz, 11 kbps), DR7 (FSK, 50 kbps), and, since RP002-1.0.5, DR12 (SF6, 9.375 kbps) and DR13 (SF5, 15.625 kbps) | Since RP002-1.0.5, DR7 (SF6, 9.375 kbps) and DR8 (SF5, 15.625 kbps) |
| Maximum application payload | 51 bytes at DR0–DR2, 115 at DR3, 222 at DR4–DR7 | 11 bytes at DR0, 53 at DR1, 125 at DR2, 222 at DR3–DR4 |
| Transmit limit | Duty cycle: 1% in the default channels' sub-band | Dwell time: 400 ms per uplink on the 125 kHz channels |
| Default maximum transmit power | +16 dBm EIRP | +30 dBm conducted |
The payload sizes assume a network that may use repeaters; without one, the largest data rates allow up to 242 bytes.
A 1% duty cycle means a device that transmits for 1 second on a sub-band must wait 99 seconds before using it again. The European limits come from ETSI EN 300 220-2: 1% in the 868.0–868.6 MHz sub-band that holds the default channels, 0.1% in 868.7–869.2 MHz, and 10% in 869.4–869.65 MHz, where the default downlink (RX2) channel sits at 869.525 MHz. ETSI also allows "polite spectrum access," a listen-before-talk scheme, in place of the duty cycle (ETSI EN 300 220-2; The Things Network).
US915 has no duty cycle, but the FCC's 400 ms dwell time rules out SF11 and SF12 on the 125 kHz channels. That's why US915's slowest uplink data rate is SF10 and why DR0 carries only 11 bytes.
Other regions have their own plans, including AS923 (four variants within 915–928 MHz for different countries), AU915 (915–928 MHz), IN865 (865–868 MHz), KR920 (920.9–923.3 MHz), and RU864 (864–870 MHz).
Since 2020, the Regional Parameters have also defined LR-FHSS, an uplink-only frequency-hopping modulation at 162–325 bit/s for EU868, US915, and AU915. It's optional, and it's designed to add network capacity and to let devices reach satellites directly (LoRa Alliance).
Range
LoRaWAN range depends on terrain, antenna height, data rate, and how deep indoors a device sits. Semtech puts typical range at up to 5 km in urban areas and 15 km or more in rural areas with line of sight. Its figures for US915 uplinks also show the effect of the spreading factor, from about 2 km at SF7 to 8 km at SF10 (Semtech AN1200.86).
LoRaWAN Networks: Public, Community, and Private
A LoRaWAN device needs a network server as well as gateways, and there are three common ways to get both.
The Things Network is a free, community-run network built on The Things Stack, with gateways contributed by its users around the world. Its fair use policy limits each device to 30 seconds of uplink airtime and 10 downlink messages per day (The Things Network). In EU868, that's about 486 ten-byte uplinks a day at SF7, or about 20 at SF12. Other public networks work differently: Helium, for example, is a decentralized network whose gateways are run by individuals.
Some telecom operators and IoT companies also run LoRaWAN networks as a commercial service, with coverage maps and service agreements.
For full control, you can run a private network: you install your own gateways and use a network server, either hosted, such as The Things Stack, or self-hosted, such as the open-source ChirpStack. The Things Network's fair use limits don't apply to a private network, but your region's duty-cycle or dwell-time rules still do.
Networks can also exchange traffic, so a device registered on one network can be heard by another's gateways. The Things Stack does this through Packet Broker, which is how Notecard for LoRa traffic from your own gateways reaches Notehub.
Choosing a LoRaWAN Gateway
The gateway is the one piece of infrastructure a LoRaWAN deployment needs, and a few things decide which one fits:
- It has to support your region's frequency plan, such as EU868 or US915, and so do your devices.
- In US915, channels need a plan too. Many gateways receive on 8 channels at a time, so with 64 uplink channels to choose from, devices and the network agree on a block of 8 called a sub-band. The Things Network uses sub-band 2: channels 8–15, plus 500 kHz channel 65 (The Things Network).
- Placement matters more than anything else. A gateway on a rooftop or mast covers far more ground than one on a desk, and outdoor gateways are weatherproof and take external antennas.
- Backhaul can be Ethernet, WiFi, or cellular. Cellular backhaul lets you put a gateway where there's no wired internet, such as a field or a construction site.
- The gateway has to work with your network server. The Things Stack, for example, lists the gateways it supports with setup steps for each.
For Notecard for LoRa, the gateway must be registered on The Things Stack, as the Notecard for LoRa section below explains.
LoRaWAN vs Cellular, Satellite, and WiFi
LoRaWAN fills a specific niche: long range, low power, and fixed sites where you control or share the gateway coverage. Here's how it compares to the other major wireless IoT technologies:
| Technology | Range | Notecard Idle Current | Data Rate | Infrastructure | Best For |
|---|---|---|---|---|---|
| Cellular LTE Cat-1, Cat-1 bis, LTE-M, NB-IoT | Global (wherever cellular coverage exists) | ~9 µA @ 5V (Notecard Cellular); ~18 µA @ 5V (Cell+WiFi) | Peak rates from ~127 kbps (NB-IoT) to ~10 Mbps (LTE Cat-1) | Carrier networks (pre-existing) | Mobile, outdoor, or geographically distributed deployments |
| Satellite Skylo NTN, Iridium | Iridium: global, including oceans and both poles. Skylo: its supported regions | ~4 µA @ 5V for Starnote for Skylo, plus its host Notecard | Small packets: up to 256 bytes (Skylo) or 10,000 bytes (Iridium) | Skylo (existing GEO satellites); Iridium (66-satellite LEO constellation) | Remote, off-grid, or cellular-dark locations; fallback for hybrid deployments |
| LoRaWAN 868 MHz EU, 915 MHz US | Up to ~5 km in cities; up to 15 km in rural line of sight | ~8 µA on VIO (Notecard for LoRa) | ~0.25–50 kbps in EU868 (the 50 kbps rate uses FSK) | LoRaWAN gateway on The Things Stack | Dense, low-power sensor networks in a fixed geographic area |
| WiFi 2.4 GHz 802.11b/g/n | ~20 m indoors (less through walls and congestion) | ~18 µA @ 5V (Notecard Cell+WiFi) | Mbps class, the highest of the four | WiFi access point (pre-existing) | Indoor, high-bandwidth, infrastructure-present products |
Why LoRa and LoRaWAN for the IoT?
LoRaWAN works best when devices send small packets over long distances on minimal power, as in agriculture, environmental monitoring, utility metering, and smart buildings.
The spectrum is license-free, and there are no SIM cards or per-device data plans, so the main costs are the devices, the gateways, and the network server. For a dense deployment in one area, such as a farm, a campus, or a factory, a few gateways can cover every device. LoRa also holds up in noisy RF environments, because its chirp spread spectrum modulation can recover signals below the noise floor.
The tradeoff is coverage. A LoRaWAN device only works where there's a gateway it can reach, so devices that move across a region, or that sit somewhere you can't install or reach a gateway, are usually better served by cellular IoT or satellite IoT.
Notecard for LoRa
At Blues, our Notecard product line exists to connect any device to any cloud, using any MCU or language, with as little friction as possible. We're best known for our prepaid cellular IoT Notecards, and Notecard for LoRa brings the same approach to LoRaWAN.
Blues Notecard for LoRa is a 30 x 35 mm system-on-module built around ST's STM32WLE5, which combines a microcontroller and a LoRa radio on one chip.
| Front of Notecard for LoRa | Back of Notecard for LoRa |
|---|---|
![]() | ![]() |
Like its cellular and WiFi siblings, it has:
- The same JSON-based Notecard API, so host firmware written for one Notecard works with the others.
- A low idle draw of about 8 µA on its 3.3V logic supply.
- LoRaWAN security, with device provisioning handled by Blues.
- Synchronization with any cloud endpoint through Blues Notehub.
Because LoRaWAN payloads are so small, every Note sent from Notecard for LoRa must use a Note Template, which packs your JSON into a compact binary format.
Choosing a Notecard for LoRa
Notecard for LoRa comes in two frequency versions. Blues sets the frequency during provisioning, so order the one that matches where your devices will run.
| Notecard | Frequency plan | Where to use it | Form factors |
|---|---|---|---|
| NOTE-LWUS | US915 | United States | Castellated-edge v2.1 or M.2 v1.4 |
| NOTE-LWEU | EU868 | Europe | Castellated-edge v2.1 or M.2 v1.4 |
Both versions are available from the Blues store.
Notecard with a LoRaWAN Gateway: The End-to-End Picture
Notecard for LoRa works with any LoRaWAN gateway provisioned on The Things Stack, including the public gateways of The Things Network. The simplest path is the Blues Starter Kit for LoRaWAN, whose Blues Indoor LoRaWAN Gateway (a RAKwireless WisGate Edge Lite 2) ships preconfigured on Blues' Things Stack tenant and connects over Ethernet or WiFi. With it, Blues manages every step from the network server to Notehub.
If you bring your own gateway, you register it on The Things Stack and enable Packet Broker so that Notecard traffic reaches the application server Blues runs for Notehub. Connecting to a LoRaWAN Gateway covers both setups.

The Role of Notehub in LoRa Deployments
Notehub is Blues' secure cloud service, a thin layer between your devices and your own cloud. With Notecard for LoRa, as with every Notecard, Notehub lets you:
- Receive Notes (JSON payloads) from your devices.
- Configure Notecards remotely with environment variables.
- Route device data to AWS, Azure, Google Cloud, or your own HTTPS or MQTT endpoints.
Because Notehub is a hosted service, you don't need to provision, secure, or maintain your own LoRaWAN application server, and your LoRa devices show up in the same projects, routes, and fleets as your cellular and WiFi devices.
Developer Walkthrough of Notecard for LoRa
Here's what the first 10 minutes with Blues and LoRaWAN look like for an embedded developer.
-
Mount Notecard for LoRa on a Notecarrier that matches your preferred form factor, such as a Notecarrier A, a Notecarrier Pi for Raspberry Pi, or a Notecarrier F for an Adafruit Feather-compatible host MCU.
-
Power on the Blues Indoor LoRaWAN Gateway and follow the quickstart to connect it to your local network. The gateway is already registered with The Things Stack and its LoRaWAN credentials are configured, so you only need to associate your Notecard with a Notehub project, as with any other Notecard.
-
Once Notecard for LoRa powers on, it joins the network, and you can start sending Notes to Notehub through the gateway. In Notehub, you can inspect incoming data, route it to AWS, Azure, Datacake, or any HTTPS or MQTT endpoint, and send environment variables back to the device.
Architectural Patterns
Blues supports several patterns with Notecard for LoRa and the rest of the Notecard family:
- Star topology, with many Notecard for LoRa devices reporting through one or a few local gateways.
- Edge aggregation, where a host MCU analyzes readings locally and sends only summaries, which keeps airtime low.
- Mixed fleets that use Notecard for LoRa where you have gateway coverage and a cellular Notecard everywhere else, with the same host firmware and the same Notehub project for both.
Frequently Asked Questions
What is the difference between LoRa and LoRaWAN?
LoRa is the radio: a chirp spread spectrum modulation from Semtech that trades data rate for long range and low power. LoRaWAN is the open networking protocol the LoRa Alliance defines on top of it, covering how devices join a network, how their messages are encrypted, which frequencies and data rates they use in each region, and how gateways relay data to a network server. In short: LoRa is the radio, LoRaWAN is the network.
What does LoRaWAN stand for?
LoRaWAN stands for Long Range Wide Area Network. It's a low-power wide-area network (LPWAN) protocol, maintained by the LoRa Alliance, that runs over LoRa radio in unlicensed sub-GHz bands.
How far can LoRaWAN reach?
Semtech puts typical LoRaWAN range at up to 5 km in urban areas and 15 km or more in rural areas with line of sight (Semtech AN1200.86). Real range depends on terrain, gateway height, how deep indoors a device sits, and the spreading factor: higher spreading factors reach farther but take longer to transmit.
What frequencies does LoRaWAN use?
LoRaWAN uses unlicensed sub-GHz bands that differ by region: 863–870 MHz for EU868 in Europe, 902–928 MHz for US915 in North America, and other plans such as AS923, AU915, IN865, and KR920 elsewhere, all defined in the LoRa Alliance's Regional Parameters. Each region also limits transmissions: EU868 devices observe a 1% duty cycle on the default channels, and US915 devices a 400 ms dwell time per uplink.
How much data can a LoRaWAN device send?
Not much, by design. The largest application payload ranges from 51 bytes at the slowest EU868 data rates (11 bytes in US915) to 222 bytes at the fastest. In EU868, the LoRa data rates every device must support run from 250 bit/s (SF12) to 5.47 kbps (SF7), and optional rates reach 15.625 kbps for LoRa (SF5) and 50 kbps for FSK. On The Things Network, a fair use policy also limits each device to 30 seconds of uplink airtime and 10 downlinks per day (The Things Network), which is about 486 ten-byte uplinks a day at SF7 in EU868.
Do I need my own LoRaWAN gateway?
Not if a network already covers your devices. You can use a public network such as The Things Network, or install your own gateway where there's no coverage. Notecard for LoRa works with gateways on The Things Stack, including The Things Network's public gateways, and Blues offers an Indoor LoRaWAN Gateway that ships preconfigured and works out of the box with Notecard for LoRa.
What is the difference between OTAA and ABP?
They're the two ways a LoRaWAN device activates on a network. With over-the-air activation (OTAA), the device sends a join request, and after the network's join accept, the device and the network each derive fresh session keys, so the keys never travel over the air (The Things Network). With activation by personalization (ABP), the session keys are programmed in ahead of time and never change, which ties the device to one network. The LoRaWAN specification recommends OTAA for higher-security applications (LoRaWAN L2 1.0.4).
What are LoRaWAN device classes?
Class A devices listen for downlinks only in two short windows after each uplink, which uses the least power; every LoRaWAN device supports Class A. Class B devices add receive windows at times scheduled by a beacon from the gateways, for predictable downlink timing. Class C devices listen almost continuously, drawing the most power but receiving commands with little delay.
How long can a LoRaWAN device run on a battery?
Years, for a Class A device that sends a few small messages a day. Battery life depends mostly on how often the device transmits and at what spreading factor, since a message at SF12 takes about 24 times the airtime of the same message at SF7. Notecard for LoRa idles at about 8 µA on its 3.3V logic supply.
Is LoRaWAN free to use?
The spectrum is: LoRaWAN runs in unlicensed bands, so there's no carrier or per-device data plan. You still need gateway coverage and a network server. The Things Network is free with a fair use policy, commercial networks charge for service, and a private network costs you the gateways and the network server, whether hosted or self-hosted.
Can I use the same firmware across cellular, WiFi, and LoRa Notecards?
Mostly, yes. Every Notecard uses the same JSON API, so host firmware written for Notecard Cellular or Notecard Cell+WiFi carries over to Notecard for LoRa with few changes. The main difference is that every Note sent over LoRa must use a Note Template to fit LoRaWAN's small payloads.
Conclusion and Next Steps
LoRaWAN gives you long range and multi-year battery life for devices that send small, infrequent messages, in exchange for low data rates and the need for gateway coverage. With Notecard for LoRa, the Blues Indoor LoRaWAN Gateway, and Notehub, you write the same JSON requests you would for any Notecard, and Blues handles provisioning, the network path, and routing to your cloud.
Because every Notecard shares the same API, you can also mix LoRa with cellular or WiFi in one product, or switch between them, without rewriting your host firmware.
Start building with a Blues Starter Kit for LoRaWAN and the LoRaWAN quickstart.

