Protocol adaptors
DLMS/COSEM, Modbus and MQTT with pluggable SDK to onboard additional sources.
Meter readings arrive from different devices, at different times and in different formats. IoT Metering Gateway validates, deduplicates and buffers that data before handing normalized records to settlement, billing and analytics.
Start with the interfaces already present at your sites: meters, sensors, PV equipment, home controllers and EV chargers.
Collection ends with a record another system can use. Validation rules, queues and normalized payloads define what happens before that handoff.
DLMS/COSEM, Modbus and MQTT with pluggable SDK to onboard additional sources.
Schema checks, deduplication, late/missing read handling and outlier rules.
Queueing, retries and dead-letter channels keep data flowing without overload.
Unified payloads for settlement/billing, portals and analytics (time-series + columnar).
SLIs/SLOs, tracing and dashboards for throughput, latency and quality.
Events/webhooks, query APIs and batch exports for settlement and BI.
From field devices to back‑office systems - mapped to a clean, normalized model.
Electricity & heat meters with pulse/serial gateways
Temperature, humidity, pressure and custom telemetry
String & hybrid inverters, production & status
Grenton & other gateways (scenes, relays, inputs)
OCPP‑enabled wallboxes and DC chargers
Modbus RTU/TCP slave networks in buildings
The gateway owns collection and preparation of the reading in a Kubernetes-native pipeline. Settlement, billing and forecasting consume its output and apply their own business rules. Agree the interfaces at those boundaries.
For each metering source, define the protocol, reading identifiers and timestamps. The adaptor connection uses the supported transport and access controls.
Decide how invalid, late or missing readings reach review and reprocessing. Queues and dead-letter handling keep those cases visible before the record is used downstream.
Choose the normalized payload, northbound API, mapper or batch export consumed by settlement, billing or analytics. That receiving system owns the calculation or decision that follows.
Different deployments consume the same prepared readings for different operational purposes.
Smart meters feed validated reads into the settlement engine and billing.
PV/storage telemetry normalized for analytics, alerts and cost allocation.
Meter/household data exposed to self-service portals and BI dashboards.
Operate the collection boundary with transport security, controlled access and an auditable exception process.
TLS/mTLS, rotated certificates, cipher policy
OIDC/OAuth2, scoped tokens and per‑tenant quotas
Encryption at rest, WORM retention and legal hold
Structured logs, traces and SLO dashboards
Queueing, back‑pressure, retries and dead‑letter review
Audit trail and export for regulators
Selected deployments and partnerships.


Trace a sample reading through its validation result, exception handling and downstream payload.
Talk to an expertSee how the gateway feeds settlement, billing and portals.
Explore the platformExplainable forecasts and anomaly detection on normalized data.
See analyticsDLMS/COSEM, Modbus TCP/RTU and MQTT brokers out of the box. The adaptor SDK supports integration of additional sources.
Validation and deduplication at ingress, rules for late/missing reads and outliers, reprocessing flows with audit lineage.