Built because we’d run one ourselves
ChirpStack is excellent software, and self-hosting it is entirely doable. It is also a recurring chore: TLS renewals, MQTT broker configuration, gateway certificate management, database backups, version upgrades and monitoring, all for a component that is essential but rarely the point of the project. ALPHi was set up to take that work on, using the standard ChirpStack release, with the operational discipline it needs to be relied upon.
Run the way we’d want it run
Every cluster is stamped from the same tested template, runs exact-pinned software versions, and is verified continuously – service health, TLS validity, API reachability, certificate expiry and image integrity. Upgrades are planned and announced rather than surprising. Secrets are never stored beside configuration, gateway ingress is protected by mutual TLS, and the platform records every instance and billing action in an append-only audit log.
That gives you:
- A standard ChirpStack you already know how to use.
- Isolation per instance, with your own console, API and endpoints.
- Transparent, snapshot-based pricing that never changes underneath you.
- Clear ownership of the infrastructure, so you own the network.
For teams that build on LoRaWAN
ALPHi is for integrators, product companies and in-house teams deploying LoRaWAN at any scale, from a handful of gateways on a single site to multi-region estates. If you’re evaluating ChirpStack, migrating from a self-hosted install, or replacing a network server that’s become someone’s unofficial second job, we’d like to hear from you.
Try Before You Commit
Your first instance runs on an evaluation period with no payment details required. Add a card when you're ready to keep it, or simply let it lapse. If you have questions about regions, migration from a self-hosted ChirpStack, or gateway setup, get in touch and we'll give you a straight answer.