ChirpStack hosting costs
This comparison is for teams asking whether they should run ChirpStack themselves or use a managed operations model. The server invoice is only one part of the cost. Productive ChirpStack also needs hardening, monitoring, backups, gateway onboarding, updates and incident response.
Table of Contents
- Short answer
- What actually drives the cost
- When each model fits
- What merkaio includes
- Related decisions
Short answer
Self-hosting is cheapest when you already have a team that can operate PostgreSQL, Redis, MQTT, TLS, gateways and updates. Managed operations become cheaper when downtime, response time and internal engineering capacity matter.
If you need a production LoRaWAN network without building a platform team first, see Managed ChirpStack hosting.
What actually drives the cost
| Cost driver | Self-hosted ChirpStack | Managed ChirpStack operations |
|---|---|---|
| Infrastructure | VMs, storage, backups, domains and network rules are selected and paid separately. | Server, backups and network setup are sized as part of the managed service. |
| Setup | Your team installs ChirpStack, MQTT, Redis, PostgreSQL and the Gateway Bridge. | Architecture, deployment and gateway onboarding are handled by merkaio. |
| Monitoring | You build alerts for gateways, queues, MQTT, database health and disk growth. | Monitoring and alert routing are included in operations. |
| Updates | Version checks, backup windows and rollback plans stay internal. | Updates are planned, executed and checked as part of the service. |
| Incidents | Your team owns troubleshooting when gateways stop sending or joins fail. | merkaio investigates stack, gateway and integration issues with defined response paths. |
| Scale | Capacity planning becomes your work as gateways and device traffic grow. | Scaling is planned around device volume, retention and integration load. |
When each model fits
Use self-hosting for labs, pilots and teams with existing operations capacity. ChirpStack is a good open-source system, and a technical team can run it well when time, ownership and monitoring are available.
Use managed operations when field devices, customer dashboards or service contracts depend on the network. In that case the cost of unclear ownership is usually higher than the cost of the server.
Use an edge appliance when data must stay on site or internet outages are expected. A local setup can run the LoRaWAN stack close to the assets.
What merkaio includes
The managed price covers work that is easy to miss in a simple hosting calculation:
- dedicated ChirpStack architecture with MQTT, Redis and PostgreSQL
- gateway onboarding, frequency-region setup and first device checks
- monitoring for stack health, storage, gateways and integrations
- backup concept, update windows and rollback planning
- integration with Grafana, ThingsBoard, webhooks or custom applications
Related decisions
ChirpStack is a trademark of its respective owner. merkaio is an independent infrastructure and operations provider.
Frequently asked questions
Is ChirpStack itself free?▼
What is missing from a basic server cost estimate?▼
When does managed ChirpStack make sense?▼
Can merkaio migrate an existing ChirpStack setup?▼
That is a lot of manual work, and operating it comes on top.
Updates, backups, hardening, monitoring: a production LoRaWAN server needs not just setup but continuous operation. We take that off your plate, as Managed ChirpStack on European infrastructure or preinstalled and ready to run on the merkaio edge pro.
Written by
Timo Wevelsiep
Founder, merkaio
Builds and operates LoRaWAN and IoT platforms, from ChirpStack to custom applications.
LinkedIn