How much compute and storage is included?

The entry level is a dedicated size XS instance with 2 vCPU, 2 GB RAM, 40 GB NVMe SSD for €99.90; it suits lightweight applications as well as test and development environments. Size S with 2 vCPU, 4 GB RAM, 80 GB NVMe SSD costs €129.90. We check which size ChirpStack needs in production before provisioning. Size M (4 vCPU, 8 GB RAM, 80 GB NVMe SSD) costs an extra €29.90 excl. VAT, L (8 vCPU, 16 GB RAM, 80 GB NVMe SSD) an extra €89.90 excl. VAT and XL (16 vCPU, 32 GB RAM, 80 GB NVMe SSD) an extra €199.90 excl. VAT, each per month. Additional storage costs €4.99 excl. VAT per 50 GB and month.

Is the number of users limited?

No. WZ-IT does not limit the number of users. How many users can work smoothly at the same time depends on usage and the chosen instance size XS to XL.

What is the contract term?

ChirpStack Hosting can be cancelled monthly, with no minimum term and 30 days' notice to the end of the month.

Where is the data stored?

Germany and Switzerland are available at the same prices, in both cases without US clouds. The data centres are ISO 27001 certified; in Germany we additionally operate with a German provider whose data centres are BSI C5 attested. The Section 203 Managed Cloud for professional-secrecy holders is available in Germany only.

How quickly is ChirpStack ready to use?

We typically provide a production instance within a few business days after signing. For a trial, we set up a test instance, usually on the next business day; it runs free of charge for 7 days and without payment details.

Can I use my own domain?

Yes. One .de domain is included with every hosting plan. Alternatively, connect your own domain or subdomain with a CNAME record.

ChirpStack is an open-source LoRaWAN® Network Server stack that allows you to connect, manage, and securely integrate LoRaWAN gateways and end devices into your systems - typically via MQTT/HTTP/API.

What is ChirpStack typically used for?

For IoT/IIoT such as sensors in buildings, industry, agriculture, smart city, tracking, and monitoring - anywhere long battery life and wide radio range are important (LoRaWAN).

What components make up the ChirpStack architecture?

Typically: Gateway Bridge, ChirpStack (Network Server + Web UI), and backend components (e.g., PostgreSQL, Redis, MQTT Broker).

What infrastructure components does ChirpStack need?

In standard setups, ChirpStack uses PostgreSQL (persistence), Redis (caching/state), and an MQTT broker for messaging/integrations.

What role does a LoRaWAN gateway play?

The gateway is the radio bridge between your LoRaWAN end devices and the server stack. It forwards LoRaWAN frames to ChirpStack (and downlinks back).

Do you support setting up LoRaWAN gateways?

Yes - we set up gateways, connect them to ChirpStack, and test the radio link (gateway ↔ device), including proper documentation and acceptance testing.

How do I connect a gateway to ChirpStack?

Basically: Create the gateway in ChirpStack, configure the forwarder/station, verify connectivity, and validate LoRaWAN frames.

Which end devices can I connect?

All LoRaWAN-compatible sensors/trackers/modules, provided the region/parameters and activation (OTAA/ABP) match and the necessary identities/keys are available.

How are LoRaWAN devices organized in ChirpStack?

ChirpStack works with Device Profiles (capabilities/versions/region params) and Applications (logical grouping of devices by use case).

What do I need to create a device (OTAA/ABP)?

At minimum: DevEUI, LoRaWAN MAC version, and Regional Parameters Revision. For ABP, also DevAddr + session keys; for OTAA, root keys - unless using an external join server.

Does ChirpStack support OTAA and ABP?

Yes. In practice, OTAA is usually standard (better key handling/provisioning), ABP is used depending on device/use case.

How do I test if a device is transmitting correctly?

In ChirpStack, you can check LoRaWAN frames and device events (JoinRequest/JoinAccept, uplinks, etc.).

Can payloads (sensor values) be decoded directly in ChirpStack?

Yes: Device Profiles can reference a payload decode function to transform raw data into usable values.

How does IoT data get from ChirpStack to my cloud/IT systems?

Typically via MQTT (events/topics), alternatively via APIs/integrations. MQTT is a central integration pattern in ChirpStack.

Can you set up an MQTT broker (including TLS)?

Yes - we set up the MQTT broker properly (TLS, credentials, permissions/topics), connect ChirpStack, and provide clear documentation of data flows.

What MQTT topics/event types are common?

ChirpStack publishes events like Uplink, Join, etc. - and tools like Node-RED can subscribe to and process these events.

Do you also handle data processing after MQTT (pipelines)?

Yes - e.g., forwarding to databases/time series, dashboards, alerting, or to your business systems. Common components: Node-RED, workers/streams, TSDB, data lake.

Can ChirpStack be operated in a private network (without public cloud)?

Yes. ChirpStack is suitable for self-hosted setups - on-prem or in a private/isolated cloud environment, including controlled network segments and data flows.

Do you support building a private network gateway ↔ cloud?

Yes - we plan and build secure connectivity (e.g., VPN/S2S, segmented networks, firewall rules) so gateways reliably and securely communicate with ChirpStack.

Can multiple locations/regions be covered with ChirpStack?

Yes - depending on architecture/provider/network design (e.g., multiple gateway locations, central processing, separate environments).

How does ChirpStack scale for many devices?

Scaling typically happens through: broker/DB performance, horizontal components, clean topic structure, backpressure, and capacity planning.

What role do Device Profiles play (and why are they important)?

They prevent chaos: Profiles bundle LoRaWAN version/region parameters/activation/decoder and ensure device groups remain consistent and operable.

What typical errors occur during onboarding?

Classics: wrong DevEUI/keys (MIC errors), wrong region/parameters, gateway config, frame counter issues.

How is monitoring/alerting typically implemented for ChirpStack?

Via metrics/logs from components (ChirpStack, DB, Redis, broker) and infrastructure monitoring. Goal: detect drops/backlogs early before uplinks disappear.

Do you do backups & restore tests for ChirpStack?

Yes - especially for PostgreSQL (configuration/state), plus robust backup strategy and regular restore checks.

Is ChirpStack enterprise-ready?

Yes - in the sense that you can operate, integrate, and secure it in a controlled self-hosted manner. Enterprise primarily comes from the operational concept (monitoring, backups, updates, documentation, SLAs).

What security measures are common for ChirpStack setups?

TLS wherever possible, least privilege, separate service accounts, network segmentation, secrets handling, update policy, logging/auditing, and documented data flows.

Do you support updates, maintenance, and ongoing operations?

Yes - we handle operations, updates, monitoring, backups, incident response, and performance tuning as managed hosting / managed operations.

What services does WZ-IT offer for ChirpStack specifically?

Typically: ChirpStack stack setup (infrastructure + services), gateway rollout (config, site check, tests), private networks/VPN, sensor onboarding, MQTT broker + integration pipelines, data processing (DB/TSDB/dashboards/alerts).

How does a ChirpStack project work with you?

Usually in 5 steps: 1. Requirements (region, use case, device types, data targets), 2. Architecture & security baseline, 3. Stack setup + MQTT + monitoring/backups, 4. Gateway + device pilot (1-3 device types), validation, 5. Rollout + operations (SLA/runbooks/documentation). More details on our ChirpStack page.

ChirpStack Hosting in Germany

WZ-IT runs ChirpStack as a dedicated instance in German data centres, with updates, daily backups, 24/7 monitoring and a personal contact. On request, we also install ChirpStack in your cloud or on premises.

Request hosting Hosting & pricing

Reviews

IT Beratung Service Consulting Soforthilfe

Companies worldwide trust WZ-IT

Read client reviews

About the technology

What is ChirpStack?

ChirpStack is an open-source LoRaWAN network server for building private LoRaWAN networks. It provides a web interface for gateways, devices and tenants plus integrations with cloud services, databases and systems that process device data.

With a gRPC-based API, ChirpStack can be seamlessly extended or integrated into your existing systems.

GitHub Website Official Documentation

Features

Class-A Support
Class-A end devices allow bi-directional communication with two short downlink windows following each uplink.
Class-B Support
In addition to the random receive windows of Class-A, Class-B devices open extra scheduled receive windows via time synchronization.
Class-C Support
Class-C end devices maintain nearly continuous receive windows, minimizing latency at the expense of higher power consumption.
Adaptive Data-Rate
Ensures optimal data rate and transmission power to save energy and improve radio spectrum utilization.
Multi-Tenant
Supports multiple organizations, ensuring that users see only their own data.
LoRaWAN 1.0 and 1.1 Compatible
Supports both LoRaWAN versions simultaneously, including all regional parameter specifications.

Infrastructure, integration and operations

ChirpStack as part of your infrastructure

We do more than provide an application. WZ-IT designs the technical architecture, integrates network and identity, operates the agreed scope and develops integrations when the standard product is not enough.

Architecture and migration

Sizing, target environment, data transfer, cutover and recovery are resolved before production operations.

On-Premise
In your data center: Installation on bare-metal, VM or Docker · Integration with existing Active Directory/LDAP
Cloud Installation
AWS, Azure, Hetzner & more: Installation on AWS, Azure, GCP, Hetzner · Terraform/IaC setup (optional) · Kubernetes or Docker Compose · Capacity and scaling design
Enterprise Setup
Advanced architecture after technical and licence assessment: HA and recovery design where supported by the application and edition · Logging according to feature set and edition · Custom security policies

Network and identity

SSO, secure access, internal systems and existing security components are integrated appropriately.

VPN Access
WireGuard, NetBird, Tailscale, Headscale, OpenVPN, Cloudflare Tunnel · Easy client setup for all devices
SSO Integration
Directly or through an upstream identity layer
Multi-Factor Auth
Depends on application, edition and identity provider
Firewall & Hardening
Fail2Ban, Rate Limiting, IP Whitelisting

Monitoring and service level

Updates, backups, technical monitoring and response paths follow a transparent operational scope.

24/7 proactive monitoring
Updates and patches
Regular updates, CVE monitoring and prioritised patches for critical vulnerabilities
Daily backup with 7-day retention
Personal technical contact

Integration and development

APIs, automation and custom extensions can be delivered beyond basic deployment.

Payload Codecs (JavaScript)
The most important dev part: We write decoder functions for your specific sensors (Milesight, Adeunis, Custom). We convert `0x012F` to `{ temperature: 22.5, unit: 'C' }` - directly in the Network Server.
MQTT & HTTP Integrations
Data must flow. We configure and develop bridges that send decoded data via MQTT to your broker or push it via HTTP webhook into your business application.
Downlink Logic
IoT is not a one-way street. We develop logic that sends commands BACK to the sensor based on analysis (e.g., 'Close Valve' or 'Change Reporting Interval').

Full-service installation with no hidden costs

What the ChirpStack setup includes

Complete installation & configuration
SSL certificate & reverse proxy setup
Backup strategy & disaster recovery
Performance optimization & tuning
Security hardening following OWASP
Monitoring & logging setup
Documentation & best practices
Administrator training (remote)
30 days email support included
Dedicated contact person
Optional integration: LDAP/AD, SSO, MFA
Update strategy & patch management setup

The exact scope depends on the application, edition, infrastructure and criticality. Vendor licences and non-standard components are quoted separately.

Concrete Use Cases

ChirpStack Development & Integration

ChirpStack is the heart of your LoRaWAN network. The challenge lies in the data: sensors send hex bytes, your app needs JSON. We close this gap.

Proprietary Sensor Decoders

Problem

You use specialized sensors or in-house developments for which there is no standard profile in ChirpStack.

Solution

Reverse engineering of the byte payload and development of an efficient JavaScript codec according to manufacturer specifications.

Time-Series Bridge (InfluxDB)

Problem

Sensor data should be stored for long-term analysis, but ChirpStack only stores short-term.

Solution

A Go/Python service that listens to the MQTT stream and writes optimized data to InfluxDB or TimescaleDB - ready for Grafana.

Smart Alerting

Problem

Alarm on threshold violation, but please not with every single packet (debouncing).

Solution

Middleware logic that analyzes the data stream and only alerts if a value remains critical for X minutes (hysteresis).

Managed Hosting & Operations

How much does ChirpStack hosting cost?

Compute, applications, storage and response are shown separately. You can see what ongoing operations include and which requirements need a technical assessment.

Starter workload from€99.90/ month · cancel monthly

ChirpStack hosting in Germany: GDPR-compliant operations

One managed standard application included
.de domain included or your own domain or subdomain via CNAME
German data centres with ISO 27001 and BSI C5, no US clouds
99.9 % standard availability per month
Regular updates, CVE monitoring and prioritised patches for critical vulnerabilities
Central logs with immutable retention
Daily backup with 7-day retention
5 TB outbound traffic per workload and month
24/7 proactive monitoring
Five service levels, 24/7 P1 response with Production or Critical
Personal technical contact

Instance sizes and monthly prices

XS · 2 vCPU, 2 GB RAM, 40 GB NVMe SSD: €99.90 in total
S · 2 vCPU, 4 GB RAM, 80 GB NVMe SSD: €129.90 in total
M · 4 vCPU, 8 GB RAM, 80 GB NVMe SSD: €159.80 in total
L · 8 vCPU, 16 GB RAM, 80 GB NVMe SSD: €219.80 in total
XL · 16 vCPU, 32 GB RAM, 80 GB NVMe SSD: €329.80 in total
Additional storage per 50 GB: +€4.99

Configure now

Straightforward provisioning within a few business days

Payment

Bank transfer

All prices are net and exclude statutory VAT. The offers are addressed to businesses. All on-premises options

Other options

Try it free for 7 days

Request a test instance

We set up a test instance for you, usually on the next business day. No payment details required. After seven days it is deleted unless you continue.

Request a test instance →Bring Your Own Infrastructure

Installation on Your Infrastructure

Installation on your own infrastructure · On-premise or in your cloud · Control over data location and access · Custom configuration · Complete documentation · Initial setup & configuration · Optional support and maintenance contract

Price on request, plus optional support & maintenanceRequest a proposal →On-premises option

Run ChirpStack on hardware at your organisation

As an alternative to managed hosting in the data centre, WZ-IT provides the hardware, configures ChirpStack, and handles hardening, monitoring, updates, backup and technical support. Access can be limited to the internal network or enabled through VPN and existing identities.

from €349 excl. VAT / month · plus one-time provisioning and initial setupView WZ-IT App Node →

Target architecture

Integrate ChirpStack into your infrastructure with clear controls

IoT platforms connect devices, gateways, message transport, time-series data and business systems through controlled network and data paths.

Devices, gateways and sites

Sensors, equipment and edge components send telemetry and receive approved control information.

Secure access

TLS, firewall rules, reverse proxies or private network paths are designed around the platform's exposure.

Identity and permissions

Local accounts, SSO, directories, service accounts and emergency access are connected through clear roles.

ChirpStack platform

Device management, rules, processing and tenants are operated for the fleet and data volume.

Brokers and protocols

MQTT, LoRaWAN, HTTP or further protocols with governed device identities.

Telemetry and storage

Time series, retention, aggregation, capacity and recovery.

Dashboards and business systems

Visualisation, alerting, APIs and integration into operational processes.

The diagram is a resilient target model. Its implementation depends on edition, data flows, load, availability objectives and existing infrastructure.

Role in the overall system

Related services for ChirpStack

This page covers installation and the agreed platform operations for ChirpStack. Custom code, the access layer and special confidentiality requirements remain clearly separated responsibilities that can be added when needed.

Maintain the application

Support custom code and integrations

Keep custom extensions, interfaces and dependencies controlled, updated and supportable.

View service Secure access

Connect users, sites and systems

Add identity-based access and private network paths as a separate operational layer.

View service Operate confidentially

Assess Section 203 requirements separately

For professional secrecy holders, define contractual, access and infrastructure requirements in a dedicated operating model.

View service

Three relevant adjacent paths instead of a long list of further products.

View the overall system

Frequently Asked Questions about ChirpStack

Everything about the LoRaWAN Network Server, operations and our services

TopicsPricing and contract Basics Gateways & Devices Integrations & Data Flows Infrastructure & Scaling Operations & Security WZ-IT Services

Pricing and contract

Basics

Gateways & Devices

Integrations & Data Flows

Infrastructure & Scaling

Operations & Security

WZ-IT Services

Knowledge

More about ChirpStack

Tutorials & guides

Matching solutions for your project

Reviews & projects

Client feedback and projects worldwide

WZ-IT moved our studio infrastructure from decentralised individual devices to a central platform: every site is securely connected via VPN, new devices are onboarded automatically and an entire site is provisioned from a template, without manual steps on location. What impressed me most is the breadth and depth of their knowledge: Timo and Robin are not a typical IT provider who sets up a server and leaves. The two of them think their way into highly complex infrastructure and software topics, work through every requirement we put in front of them, and build networking, provisioning and operations so that everything fits together in the end. WZ-IT is an excellent partner for complex software, network and architecture projects.

Steve KirchnerManaging Director, nextGYM GmbH

View project

International

Built in Germany's Ruhr Valley. Running worldwide.

WZ-IT designs, develops and operates infrastructure and software for clients in Germany and internationally. We deliver projects remotely and continue supporting them in ongoing operations after go-live.

Selected projects

Read client reviews

Managed Hosting & Operations

Enquire about hosting and operations for ChirpStack

Briefly describe the current state and objective for ChirpStack. We assess infrastructure, integration, and ongoing operations.

Straight with Timo and Robin - no sales team, no pitch
A professional assessment of your situation
Concrete next steps for infrastructure, software or AI

The conversation is free and non-binding.

WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.

Jakob ÖschlbergerInno7 GmbH

Email[email protected]Phone+49 2922 875068

WZ-IT's advice on our Azure migration was technically sound and completely non-binding right from the intro call - we took away a great deal.

Jakob ÖschlbergerInno7 GmbH

ChirpStack Hosting in Germany

Class-A Support

Class-B Support

Class-C Support

Adaptive Data-Rate

Multi-Tenant

LoRaWAN 1.0 and 1.1 Compatible

On-Premise

Cloud Installation

Enterprise Setup

VPN Access

SSO Integration

Multi-Factor Auth

Firewall & Hardening

24/7 proactive monitoring

Updates and patches

Daily backup with 7-day retention

Personal technical contact

Payload Codecs (JavaScript)

MQTT & HTTP Integrations

Downlink Logic

What the ChirpStack setup includes

Proprietary Sensor Decoders

Time-Series Bridge (InfluxDB)

Smart Alerting

ChirpStack hosting in Germany: GDPR-compliant operations

Instance sizes and monthly prices

Request a test instance

Installation on Your Infrastructure

Run ChirpStack on hardware at your organisation

Devices, gateways and sites

Secure access

Identity and permissions

ChirpStack platform

Brokers and protocols

Telemetry and storage

Dashboards and business systems

Support custom code and integrations

Connect users, sites and systems

Assess Section 203 requirements separately

Pricing and contract

How much does ChirpStack hosting cost?+

How much compute and storage is included?+

Is the number of users limited?+

What is the contract term?+

Where is the data stored?+

How quickly is ChirpStack ready to use?+

Can I use my own domain?+

Basics

What is ChirpStack?+

What is ChirpStack typically used for?+

What components make up the ChirpStack architecture?+

What infrastructure components does ChirpStack need?+

Gateways & Devices

What role does a LoRaWAN gateway play?+

Do you support setting up LoRaWAN gateways?+

How do I connect a gateway to ChirpStack?+

Which end devices can I connect?+

How are LoRaWAN devices organized in ChirpStack?+

What do I need to create a device (OTAA/ABP)?+

Does ChirpStack support OTAA and ABP?+

How do I test if a device is transmitting correctly?+

Can payloads (sensor values) be decoded directly in ChirpStack?+

Integrations & Data Flows

How does IoT data get from ChirpStack to my cloud/IT systems?+

Can you set up an MQTT broker (including TLS)?+

What MQTT topics/event types are common?+

Do you also handle data processing after MQTT (pipelines)?+

Infrastructure & Scaling

Can ChirpStack be operated in a private network (without public cloud)?+

Do you support building a private network gateway ↔ cloud?+

Can multiple locations/regions be covered with ChirpStack?+

How does ChirpStack scale for many devices?+

Operations & Security

What role do Device Profiles play (and why are they important)?+

What typical errors occur during onboarding?+

How is monitoring/alerting typically implemented for ChirpStack?+

Do you do backups & restore tests for ChirpStack?+

Is ChirpStack enterprise-ready?+

What security measures are common for ChirpStack setups?+