LoRaWAN

LoRaWAN is an open, royalty-free networking protocol standardised by the LoRa Alliance that sits on top of Semtech's LoRa radio modulation. Where LoRa defines how bits travel through the air — chirp spread spectrum that trades data rate for kilometres of range — LoRaWAN defines the media-access and network architecture above it: how thousands of battery-powered end devices share airtime, authenticate, encrypt payloads, and route messages through gateways to a network server. The two names are constantly conflated, and keeping them separate is the first step to choosing the right tool.

Star-of-stars topology

A classic LoRaWAN deployment is not a peer mesh. End devices broadcast to any gateway in range; gateways are simple packet-forwarders that relay traffic over IP backhaul to a central network server, which de-duplicates packets heard by multiple gateways, manages the radio parameters, and passes decrypted application payloads onward. This star-of-stars design keeps the end nodes extremely simple and power-frugal — a sensor can run for years on a coin cell because it wakes, chirps a few bytes, listens briefly, and sleeps. Devices come in three classes that trade downlink responsiveness against battery: Class A opens two short receive windows only after it transmits, Class B adds scheduled beacon-synchronised slots, and Class C listens continuously at mains-powered energy cost.

Airtime discipline and adaptive rates

Because LoRaWAN lives in the licence-free ISM bands, it inherits their etiquette: regional duty-cycle and dwell-time limits cap how often any node may transmit. The protocol works with, not against, these constraints — the network server runs adaptive data rate (ADR), instructing each device to use the fastest spreading factor its link quality allows, which shortens airtime, saves battery, and multiplies overall network capacity. It is a well-engineered system for its purpose: enormous fleets of low-power sensors reporting small payloads over long distances, with the coordination burden pushed onto mains-powered infrastructure where energy is cheap.

Devices join the network in one of two ways: over-the-air activation (OTAA), where the device performs a join handshake and derives fresh session keys — the recommended path — or activation by personalization (ABP), where keys are baked in at provisioning, simpler but weaker since the keys never rotate.

Security and sovereignty trade-offs

LoRaWAN provides AES-128 encryption by default, with separate network and application session keys so the infrastructure operator can route packets without reading payloads — a genuinely thoughtful design, attractive for sovereign telemetry. The catch is architectural: everything flows through internet-connected gateways to a network server, so joining a public LoRaWAN network reintroduces exactly the central dependency a sovereign builder is trying to remove. The server operator sees metadata, controls access, and is a single point of failure. The remedies run in order of effort: self-host a private LoRaWAN network server on hardware you control, or skip the protocol entirely in favour of peer-to-peer mesh firmware such as Meshtastic, which uses the very same LoRa radios with no gateway, no server, and no backhaul at all.

Choosing between LoRaWAN and a mesh

The decision is workload-shaped. Dozens of sleepy sensors reporting to one collector — water tanks, soil probes, a mining container's door and temperature sensors — favour LoRaWAN's star topology and battery economics. Human-to-human messaging that must survive infrastructure loss favours a decentralised mesh, where every node relays and no single box matters; compare the approaches under mesh routing. Many homesteads sensibly run both on the same band plan. Review the underlying radio at LoRa before committing hardware to either.

See regional bands in the Meshtastic/LoRa regions dataset.

Full open-data reference: Meshtastic LoRa Modem Presets — CSV / JSON + REST API, CC BY 4.0.