An isolated ChirpStack tenant, per instance
Each instance is its own ChirpStack tenant on a shared, monitored cluster in the region you choose. You get a console login, a gRPC API endpoint and gateway ingress endpoints as soon as it’s provisioned. Instances can be started and stopped from the dashboard; a deleted instance is retained for 30 days before it’s permanently removed, so an accidental deletion is recoverable. The ChirpStack version is managed at cluster level, so every instance runs a tested, pinned release and upgrades are handled for you.
Connect gateways the way ChirpStack expects
Gateways connect over Basic Station with mutual TLS, using a per-gateway client certificate issued from the cluster’s private CA – only gateways you’ve registered can reach your network. Semtech UDP is also supported for gateways that need it. Each cluster serves multiple radio regions from a single host, with EU868, US915 and AU915 available today. Register device profiles, applications and devices in the standard console, and use ChirpStack’s built-in integrations to push uplinks into your own systems.
Choose where your network lives
Clusters run in Europe (London) and North America (New York). Pick the region closest to your gateways for the lowest latency, and keep your data in the jurisdiction you need. Pricing is set per region, in your team’s currency, and is shown before you create an instance.
Built for teams, not single logins
Everything belongs to a team. Invite colleagues by email and assign one of three roles: Owners have full control, Admins can do everything except delete the team or manage members, and Viewers are read-only. The interface only shows what a role is allowed to do, and every instance and billing action is written to an append-only, team-scoped audit log that owners and admins can review at any time.
Predictable, per-instance pricing
Each instance is billed monthly at a fixed price that includes a device allowance; devices beyond the allowance are metered at a per-device rate. The price you signed up at is frozen to your instance, so changes to the public price list never affect existing customers. Invoices are issued in your team’s currency, VAT is calculated correctly for UK and EU customers (including reverse charge on verified EU VAT numbers), and payment is by card, stored securely with Stripe. Running and stopped instances are billed; instances still provisioning are not.
Your first instance is free to evaluate
Create your first instance without entering payment details and run it for a full evaluation period. Add a card before it ends and the instance simply continues; let it lapse and it stops, with nothing charged. One evaluation is available per customer.
Operated with the discipline an LNS needs
Every cluster is deployed from the same tested template with exact-pinned software versions and a dedicated managed PostgreSQL database. Public endpoints use Let’s Encrypt certificates with automated renewal; gateway connections use a separate private CA. The API is protected by ChirpStack’s own authentication with IP allow-listing as a second layer, and the internal MQTT broker is never exposed publicly. Automated checks continuously verify service health, TLS validity, API reachability, image integrity and certificate expiry, with alerts routed to our on-call. Secrets are never stored alongside configuration. Upgrades are planned, tested against the same template and announced in advance.
Already running ChirpStack?
ALPHi runs the same software, so migration is a matter of exporting your device profiles, applications and devices from your existing instance, importing them into your ALPHi tenant, and repointing your gateways to the new ingress endpoints. If you’d like help planning the switch, get in touch.
Start with one instance
Create a team, create an instance, connect a gateway. If it does what you need, add a card; if not, walk away.