17.02.2026
IoT Retrofit for Warehouses: How Businesses in Werl Digitize Logistics with LoRaWAN
Warehouses in the KonWerl business park, in Werl's town center or along the B1 highway - many logistics companies in Werl face the same challenge:...

ChirpStack is an open-source LoRaWAN network server that enables you to build LoRaWAN networks. It provides a web interface for managing gateways, devices, and tenants, along with extensive integrations with major cloud providers, databases, and services for handling device data.

ChirpStack is an open-source LoRaWAN network server that enables you to build LoRaWAN networks. It provides a web interface for managing gateways, devices, and tenants, along with extensive integrations with major cloud providers, databases, and services for handling device data.
With a gRPC-based API, ChirpStack can be seamlessly extended or integrated into your existing systems.
We install, host and operate ChirpStack for your company - either on our secure, GDPR-compliant infrastructure in Germany or other locations, as well as on-premise in your own environment.
With 24/7 monitoring, enterprise support, backups and professional maintenance, we ensure maximum availability and reliable operation of your ChirpStack instance.
Class-A end devices allow bi-directional communication with two short downlink windows following each uplink.
In addition to the random receive windows of Class-A, Class-B devices open extra scheduled receive windows via time synchronization.
Class-C end devices maintain nearly continuous receive windows, minimizing latency at the expense of higher power consumption.
Ensures optimal data rate and transmission power to save energy and improve radio spectrum utilization.
Supports multiple organizations, ensuring that users see only their own data.
Supports both LoRaWAN versions simultaneously, including all regional parameter specifications.

See how simple and efficient ChirpStack works in practice. From installation to productive use.
Professional installation on your infrastructure – on-premise, cloud or hybrid
In your data center
AWS, Azure, Hetzner & more
High-availability setup with comprehensive security and compliance features
Secure access and access control for your installation
WireGuard, NetBird or Tailscale
Keycloak, Authentik, Azure AD
TOTP, WebAuthn, YubiKey
Fail2Ban, Rate Limiting, IP Whitelisting
We set up secure VPN access to your installation – ideal for remote work and external employees.
Full-service installation with no hidden costs
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.
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.
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.
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').
How we implement ChirpStack development in practice.
You use specialized sensors or in-house developments for which there is no standard profile in ChirpStack.
Reverse engineering of the byte payload and development of an efficient JavaScript codec according to manufacturer specifications.
Sensor data should be stored for long-term analysis, but ChirpStack only stores short-term.
A Go/Python service that listens to the MQTT stream and writes optimized data to InfluxDB or TimescaleDB – ready for Grafana.
Alarm on threshold violation, but please not with every single packet (debouncing).
Middleware logic that analyzes the data stream and only alerts if a value remains critical for X minutes (hysteresis).
Open source enterprise-ready for productive workloads - we run your applications with highest security standards and enterprise support
Open source software for business-critical processes requires professional maintenance, continuous updates, and enterprise-grade support. With our ChirpStack Enterprise Managed Hosting, you get the necessary infrastructure and support to reliably operate open source in production environments. Backups, SLAs, telephone support, and personal contact - so you can focus on your core business.
We also offer customized ChirpStack Enterprise solutions for your specific requirements. Contact us for an individual quote.
Good choice – we'll help you get started or with operations.
Monitor your infrastructure in real-time, schedule maintenance and get direct support – all in one central portal.

Production-ready ChirpStack hosting with professional support. merkaio accompanies you as a partner throughout your entire LoRaWAN project.
Discover ChirpStack HostingEverything about the LoRaWAN Network Server, operations and our services
Themen
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.
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).
Typically: Gateway Bridge, ChirpStack (Network Server + Web UI), and backend components (e.g., PostgreSQL, Redis, MQTT Broker).
In standard setups, ChirpStack uses PostgreSQL (persistence), Redis (caching/state), and an MQTT broker for messaging/integrations.
The gateway is the radio bridge between your LoRaWAN end devices and the server stack. It forwards LoRaWAN frames to ChirpStack (and downlinks back).
Yes – we set up gateways, connect them to ChirpStack, and test the radio link (gateway ↔ device), including proper documentation and acceptance testing.
Basically: Create the gateway in ChirpStack, configure the forwarder/station, verify connectivity, and validate LoRaWAN frames.
All LoRaWAN-compatible sensors/trackers/modules, provided the region/parameters and activation (OTAA/ABP) match and the necessary identities/keys are available.
ChirpStack works with Device Profiles (capabilities/versions/region params) and Applications (logical grouping of devices by use case).
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.
Yes. In practice, OTAA is usually standard (better key handling/provisioning), ABP is used depending on device/use case.
In ChirpStack, you can check LoRaWAN frames and device events (JoinRequest/JoinAccept, uplinks, etc.).
Yes: Device Profiles can reference a payload decode function to transform raw data into usable values.
Typically via MQTT (events/topics), alternatively via APIs/integrations. MQTT is a central integration pattern in ChirpStack.
Yes – we set up the MQTT broker properly (TLS, credentials, permissions/topics), connect ChirpStack, and provide clear documentation of data flows.
ChirpStack publishes events like Uplink, Join, etc. – and tools like Node-RED can subscribe to and process these events.
Yes – e.g., forwarding to databases/time series, dashboards, alerting, or to your business systems. Common components: Node-RED, workers/streams, TSDB, data lake.
Yes. ChirpStack is suitable for self-hosted setups – on-prem or in a private/isolated cloud environment, including controlled network segments and data flows.
Yes – we plan and build secure connectivity (e.g., VPN/S2S, segmented networks, firewall rules) so gateways reliably and securely communicate with ChirpStack.
Yes – depending on architecture/provider/network design (e.g., multiple gateway locations, central processing, separate environments).
Scaling typically happens through: broker/DB performance, horizontal components, clean topic structure, backpressure, and capacity planning.
They prevent chaos: Profiles bundle LoRaWAN version/region parameters/activation/decoder and ensure device groups remain consistent and operable.
Classics: wrong DevEUI/keys (MIC errors), wrong region/parameters, gateway config, frame counter issues.
Via metrics/logs from components (ChirpStack, DB, Redis, broker) and infrastructure monitoring. Goal: detect drops/backlogs early before uplinks disappear.
Yes – especially for PostgreSQL (configuration/state), plus robust backup strategy and regular restore checks.
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).
TLS wherever possible, least privilege, separate service accounts, network segmentation, secrets handling, update policy, logging/auditing, and documented data flows.
Yes – we handle operations, updates, monitoring, backups, incident response, and performance tuning as managed hosting / managed operations.
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).
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 installation page.
17.02.2026
Warehouses in the KonWerl business park, in Werl's town center or along the B1 highway - many logistics companies in Werl face the same challenge:...
15.02.2026
Münster is a city of science. The University of Münster, the Münster University of Applied Sciences, the University Hospital and numerous research institutions form a...
03.02.2026
IoT projects face a central challenge: Which components are needed for a functional IoT stack? From the sensor layer to data collection and visualization, various...
These solutions are often used together with ChirpStack
These solutions offer similar functionalities and can be evaluated together
Whether a specific IT challenge or just an idea – we look forward to the exchange. In a brief conversation, we'll evaluate together if and how your project fits with WZ-IT.
Timo Wevelsiep
Lead IoT Solutions Architect

