Morning my friends. I’m planning to use ChirpStack as the NS for a commercial product I’m building. However, I’m not too sure about its scalability. My use case will require managing devices and gateways deployed in different locations that relates to different organizations. And one organization may have one location or more. Can the multi-tenant feature ChirpStack has handle this case?
Yes multi-tenant can handle this, but if you only plan on using Chirpstack as a NS, and you have a seperate application you are building above it that the clients interface with, then there you can organize the devices in Chirpstack however is best for you. But if you do plan on letting users interface directly with Chirpstack the multi-tenant features can segregate data by users and prevent clients for accessing other data (they can only see devices and gateways added to that specific tenant, each device or gateway is linked to a single tenant).
The only other consideration is that the Chirpstack gateway bridge only supports a single LoRaWAN region. So if you need to have support for multiple regions you will need to spin up multiple gateway bridges, or else put your gateway bridges on your gateways.
Whatever your use-case there is almost definitely a way to get it done in Chirpstack.
1 Like