Why choose The Things Stack: LoRaWAN, built to last

The short answer

The Things Stack is a LoRaWAN Network Server (LNS) built by The Things Industries. It connects more than 6 million devices across 2,000+ enterprise deployments. Quietly, those deployments generate more than $2 billion in economic value every year.

Individuals and teams choose The Things Stack for three reasons. It is built only to be a network server, so it does that job better than tools that bolt one on. It runs anywhere, from our cloud to your own data center. And it keeps your network independent of any application, cloud or hardware vendor, so you can change the layers above it without rebuilding the network underneath.

If you are comparing LoRaWAN options in 2026, start with the layer everything else depends on. That layer is the network server.

What a LoRaWAN Network Server actually does

A LoRaWAN Network Server is the brain of a LoRaWAN network. Every message from every sensor passes through it before it reaches your application.

A LoRaWAN deployment has four layers:

1. Devices: sensors and meters that send small packets of data over long distances on very little power.
   
   

2. Gateways: radio receivers that pick up those packets and forward them over the internet.
   
   

3. The LoRaWAN Network Server: authenticates each device, removes duplicate messages, decides which gateway answers, manages radio settings and keeps encryption keys safe.
   
   

4. Applications: the dashboards, ERP, BMS and cloud platforms where the data turns into decisions.

Here are 7 reasons to deploy with The Things Stack

1. We only build one thing

No dashboards. No side products. Just the LoRaWAN Network Server, since 2015. That focus is why the edge cases you’ll hit at device 40,000 are ones we fixed years ago.

2. It already runs at your target scale

6 million+ devices. 2,000+ enterprise deployments. 25% growth every year. Deutsche Bahn, Bosch, SkyCell and Wien Energie run live operations on it. Your rollout plan isn’t a stress test for us.

3. Cloud today, on-prem tomorrow, same stack

Start on The Things Stack Cloud, move to a dedicated instance, or self-host in your own data center [verify tier names]. Same APIs, same CLI, same features. Your devices never notice the move.

4. Security isn’t a plugin

Built-in Join Server, hardware secure element support, secure device claiming. Role-based access and SSO. Your keys stay yours, and your security review gets shorter.

5. Swap anything above or below the network

Any LoRaWAN device. Any standard gateway. MQTT, webhooks, AWS, Azure and dozens of IoT platforms out of the box. Change your application next year without re-onboarding a single sensor.

6. From unboxing to first uplink in minutes

The LoRaWAN Device Repository gives you over 1,500 device profiles with payload decoders already written. Pick the device, enter the keys, watch data arrive. No decoder writing, no guesswork.

7. Built for year five, not week one

Launching 100 sensors is easy. Keeping 100,000 healthy for a decade is the job. Gateway fleet management, multi-tenancy, FUOTA and multicast, LoRaWAN Relay, roaming through Packet Broker, a 99.9% uptime SLA and support directly from our engineers who wrote the code.

Six questions to ask any LoRaWAN Network Server provider

Comparison sites list features. These questions tell you what happens after go-live.

1. Is the network server your core product, or one feature among many? Focus decides how fast bugs get fixed and standards get supported.

2. How many devices are active on it today? Not contracted, not registered and sitting in a warehouse. Active, in the field, sending data.

3. Can I self-host it if my requirements change? If the answer is no, your data residency options are already decided for you.

4. Can I switch applications without touching my devices? If not, you are buying a bundle, not a network.

5. How will I receive the keys for my devices? If the answer is a spreadsheet attachment, that’s a red flag. Keys should be handed over securely through a Join Server, never sent by email.

6. What is the uptime SLA, and who do I talk to when something breaks? At 3am, a forum thread is not support.

The Things Stack has a straight answer to all six. That is the point.

Start with the layer that lasts

Applications change. Cloud providers change. Your sensors will be in the field for ten years. Build them on a LoRaWAN Network Server that is designed to outlast everything above it.

Explore The Things Stack features or talk to someone from our team about your deployment.