Thousands of sensors, one network
Where a mesh is right for resilience, LoRaWAN is right for scale: many low-power devices reporting through gateways to a network server you control. We design, deploy and run them.
What a LoRaWAN engagement covers
Gateways
Siting, mounting, backhaul and power for the gateways that carry your catchment — indoor, outdoor and solar.
- Coverage-led siting
- Cellular or wired backhaul
- Solar and PoE
Network server
Private and self-hosted, or a public network where that fits. We will tell you which, and what each costs to run over five years.
- Self-hosted or managed
- Join servers and keys
- Roaming where useful
Devices
Selection, onboarding and lifecycle for the sensors themselves — metering, level, environmental, GPS and the awkward ones.
- Vendor-neutral selection
- Provisioning at scale
- Battery-life modelling
Keys and security
Device keys, join procedures and where the root keys live. A network whose keys are on somebody else’s server is somebody else’s network.
- Key custody
- OTAA provisioning
- Payload encryption
Integration
Payload decoding and delivery into whatever you already run — a SCADA system, a database, a dashboard or an API.
- Codec authoring
- MQTT, HTTP and webhooks
- Historian and BI feeds
Operation
Monitoring, alerting and the unglamorous work of noticing a gateway has been quiet for a day. Optional, and never a lock-in.
- Uptime and gap alerts
- Battery-fade reporting
- Firmware campaigns
Mesh or LoRaWAN is a choice, not a religion
They solve different problems. Many sensors in a fixed catchment want LoRaWAN. Resilience with no infrastructure wants a mesh. We are equally happy to build either, which is what makes the recommendation worth something.
How many devices, and over what ground?
Those two answers usually decide the architecture. Tell us both and we will sketch the shape of it.