LoRaWAN sits in an interesting niche in the IoT connectivity stack. It’s not as fast as LTE-M. It’s not as standardised as NB-IoT. But it covers kilometres, runs on a coin cell for years, costs nothing per message, and you can deploy your own private network in a weekend. For the right use cases, nothing else comes close.

If you’ve been looking at IoT deployments where you need to cover large outdoor areas, run sensors with minimal maintenance, and not pay per-device monthly fees indefinitely, LoRaWAN deserves a serious look. Here’s what you need to know about where it stands in 2026 and how to get a deployment running.

What LoRaWAN Actually Delivers

LoRa (Long Range) is a radio modulation technique developed by Semtech. LoRaWAN is the MAC layer protocol and network architecture that sits on top of it. They’re often conflated but it’s worth separating them: LoRa is the radio, LoRaWAN is the network specification that defines how devices join networks, how messages are routed, and how security works.

In practice, a LoRaWAN device sends small packets of data — typically 10 to 50 bytes — to a gateway, which forwards them to a network server over Ethernet, WiFi, or cellular backhaul. Gateways can cover anywhere from 2km in dense urban environments to 15km+ in open rural terrain, which is what makes LoRaWAN practical for deployments where running Ethernet or putting a cellular SIM in every sensor isn’t viable.

What you give up: bandwidth. LoRaWAN isn’t suited to anything requiring high data rates. A soil moisture reading, a GPS coordinate, a temperature and humidity value, a door open/close event — all fine. Streaming video, real-time audio, or anything requiring sub-second latency — not this technology.

The power consumption numbers are genuinely impressive. A LoRaWAN sensor sending a reading every fifteen minutes can last four to ten years on a standard AA battery, depending on the spreading factor and payload size. That changes the economics of large-scale sensor deployments significantly.

Where LoRaWAN Beats NB-IoT and LTE-M

The cellular LPWAN standards — NB-IoT and LTE-M — are genuinely good for many use cases. They’ve got better latency, more reliable coverage in urban environments, and the network infrastructure already exists. But they come with per-device SIM and connectivity costs, and they depend on carrier coverage that may not reach every corner of a rural estate or an underground car park.

LoRaWAN’s advantages are: zero per-message cost on private networks, the ability to deploy gateways wherever you need them, and coverage in areas where cellular doesn’t reach. It also handles indoor penetration reasonably well — multi-story buildings, basements, industrial premises with metal walls.

The practical decision point is usually whether you control the environment. For a factory floor, a farm, a logistics depot, or a smart building where you can put up your own gateways, LoRaWAN often wins. For tracking assets that move across wide geographic areas without a predictable path — vehicles on public roads, shipping containers across country — cellular LPWAN makes more sense because the coverage already exists.

The Two Deployment Paths: Public vs Private

The Things Network (TTN) / Helium let you piggyback on community-run infrastructure. If there’s TTN coverage in your area (check map.thethingsnetwork.org), you can deploy sensors and have them talk to the public network for free. TTN operates a fair-use policy rather than hard limits, making it ideal for pilots and smaller deployments. Coverage in UK cities is generally good; rural coverage depends entirely on whether volunteers have put up gateways.

Private LoRaWAN with ChirpStack is the production path for anything serious. ChirpStack is an open-source LoRaWAN network server that runs on your own infrastructure — a Raspberry Pi for a small deployment, a proper server or cloud VM for larger ones. You pair it with LoRa gateways (RAK Wireless, Dragino, and Kerlink all make solid options in the £150-£800 range) and your own MQTT broker or application server.

Running ChirpStack gives you full control: you own the data, you choose the data retention policy, you set the security parameters, and you’re not dependent on a third party’s uptime. For anything regulated, anything involving sensitive data, or anything critical, private is the right call.

# docker-compose.yml for ChirpStack stack
version: "3"
services:
  chirpstack:
    image: chirpstack/chirpstack:4
    environment:
      - MQTT_BROKER_URI=tcp://mosquitto:1883
      - POSTGRES_DSN=postgres://chirpstack:password@postgres/chirpstack
    ports:
      - "8080:8080"
  
  chirpstack-gateway-bridge:
    image: chirpstack/chirpstack-gateway-bridge:4
    ports:
      - "1700:1700/udp"
  
  mosquitto:
    image: eclipse-mosquitto:2
    ports:
      - "1883:1883"
  
  postgres:
    image: postgres:15
    environment:
      POSTGRES_PASSWORD: password
      POSTGRES_DB: chirpstack

ChirpStack v4, the current stable release, added multi-region support (you can run LoRaWAN EU868, US915, and AU915 from a single instance), improved device management, and better integration with external systems via gRPC.

Real Deployments Worth Studying

Smart agriculture is probably the strongest current use case. Soil moisture sensors, weather stations, cattle tracking, irrigation control, and crop monitoring across hundreds of acres — all of this works well with LoRaWAN. A single gateway at the farm centre covers the entire estate. Sensors run for years without battery changes. Data goes into a dashboard or straight to irrigation control logic.

Smart city applications — street lighting control, bin fill sensors, parking occupancy, air quality monitoring — are well-established. UK councils including Bristol, Manchester, and Milton Keynes have LoRaWAN deployments at scale. The gateway density in urban areas makes coverage easy to achieve.

Asset tracking works for slow-moving assets — tools on a construction site, equipment in a hospital, trailers in a logistics yard. Combine a GPS module with a LoRaWAN transmitter and you’ve got location updates every few minutes with multi-year battery life. For assets that move fast across wide areas, you’d switch to a different technology, but for assets that mostly stay within a defined geographic area, this is hard to beat.

Getting Started

For a first deployment, the simplest path is: pick up a RAK7244 Raspberry Pi-based gateway (around £180), install ChirpStack via Docker, connect a few sensor nodes (Dragino LHT65 for temperature/humidity is a reliable starter at around £25 each), and start seeing data in the ChirpStack dashboard within a few hours.

The TTN community forum and ChirpStack documentation are genuinely good. The technology has been deployed long enough that most common problems have documented solutions, and the open-source tooling is mature. In 2026, LoRaWAN isn’t cutting-edge — it’s proven infrastructure that deploys reliably when you need what it offers.