I’m Chloe McAree and I’m a Senior Software Engineer, and I’ve worked across a broad range of projects throughout my career and my time at Hamilton Robson. When I first started working with IOT devices and in particular LoRaWAN, I had imagined a simple setup: a device sends data over radio, a gateway picks it up, and the data magically appears in the cloud. In reality, there was a crucial middle piece that I needed to make this possible and that was a  LoRaWAN Network Server (LNS). 

Devices and gateways are constantly sending signals, but without an LNS, those signals would be uncoordinated, insecure, and unusable. 

Here’s why the LNS is essential: 

• Device management: It handles how devices join the network (via OTAA or ABP), keeps track of their keys, and enforces LoRaWAN security. 
• Message handling: Streams messages from a device, routes them to the correct application and formats them into a more readable format. 
• Downlink scheduling: If you need to send commands to a device, the LNS coordinates the timing (since LoRaWAN devices usually sleep and only “listen” at certain times). 
• Scalability & reliability: As you add more gateways and devices, the LNS ensures everything stays synchronised and doesn’t interfere. 

If you’re new to the world of LoRaWAN and IoT, one of the first big decisions you’ll face is: Which LoRaWAN Network Server (LNS) should I use? 

The LNS is really at the heart of your LoRaWAN deployment. Since it manages device registrations, handles uplinks and downlinks, enforces security, and routes your data where it needs to go. Choosing the right one can make your life a lot easier! 

In this post, I’ll share our experiences with three common LNS options: The Things Industries (TTI), ChirpStack, and AWS IoT Core. Each comes with its own pros and cons, and which one is right for you depends on your project’s scale, budget, and technical requirements. 

The Things Network/Industries  

The Things Network is a LoRaWAN network and managed LNS platform. It comes in two flavours: 

• Community edition (free) – anyone can connect gateways/devices to the public network, but without SLAs or dedicated infrastructure.
• The Things Industries (TTI, paid) – a commercial version that provides private clusters, enterprise features, and guaranteed reliability.

With the paid plan, you’re not sharing resources with the public community, you get your own private cluster, which gives you more control, scalability, and stability for production use. 

At Hamilton Robson, we have built a large enterprise meeting room occupancy platform, that spans 4 continents, over 7 time zones and is currently processing over 2.3 million data requests per day. We use a paid Thing Stack Industries account with our own cluster for this. 

What we liked 

• Dedicated cluster: Having our own private cluster avoids noise from the shared community edition and ensures global reliability. 
• Global reach: Since this project is a worldwide, TTN’s cluster architecture means we don’t have to manage separate infrastructure in each region. 
• Gateway insights: We get visibility into how gateways are performing, which helps us troubleshoot and optimize deployments. 
• Managed service: No need to self-host or worry about updates — TTI handles it. 

This service is best used for: teams that want a managed, production-ready LoRaWAN service with global reach, but don’t mind paying for simplicity and support. 

ChirpStack 

ChirpStack is an open-source LoRaWAN Network Server stack you host yourself. Unlike TTI, there’s no subscription or managed cluster, you run it on your own infrastructure (on-premise, in the cloud, or even lightweight devices like a Raspberry Pi for small setups). 

Compared to a paid TTI cluster, ChirpStack offers more control and flexibility but at the cost of maintenance overhead. You don’t get features like built-in gateway insights, but you save significantly on recurring costs. 

We used ChripStack in the environmental monitoring system we have recently deployed, because our customer had a requirement that it needed to run fully on-premise. 

What we liked 

• Feature-rich: ChirpStack covers almost everything TTI does in terms of device management and message handling.
• Lower cost: Because it’s open-source, there are no subscription fees. You just pay for the infrastructure you run it on. 
• Flexibility: You can deploy it on-premise or in the cloud, and configure it however you want. 

Drawbacks 

• Maintenance burden: You have to deploy, scale, and maintain it yourself. 
• No gateway insights: Unlike TTI, ChirpStack doesn’t provide built-in monitoring of gateway health. 

This service is best used for: teams who want full control over their LNS, are comfortable managing infrastructure, and want to avoid recurring SaaS fees.

AWS IoT Core 

AWS IoT Core is Amazon’s cloud-native IoT platform, and it can also serve as a LoRaWAN Network Server. With IoT Core, you register gateways and devices directly in AWS, and data flows seamlessly into AWS services through its rules engine. 

Compared to a paid TTI cluster, IoT Core is tightly integrated into AWS and removes the need for a separate LNS service altogether. However, it only works with AWS-qualified LoRa gateways, which introduces some hardware lock-in. 

What we like 

• Rules engine: You can filter uplinks, trigger Lambdas and route messages to AWS services like SQS/SNS/Kinesis, or call APIs. 
• Device management: Supports rules, alerts, and basic provisioning. 

Drawbacks 

• Gateway limitations: AWS IoT Core only supports AWS-qualified LoRa gateways. If you don’t commit to one of these, you risk lock-in. 
• Learning curve: IoT Core is very powerful, but it comes with AWS complexity and pricing. 
• Insights: AWS IOT core is more of a black box when it comes to debugging, while TTI and ChirpStack, allow you to view log streams from each individual device and gateway streams, AWS does not provide this out of the box and you need to invest development time in creating and setting this up. 

This service is best used for: teams already invested in AWS, or who want tight integration with other AWS services — but only once you’ve confirmed your gateway is supported. 

Final Thoughts 

There’s no one-size-fits-all answer when it comes to LNS selection. Here’s how I’d summarize it: 

• Pilots or Enterprise ready global deployments → TTI gets you up and running fast and makes global deployment easy. 
• Cost-sensitive or infra-savvy teams → ChirpStack gives you control and avoids recurring fees. 
• AWS-heavy architectures → IoT Core can be a strong long-term play, but only if you’re aligned with AWS’s gateway ecosystem. 

For our projects at Hamilton Robson, TTI gave us global reach quickly, ChirpStack gave us flexibility when customers had their own infrastructure, and AWS IoT Core is where we see future possibilities for deeper cloud integration. 

 Read the next blog in this series here.