Deployment
Managed cloud, on-premise or hybrid — on your own gateways, a public operator’s, or both. The same platform in every case, so the choice follows your data rules and coverage needs, not our product catalogue.
Decision 1 · Hosting
Three hosting models, one platform. Moving between them later is a supported path, so the first choice does not lock you in.
We host, monitor and maintain the network server. The fastest route from pilot to production with no infrastructure to run.
The full network server inside your own data centre or private cloud. Device keys, payloads and subscriber data never leave your infrastructure.
Keep sensitive workloads on-premise while using managed cloud capacity for scale, redundancy or regional coverage.
Decision 2 · Network
LoRaWAN runs in unlicensed spectrum, so owning your network is a real option — not just something for mobile operators. Many deployments end up mixing both.
You install and own the gateways. Full control of coverage, capacity and data, with no per-device connectivity fees. The usual choice for utilities and industrial sites.
Devices connect through a LoRaWAN network run by an operator. Nothing to install, but you depend on their coverage and typically pay per device.
Your own gateways where density and control matter, public coverage filling the gaps. Roaming lets one device move between the two.
Rollout
Large deployments fail when they skip straight to scale. Each stage below produces evidence the next one depends on.
Device count, uplink frequency, sites and data-residency rules. We plan gateway placement against your real terrain rather than a headline range figure.
A handful of gateways and devices. Confirm coverage in the difficult spots, validate payload decoding, and connect data to one downstream system.
A representative area at meaningful scale. Measure read success and battery behaviour, and run the billing or operations workflow end to end.
Phased rollout with bulk provisioning, device profiles per meter model, and gateway health monitored centrally as the fleet grows.
Comparison
The honest trade-offs: control and compliance on one side, operational simplicity on the other.
| Criterion | Managed Cloud | On-Premise | Hybrid |
|---|---|---|---|
| Where data resides | Our managed infrastructure | Entirely within your own network | Split by tenant, region or sensitivity |
| Who operates it | Our team | Your team, with our support | Shared responsibility |
| Time to first device | Fastest | Depends on your provisioning | Cloud first, on-premise in parallel |
| Data residency compliance | Depends on region | Full control | Full control for sensitive tenants |
| Infrastructure to maintain | None | Servers, backups, monitoring | Only the on-premise portion |
| Typically suits | Pilots, integrators, utilities without a platform team | Government, defence, regulated utilities | Multi-region or phased rollouts |
Which to choose
The decision is rarely technical. It is usually settled by whether procurement or a regulator allows subscriber data to leave your infrastructure. If not, on-premise is the answer and everything else follows.
If residency is not a constraint, managed cloud is almost always the right start: no infrastructure work, a pilot running quickly, and a supported path to on-premise later.
Hybrid suits operators with several regions or business units, where one tenant has strict residency requirements and the others do not — or as a staged migration.
Trial access is available on request for any of the three models.
Any standards-compliant LoRaWAN gateway connects. Keep the hardware you already have, or buy on price and availability.
Devices can move between your network and partner networks without re-provisioning — useful for assets that travel.
MQTT, HTTP webhooks and a REST API move data into billing, GIS or analytics, whichever model you deploy.
Class A, B and C devices, OTAA and ABP activation, and IN865 and EU868 regional plans.
FAQ
Yes. Many operators start with managed cloud to get a pilot running quickly, then move on-premise once procurement or data-residency requirements are confirmed. It is a supported migration path rather than a rebuild.
For a private network, yes — you own and site the gateways, which gives you full control of coverage and no per-device connectivity fees. Where a public LoRaWAN operator already has coverage, you can use it instead, or combine both in a hybrid network.
The platform is vendor-agnostic: any standards-compliant LoRaWAN gateway can connect. You can reuse gateways you already own or choose on price and availability.
Yes. Passive roaming lets devices move between your network and partner LoRaWAN networks without being re-provisioned, which is particularly useful for assets that travel between sites.
They are two separate decisions. Hosting is where the network server software runs — managed cloud, your own data centre, or hybrid. Network ownership is who owns the radio gateways — you, a public operator, or both. You can, for example, run the server on-premise while using a public operator’s gateways.
Trial access is available on request for any of the three hosting models. Tell us your device count, region and timeline and we will set up an evaluation suited to your deployment.
Tell us your device count, region, data residency requirements and timeline. We will recommend a hosting and network model — and be straight with you if we are not the right fit.
Or call +91 9567060033
