ChirpStack vs The Things Stack: A Definitive LoRaWAN Network Server Comparison

WZ-IT operates chirphost. Current hosting starts from €129.90 net/month; setup and service level follow the proposal. Former package prices, location lists and cost comparisons in this dated article describe the previous offer, not current WZ-IT terms. View current service scope.

ChirpStack and The Things Stack represent fundamentally different philosophies for running LoRaWAN infrastructure — self-hosted open-source freedom versus managed cloud convenience. ChirpStack v4, rewritten in Rust as a single unified binary, gives organizations full control over their data and infrastructure with zero license fees, proven at scales of 52,000+ devices. The Things Stack, backed by The Things Industries, offers a managed cloud platform starting at ~$230/month with 99.9% SLA, 36+ pre-built integrations, and the world's largest community LoRaWAN network. The right choice depends on your team's DevOps capability, data sovereignty requirements, deployment scale, and willingness to manage infrastructure. This comparison covers architecture, features, costs, and real-world considerations current through early 2026.

Table of Contents

• Architecture: one unified binary versus distributed microservices
• Feature comparison reveals different strengths
• Scalability and the fair use question
• Cost analysis: infrastructure versus subscription
• Data sovereignty gives ChirpStack a decisive edge
• Community, ecosystem, and third-party tools
• Recent developments show both platforms actively evolving
• Migration paths favor moving toward TTS
• Conclusion
• Sources

Architecture: one unified binary versus distributed microservices

ChirpStack v4 represents a radical architectural simplification from v3. The formerly separate Network Server and Application Server have been merged into a single binary, eliminating the inter-service configuration complexity that plagued v3 deployments. Written entirely in Rust (replacing Go from v3), ChirpStack v4 delivers strong memory safety and performance while requiring just three infrastructure dependencies: PostgreSQL (or SQLite since v4.10.1), Redis, and an MQTT v5 broker such as Mosquitto. A complete deployment fits into a single Docker Compose file — the official chirpstack-docker repository bundles everything needed, pre-configured for all LoRaWAN regions. For embedded or edge scenarios, the SQLite backend allows ChirpStack to run on Raspberry Pi-class hardware via ChirpStack Gateway OS.

The Things Stack takes a different approach with a full microservices architecture comprising five distinct components: Identity Server, Gateway Server, Network Server, Application Server, and Join Server. This architecture enables independent scaling of each component — from a single-binary development setup to globally distributed carrier-grade networks. TTS is available in multiple editions: the free Sandbox (formerly Community Edition) for non-commercial use, the free Discovery tier limited to 10 devices, paid Cloud Standard and Plus tiers as fully managed SaaS, a self-hosted Enterprise edition, and a community Open Source edition compilable from GitHub. The Sandbox runs on three global clusters in Dublin, California, and Sydney.

Deployment complexity differs significantly. ChirpStack requires provisioning and maintaining your own servers, databases, and MQTT broker — but a functional instance can be running within an hour using Docker Compose. The Things Stack Cloud eliminates all infrastructure management; registration takes minutes. TTS Enterprise sits between these extremes, requiring customer infrastructure but providing commercial Docker images and AWS CloudFormation templates for streamlined deployment.

Feature comparison reveals different strengths

Both platforms support the full LoRaWAN specification — Classes A, B, and C, LoRaWAN 1.0.x and 1.1, all regional frequency plans, OTAA and ABP activation, and Adaptive Data Rate. The differences lie in ecosystem breadth and customization depth.

Device management approaches diverge in notable ways. The Things Stack offers a comprehensive Device Repository with pre-configured profiles for hundreds of commercial devices, batch registration via CSV/JSON import, and QR code scanning for rapid onboarding. ChirpStack provides device profiles with customizable parameters and can import device profiles from The Things Stack's device repository, but lacks the same breadth of out-of-box device templates. Both platforms support device metrics dashboards, frame logging for debugging, and multicast groups for Class B/C devices.

Integration ecosystems show the starkest contrast. The Things Stack provides 36+ pre-built webhook templates covering platforms like Datacake, TagoIO, Ubidots, AllThingsTalk, Losant, and many more. Its cloud integrations are particularly deep: the AWS IoT Core integration includes CloudFormation templates for automated deployment, and the Azure IoT Hub integration provides ARM templates for device provisioning and shadow updates. ChirpStack offers approximately 10–12 built-in integrations — MQTT (always active), HTTP webhooks, InfluxDB (v1, v2, and v3), ThingsBoard, AWS SNS, Azure Service Bus, GCP Pub/Sub, AMQP/RabbitMQ, myDevices, Pilot Things, IFTTT, and Blynk. Where ChirpStack has an edge is its native InfluxDB integration that writes device data directly, making Grafana dashboards trivially easy to set up — TTS requires webhook middleware for the same workflow.

Codec support is comparable: both use JavaScript-based payload formatters for encoding and decoding device payloads, with built-in CayenneLPP support. ChirpStack additionally allows custom ADR algorithms written in JavaScript, giving network operators fine-grained control over data rate optimization. Both platforms support multi-tenancy — ChirpStack through its tenant/organization structure with per-tenant user management and API keys, and TTS through isolated customer tenants on Cloud or configurable multi-tenancy on Enterprise.

A distinguishing TTS feature is Packet Broker — an open, global backbone for LoRaWAN traffic peering that enables roaming between networks. Launched in 2020 and processing over 25 million messages per day, Packet Broker allows devices to use gateways from different network operators, supports commercial peering agreements, and even enables satellite-to-ground peering through a Lacuna Space partnership. ChirpStack has no equivalent roaming or peering capability.

ChirpStack counters with unique features of its own: Gateway Mesh (v4.9.0) extends coverage through relay gateways that operate without internet connectivity, and ChirpStack Gateway OS provides a complete OpenWrt-based operating system for running gateway components, including a bundled Node-RED instance. The platform also supports end-to-end encryption (v4.6.0+) where the application server never sees plaintext application data.

Scalability and the fair use question

The Things Stack Sandbox imposes a Fair Use Policy limiting each device to 30 seconds of uplink airtime per day and 10 downlink messages per day (including acknowledgments). At SF7, this allows roughly 647 small packets daily — adequate for many monitoring use cases but insufficient for applications requiring frequent downlinks like actuator control or confirmed uplinks. The policy is reportedly not always actively enforced at the network level, but production deployments should not rely on this leniency.

Commercial TTS Cloud plans eliminate fair use restrictions entirely. The Standard plan includes 1,000 devices with pay-as-you-go scaling; AWS Marketplace pricing reveals the cost curve: ~$245/month for 1,000 devices, ~$910 for 5,000, and ~$1,365 for 10,000. Deployments above 50,000 devices require custom pricing through direct sales. TTS Cloud guarantees 99.9% uptime SLA on paid tiers.

ChirpStack imposes no artificial limits whatsoever — scaling is bounded only by provisioned infrastructure. Real-world evidence validates this approach: a deployment in Turkey runs 52,000 active end devices across 17 applications and 5 organizations on a single ChirpStack instance, with EMQX replacing Mosquitto as the MQTT broker for stability at scale. Other confirmed production deployments include nationwide networks with 200+ gateways in the Middle East and multi-city Kubernetes deployments on Azure AKS. At scale beyond approximately 15,000 devices, operators should replace Mosquitto with clustered MQTT brokers like EMQX or VerneMQ for RAM stability.

Cost analysis: infrastructure versus subscription

The cost equation fundamentally differs between the two platforms. ChirpStack's MIT license means zero software costs — you pay only for infrastructure and labor. The Things Stack charges subscription fees that include infrastructure, management, and support.

For ChirpStack, infrastructure costs depend on your hosting provider and deployment size. A complete self-hosted IoT stack including ChirpStack, ThingsBoard, Grafana, and InfluxDB can run for as little as €40–80/month on European VPS providers for up to 5,000 devices. With managed cloud databases and high availability, costs rise to €300–600/month for medium deployments and beyond for large-scale setups. The critical hidden cost is DevOps labor: security patching, monitoring, backups, and updates can consume hundreds of engineering hours annually. Organizations without dedicated infrastructure teams often underestimate this burden — operations and maintenance typically represent roughly 51% of total cost of ownership.

The crossover where self-hosted ChirpStack becomes clearly more economical typically occurs at very large scale (50,000+ devices) or when the organization already has IoT infrastructure management as a core competency. For small to medium deployments, the managed TTS Cloud often delivers lower total cost when labor is honestly accounted for.

With chirphost managed hosting, organizations get the best of both worlds: ChirpStack's data sovereignty and zero license fees, combined with professional infrastructure management — at a predictable flat rate starting from €99.90/month. No DevOps overhead, no surprise costs. Which flat rate fits which fleet size is shown in the chirphost plans and pricing.

Data sovereignty gives ChirpStack a decisive edge

For organizations in regulated industries or those subject to strict data residency requirements, ChirpStack offers the strongest position. All data remains entirely on your own infrastructure — no third-party cloud provider ever sees sensor payloads, no Data Processing Agreement is required for the network server itself, and data can be kept within specific jurisdictions. Hosting ChirpStack on European servers keeps all LoRaWAN data within EU borders under full GDPR compliance without involving any US-headquartered cloud provider.

The Things Stack Cloud processes data on TTI-managed infrastructure. While The Things Industries is headquartered in the Netherlands (an advantage over US-based providers), data still traverses third-party managed infrastructure requiring a DPA with TTI. The Sandbox network — with its shared community gateways and infrastructure — is unsuitable for any application with data sovereignty requirements.

TTS Enterprise bridges this gap by allowing self-hosted deployment on customer infrastructure while retaining access to the TTI ecosystem, including Packet Broker peering and the Network Operations Center. For organizations that need both data sovereignty and TTI's commercial features, Enterprise is the appropriate tier.

For healthcare, utilities, government, and defense applications where data cannot leave controlled environments, self-hosted ChirpStack or TTS Enterprise are the only viable options. Deutsche Bahn, notably, uses The Things Stack for various use cases across trains, stations, and maintenance facilities — demonstrating that even large, regulated enterprises can work with the TTS ecosystem when properly configured.

chirphost eliminates this trade-off entirely: fully managed ChirpStack hosting in ISO 27001 certified data centers in Germany. Full data sovereignty, zero operational burden. Details on regions, certifications and scope are on the managed ChirpStack hosting from Germany overview.

Community, ecosystem, and third-party tools

The Things Network boasts the larger community by a significant margin — a global network of 20,000+ community gateways, local communities in hundreds of cities worldwide, and an annual conference (The Things Conference in Amsterdam) drawing 1,500+ ecosystem members. The TTN forum has tens of thousands of registered users, and the documentation at thethingsindustries.com is polished, extensive, and includes step-by-step guides with screenshots for 20+ gateway models and dozens of integrations.

ChirpStack's community is smaller but technically focused — ~946 GitHub stars on the main repository, with an active Discourse forum at forum.chirpstack.io. The project is primarily maintained by a single developer, Orne Brocaar, who has led development since 2015 and provides commercial consultancy, training, and custom engineering. Documentation is comprehensive but more developer-oriented, with less visual guidance than TTS.

For third-party tool integration, both platforms connect well with the most popular IoT middleware:

• ThingsBoard: Both have native bidirectional integrations; ThingsBoard PE includes dedicated integration types for each platform. For managed ThingsBoard hosting, see thingshost.de
• Node-RED: ChirpStack has dedicated npm nodes; TTS recommends standard MQTT nodes (the older node-red-contrib-ttn package is deprecated)
• Grafana: ChirpStack's built-in InfluxDB integration makes this particularly straightforward; TTS requires webhook or MQTT middleware.
• Home Assistant: TTS has an official HA integration (~353 active installations); ChirpStack requires manual MQTT configuration

Gateway hardware compatibility is broadly equivalent — both support all major brands including RAK, Kerlink, Multitech, Mikrotik, Dragino, Milesight, and Tektelic via either Semtech UDP Packet Forwarder or LoRa Basics Station protocols. TTS strongly prefers Basics Station for security reasons. ChirpStack offers additional flexibility through its MQTT Forwarder (allowing gateways to bypass the UDP protocol entirely), Concentratord (hardware abstraction daemon), and the ability to connect a single gateway to multiple network servers simultaneously. Notably, Dragino switched its LPS8v2 gateway from pre-installed TTS to pre-installed ChirpStack v4 in 2023 — a signal of ChirpStack's growing gateway vendor adoption.

Recent developments show both platforms actively evolving

ChirpStack v4 has maintained a rapid release cadence through 2024–2026, with 8–10 releases annually. Key additions include FUOTA support (v4.12.0, April 2025) implementing LoRa Alliance firmware update specifications, Gateway Mesh (v4.9.0) for relay gateways without internet, SQLite support (v4.10.1) for embedded deployments, RP002-1.0.5 with SF5/SF6 (v4.16.0), and new integrations for Blynk and InfluxDB v3. The current release is v4.16.2 with v4.17.0 in development, adding read-only API keys, CLI password reset, and secondary NetIDs for roaming.

The Things Stack reached v3.35.2 (January 2026) with v3.36 in development. Recent highlights include MAC settings profiles (v3.35.0) for reusable device configuration templates, improved ADR algorithms fixing off-by-one errors and flip-flop conditions, channel steering for US915/AU915 devices, and webhook pausing from the console. The February 2025 launch of global LoRaWAN network peering through Packet Broker — including satellite connectivity via Lacuna Space — represents the most strategically significant TTS development, enabling commercial monetization of gateway coverage across networks.

Migration paths favor moving toward TTS

Moving from ChirpStack to TTS is well-supported through the official ttn-lw-migrate CLI tool, which exports device descriptions from ChirpStack (both v3 and v4) into TTS-compatible JSON format, including session data for seamless migration of active devices.

The reverse migration — TTS to ChirpStack — lacks a dedicated tool and requires manual re-provisioning: removing devices from TTS, re-registering them in ChirpStack with the same DevEUI/AppEUI/AppKey, reconfiguring gateways, and triggering new join requests. ChirpStack can import device profiles from the TTS Device Repository, which eases profile creation. For either direction, payload decoders must be recreated, all integrations reconfigured, and historical data exported separately. OTAA devices need to rejoin the network, while ABP device sessions can potentially be preserved if session data is migrated. How that path plays out in practice, from the device list through the OTAA rejoin to switching the gateways over, is described in our guide to migrating from The Things Network to ChirpStack.

Conclusion

The choice between ChirpStack and The Things Stack is ultimately a build-versus-buy decision that hinges on three factors: data control requirements, team capability, and deployment scale. ChirpStack delivers unmatched data sovereignty, zero licensing costs, and proven scalability to tens of thousands of devices — but demands infrastructure expertise and ongoing operational investment. The Things Stack provides a faster path to production with richer out-of-box integrations, the world's largest LoRaWAN community network, and unique roaming capabilities through Packet Broker — at the cost of subscription fees and reduced data control.

For private industrial networks, regulated industries, and organizations with strong DevOps teams, ChirpStack is the natural choice. For rapid prototyping, commercial deployments without dedicated infrastructure staff, and projects benefiting from multi-network roaming, The Things Stack Cloud delivers more value. The emergence of TTS Enterprise as a self-hosted commercial option and ChirpStack's growing feature parity (FUOTA, Gateway Mesh, embedded SQLite) are gradually narrowing the gap — but the architectural philosophies remain fundamentally different, and that distinction drives the decision.

With chirphost, you don't have to choose between control and convenience. Managed ChirpStack hosting gives you full data sovereignty, zero license fees, and professional infrastructure management — starting from €99.90/month, hosted in ISO 27001 certified data centers in Germany.

If the choice lands on a managed instance, scope, regions and SLA are covered on the rent a LoRaWAN network server page.

Sources

• ChirpStack Official Website
• ChirpStack Architecture Documentation
• ChirpStack GitHub Repository (MIT License)
• ChirpStack Docker Compose Setup
• ChirpStack Changelog
• ChirpStack Forum — 52,000 Device Deployment
• The Things Industries — Stack Plans & Pricing
• The Things Industries — Stack Overview
• The Things Stack GitHub Releases
• AWS Marketplace — The Things Stack Cloud
• The Things Network
• TTN Forum — Fair Use Policy Explained
• The Things Industries — Deutsche Bahn Case Study
• ThingsBoard — ChirpStack Integration