Private vs. Public Gateway
The deployment distinction that affects cost, control, and data ownership.
One product, two deployment models
Vandyam's catalogue and website describe one physical VIoT Gateway product — there is no separate "Private Gateway" and "Public Gateway" SKU with different hardware. "Private" and "Public" describe how a LoRaWAN gateway is deployed and which network server it reports to, not a difference in the device itself.
This is the most important conceptual distinction for anyone deploying a VIoT Gateway. The distinction is about which LoRaWAN network server the Gateway is registered to and who controls that server — not a difference in the Gateway hardware itself.
Private Gateway Deployment
In a private deployment, the VIoT Gateway is registered to a network server instance that belongs entirely to the customer (or is run by Vandyam on the customer's behalf) — typically a dedicated ChirpStack instance, since that's the platform the Gateway is built to support. All data from every node passing through that Gateway stays within infrastructure the customer controls. This is the natural choice for industrial sites, defence installations, or any deployment where data sensitivity, security, and predictable performance matter more than sharing infrastructure cost with other users. There is no per-message or per-node subscription fee to a third-party network operator — once the Gateway and server are set up, ongoing costs are the customer's own hosting/maintenance costs rather than a recurring network fee.
Public Gateway Deployment
In a public (or "operated") deployment, a Gateway connects to a shared network server operated by a third party — typically a telecom operator or a community network — and that operator's infrastructure is shared across many customers' devices. This avoids the cost and effort of standing up dedicated server infrastructure, and can make sense for smaller deployments or proof-of-concept projects where public LoRaWAN coverage already exists in the area.
Not yet a confirmed offering
Vandyam does not currently document offering a public/shared network service of its own — this reflects the general LoRaWAN industry concept rather than a confirmed Vandyam offering. Route customers asking about a public deployment option to a direct conversation with the team.
Which to Choose
| Data Ownership | Private: customer-controlled | Public: shared with network operator |
| Setup Effort | Private: requires standing up/configuring a network server | Public: minimal, if coverage already exists |
| Ongoing Cost Model | Private: infrastructure/hosting cost only | Public: typically a per-device or per-message operator fee |
| Best Fit | Private: industrial, defence, sensitive-data deployments | Public: pilots, small deployments, areas with existing public coverage |
| Vandyam Offering Status | Private: supported today via ChirpStack | Public: not currently a documented Vandyam offering |