Our solution
One platform for every layer of your IoT stack.
Divako spans the full chain - from the device in the field to the line in your billing system, dashboard or SCADA. Five layers that work on their own and even better together.
01 · Hardware
Bring any meter, sensor or gateway.
Divako isn't tied to a specific manufacturer. Our product database carries validated device profiles, payload parsers and alarm definitions for hundreds of meters - from LoRaWAN water meters to DLMS electricity meters to industrial Modbus sensors.
That means installation is predictable, provisioning is bulk-friendly, and you never start from a blank page when a new device lands on a rollout.
- Hundreds of pre-validated device profiles
- Versioned payload parsers with alarm mapping
- Bulk provisioning by EUI, CSV or API
- Field-installation flow integrated with DriveBy
02 · Network
Operate every radio, from one console.
Coverage rarely fits one protocol. Divako lets you run LoRaWAN, wM-Bus and NB-IoT together - same devices, same data pipeline, same operations team. Add DriveBy where no network can reach, and feed it through the same funnel.
Gateway health, RSSI, packet loss and coverage gaps show up as alerts, not as 3am phone calls.
- Multi-protocol gateways and bridges
- Live coverage maps and RSSI heat layers
- Automated Drive-By collection with offline sync
- ChirpStack, Kamstrup, OPC UA and more - native
03 · Data
Every payload, one schema.
Raw payloads come in a dozen formats. Consumption data shouldn't. Divako parses every message against the device profile, checks ranges, gaps and duplicates, and emits a single harmonised measurement - with unit, timestamp and quality flag attached.
From there, every downstream job - trends, balancing, billing exports - is the same regardless of the meter underneath.
- Payload parsing with validation & replay
- Range, gap and duplicate checks on ingest
- Units, timestamps and quality harmonised per profile
- Historic series with downsampling and export
04 · Analyze
From readings to answers.
A clean measurement is the starting point, not the finish. Divako watches every series for what matters in the field - a slow leak, a burst, reverse flow, a meter quietly drifting out of spec - and turns it into an alarm before it shows up on a bill.
Validation runs per device, not per fleet, so the rules that fit a DN15 apartment meter never get applied to a DN200 trunk main.
- Continuous leak, burst and backflow detection
- Water-loss & non-revenue water balancing by zone
- Per-device validation rules and drift detection
- Alarms routed to email, SMS, push and webhooks
05 · Connections
Open APIs, native connectors.
The Divako UI runs on the same APIs your team can. REST for request/response, MQTT for streams, webhooks for events, SFTP for batch. Everything versioned, rate-limited, documented - and covered by an SLA.
Native connectors handle the long tail: billing systems, SCADA, ERP, BI, data warehouses, resident portals. If it needs metering data, there's a path.
- REST, MQTT, webhooks, SFTP
- Native connectors for billing, SCADA, ERP
- Role-based access, SSO/SCIM, full audit log
- SDK examples in Go, PHP and TypeScript
Get started
See the platform end to end.
30 minutes. We'll walk the pipeline from a physical meter to a live billing export, with your data if you want.