Secure access and access control for your installation
VPN Access
WireGuard, NetBird or Tailscale
SSO Integration
Keycloak, Authentik, Azure AD
Multi-Factor Auth
TOTP, WebAuthn, YubiKey
Firewall & Hardening
Fail2Ban, Rate Limiting, IP Whitelisting
Secure Access via VPN
We set up secure VPN access to your installation – ideal for remote work and external employees.
Zero-Trust Network Access (ZTNA)
Encrypted connections
Easy client setup for all devices
Centralized access management
Supported VPN Solutions:
WireGuard
NetBird
Tailscale
Headscale
OpenVPN
Cloudflare Tunnel
Perfect for These Use Cases
LoRaWAN Network Server
Complete LoRaWAN network server for IoT gateways and sensors with device management
Smart City & Infrastructure
City-wide IoT networks for parking management, waste disposal and environmental monitoring
Industrial IoT (IIoT)
Industrial sensor networks for machine data, predictive maintenance and production monitoring
Agriculture & Farming
Smart agriculture with soil, weather and plant sensors across large areas
Building Management
Building automation with temperature, humidity and energy sensors
Asset Tracking
GPS tracking and location monitoring for vehicles, containers and valuables
What's Included in the Service
Full-service installation with no hidden costs
✓ 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
Why WZ-IT for Your Installation?
Expertise that moves you forward
Installation Expertise
We have successfully implemented dozens of enterprise installations and know all best practices.
Security First
Comprehensive security hardening following OWASP, including VPN access, firewall configuration and audit logging.
Open-Source Philosophy
We rely on open-source software and avoid vendor lock-in – you retain full control over your data.
Multi-Cloud Expertise
Whether AWS, Azure, Google Cloud, Hetzner or on-premise – we install where you need it.
Personal Support
You get a dedicated contact person who supports you during and after installation.
No Vendor Lock-in
Your installation runs on your infrastructure – you are always independent and can continue operating the solution yourself.
Interested in ChirpStack?
Good choice – we'll help you get started or with operations.
1/2 – Interest50%
Frequently Asked Questions about ChirpStack Installation
Technical details on infrastructure, components and operations
Themen
Installation & Components
We set up the ChirpStack LoRaWAN Network Server including typical core dependencies: ChirpStack, PostgreSQL (persistence), Redis (cache/queue), and in many setups an MQTT broker (e.g., Mosquitto) and the ChirpStack Gateway Bridge component for gateway connectivity.
Both: We install ChirpStack on-prem, in your cloud, or on dedicated hardware. We often also build a private network (VPN/Private Link) between gateways/locations and the ChirpStack environment.
This depends heavily on gateway count, device count, uplink frequency, and payload size. As a rule of thumb: For an initial production setup, we plan separate resources for database (IO/storage), MQTT, and ChirpStack services.
Primarily persistent are: PostgreSQL (configuration, devices, events, metadata), MQTT depending on configuration, and ChirpStack configuration (config files, secrets). We ensure clean persistence via volumes/managed disks.
Infrastructure & Networking
In practice: yes, almost always, because MQTT in the ChirpStack ecosystem is the central messaging layer between components/Gateway Bridge and server (and is also used for integrations).
All three variants are possible: With you (on-prem / in your cloud), with us (managed hosting), or as managed MQTT. What matters is: access control, TLS, credential handling, and clear data flow documentation.
Yes. In the reference setup, 'EU868' is preconfigured, other regions can be cleanly switched. Important here is the region/topic configuration (e.g., topic prefix per region).
ChirpStack typically separates traffic via region prefixes (e.g., eu868, us915_0…). If gateways/forwarders use the wrong prefix, traffic ends up in the wrong context or isn't processed correctly.
Yes – this is often the clean enterprise approach: Gateways/locations send via VPN/Private Network to the ChirpStack infrastructure. This reduces attack surface and provides controllable data flows.
Typical baseline: TLS at external endpoints (reverse proxy/LB), strict firewalling, secret management (no secrets in repo), role/admin concept, separate admin access, logging/monitoring with defined scope.
In quickstart, the UI is locally accessible at http://localhost:8080; in production environments, there's typically a reverse proxy / load balancer with TLS and access controls in front.
Gateways & Protocols
Typical variants: Semtech UDP Packet Forwarder on UDP port 1700 (very common) or Semtech Basics Station by default on port 3001. Which variant you use depends on the gateway (vendor/firmware).
Both are possible: Gateways send via UDP/Basics Station to a Gateway Bridge instance. Alternatively, some setups use MQTT-based forwarders that publish to your MQTT broker (e.g., port 1883).
Yes. We support gateway onboarding end-to-end: provisioning, forwarder variant setup (UDP/Basics Station), connection tests, and documentation of parameters for your operations.
Operations & Scaling
Almost always: PostgreSQL (I/O, backups, restore times), Redis (performance/queueing), MQTT broker (availability/throughput). We design the infrastructure so these components have robust defaults.
At minimum: regular PostgreSQL backups (point-in-time/incremental), defined retention + offsite/second location, regular restore tests. Optional: config backups/secrets and long-term event storage.
We define an update process with: staging/test (if available), maintenance window + communication, rollback options (snapshots/backups). This keeps operations plannable and low-risk.
Yes – but 'HA' here usually means: redundant services, robust DB setup, and clean failover concept. Which HA level makes sense depends on the use case and budget.
Scaling typically happens through: separate resources for DB/MQTT/services, horizontal scaling of stateless components, clean network and storage performance (DB IOPS!).
We offer: installation & secure baseline, operations/monitoring/incident handling, backups/restore tests, updates/maintenance, support for gateways, sensor onboarding, MQTT and data pipeline. In short: We handle infrastructure & operations, you use the IoT data.
Learn More About ChirpStack
Discover all features, use cases and managed hosting options for ChirpStack
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.