One gateway, large-site coverage
A single LoRaWAN gateway can cover a large site, where short-range approaches need more gateways as distance or obstruction increases. The radio comparison is made per competitor, not assumed.
Tank farms · pump stations · outdoor and mobile equipment
Monitor equipment kilometers from the control room — without a wiring project
Open LoRaWAN sensor ecosystem, single-gateway site coverage and health scoring even where cellular and wiring aren't practical.
1gateway, kilometres of site coverage
Built for the maintenance lead at a remote site
The challenge
Built for the maintenance lead at a remote site.
- Tank farms, remote pump stations and mobile or outdoor equipment are often too costly or physically impractical to wire for condition monitoring.
- Cellular coverage at remote sites is inconsistent, and power for continuous wired sensors may not exist.
- Closed wireless ecosystems lock the customer into one vendor's sensors and gateways.
How the system solves it
Only the capabilities that apply to this use case.
- 01
LoRa sensors
Battery · open ecosystem · km range
- 02
Single gateway
LoRaWAN · one site coverage cell
- 03
Entry IPC + ChirpStack
Local store · health scoring on edge
- 04
Your stack
OPC UA · MQTT · Modbus · HTTPS
Raw waveform depth traded for range — physical I/O optional · cloud fleet view is opt-in only
- LoRaWAN / ChirpStack variant
- Real-time summary metrics and AI health scores over an open radio standard, with the network server running on the edge IPC.
- Open sensor choice
- Sensor selection is not locked to a single vendor's catalogue. Validated sensor models are confirmed per project before commitment, so you know exactly what is supported.
- Honest trade-off
- Raw waveform capture is constrained and physical I/O is optional on this variant. It trades some depth for range and power efficiency, and we say so up front — it is not full parity with wired.
- Same platform as wired
- Health scores, HTTPS HMI, RBAC and northbound OPC UA / MQTT / Modbus / HTTPS egress behave identically to the wired variant.
Why it wins here
Architectural differences, not slogans.
One system for a mixed fleet
Because the edge platform is shared with the wired variant, a mixed-fleet site does not have to learn and support two different systems.
No mandatory cloud subscription
The gateway stores and evaluates data locally. Cloud fleet dashboards are opt-in, priced per sensor per year, not a condition of operation.
Deployment path
Variant
Wireless / LoRaWAN-ChirpStack
Hardware tier
Entry-tier IPC as local gateway and aggregator
Why
Wireless assets send periodic metric frames rather than continuous streams, so an entry-tier IPC handles a substantial sensor count within one enclosure.
Proof & validation
Range and sensor count, measured at a real site
A field pilot records the coverage radius and the number of sensors a single gateway sustains before any figure is quoted. The tested configuration — gateway placement, sensor models and message cadence — is published with the result.
Explore the other use cases
Rotating equipment PdM
Catch bearing failures weeks before they cause downtime
Read use caseMachine protection & interlocks
Trip the machine before damage happens — deterministically, locally
Read use caseMulti-site fleet standardization
One condition-monitoring platform, right-sized for every site in your fleet
Read use caseBrownfield retrofit
Add condition monitoring without ripping out what's already there
Read use case