TECHNICAL BRIEF / ARCHITECTURE

Edge-first, cloud-synced.

DYNVOLT runs on embedded Linux nodes deployed at every site. They poll Modbus TCP every 30 seconds, persist locally, and stream to the cloud when connectivity allows. Your plant keeps trading even when the internet doesn't.

0
Inbound ports at the edge
30s
Modbus poll cadence
14 days
Offline buffer
TLS 1.3
All transport
SYSTEM TOPOLOGY

Three planes. One platform.

EXTERNAL · MARKETS & OBSERVERSEuropean power marketsDAY-AHEAD · INTRADAY · IMBALANCE — BIDS SUBMITTED BY YOU OR YOUR BRPPARTNERSTSO · BRP · OFFTAKER · AUDITORSCLOUD · CONTROL PLANETIME-SERIES STOREcolumnar · downsampled7-year retentionAI FORECASTERmulti-NWP · site-trainedP10 · P50 · P90DISPATCH ENGINEarbitrage · imbalancewarranty-boundedALERT & TICKETpeer-relative rulesauto-resolvingREPORTSdaily · settlePDF · XLS · APIEDGE · ON-SITE · MODBUS TCP / MQTT · 30s POLLINGDYNVOLT EDGE NODEembedded · debian · 30-second polling · 14-day local buffer · deterministic latency● EDGE-FIRSTsigned updates<50ms POLLPHYSICAL · PLANTINVERTERSPER-STRINGBESSCOMMISSIONINGPCC METERREVENUE GRADEWX STATIONSPOA/T/WTRANSFORMERSMV / HVTRACKERSSCADA-AWARESENSOR NODESMQTT · LWT
DESIGN PRINCIPLES

What we built. And why.

Edge-resilient by default

A 14-day local buffer keeps every reading durable. When connectivity returns, the cloud catches up — gap-free. No data loss on WAN outages.

L

Latency-bounded control

Set-point write-back happens at the edge, not via a cloud round-trip — no WAN in the control path, so curtailment and export limits keep working when the link drops.

S

Security-hardened

TLS 1.3, mTLS device attestation, and role-based access on every API. Network-isolated edge by default.

O

Open at the seams

Modbus TCP and MQTT in production, plus a REST API you can integrate with your CMMS or ERP. More protocols on the roadmap — stated honestly on the integrations page.

U

Upgrade-safe

Edge nodes self-update over signed channels. Roll-back automatic on health-check failure.

Get a tailored architecture review.

A 30-minute call with our solutions team — walk through the edge runtime, security model, and a deployment plan sized for your fleet.

Request a demoSee custom edge hardware →
FAQ

Architecture — frequently asked

Can't find what you're looking for? Talk to our team →

What happens if the edge node fails?
The edge is autonomous by design — control loops, alarms and the export limit run locally, and a 14-day buffer plus encrypted off-site backups mean history survives hardware failure. Recovery is a re-provision from signed configuration, not a rebuild.
What data leaves the plant?
Only the time-series payload your tenancy is configured for, over outbound-only encrypted tunnels — the edge accepts no inbound connections. PII never leaves the device.
How is the platform updated?
Edge nodes pull GPG-signed update channels with signed configuration envelopes, and roll back automatically on health-check failure. Cloud is rolling-deploy with zero downtime.
What protocols are supported?
In production: Modbus TCP/RTU and MQTT. On the roadmap, stated honestly as such: OPC-UA, IEC 61850, DNP3, and IEC 60870-5-104 delivered as a project build to your operator's specification. Plus REST and webhooks for your own systems.
Is the platform multi-tenant or single-tenant?
Multi-tenant by default, with a central identity provider, per-tenant entitlements, and hash-chained audit logging. Single-tenant and on-prem arrangements are a conversation, not a checkbox — ask us.