Industries / Energy devices
Distributed assets with a verified identity and safe updates
For makers of meters, chargers, inverters, controllers and monitoring units installed in the field for years. Each asset proves who it is, receives signed updates in waves and reports back reliably over whatever link it has. Your customer operates the fleet in a console with your brand.
A fleet console in the device maker's brand: devices online, an update rolling out in waves and a live heartbeat.
- Hardware-rooted identity per asset
- Updates in waves across a wide-area fleet
- Data delivered over intermittent links
- Audit trail and SBOM for every release
How your devices connect
Two ways in, one fleet. Devices that can run the agent do; everything else connects through the bridge.
- EV chargers
- Inverters and battery systems
- Smart meters and gateways
- Substation and grid controllers
- Solar and wind monitoring units
- Water and gas monitoring
SVH Device Agent
Chargers, inverters, gateways and controllers on embedded Linux run the SVH Device Agent with a hardware-rooted identity.
Hardware-rooted identity, an offline queue, signed updates and a sandbox for your application.
SVH Device Bridge
Meters and legacy controllers behind a site gateway connect through the SVH Device Bridge, over MQTT today or a custom adapter scoped with you.
No firmware change. The bridge carries their data to the Fleet Server over mutual TLS.
What your customer sees
A console in your brand, on their premises or in your cloud.
- Every asset by region, site and feeder, with live status
- Firmware version and update history per asset
- Faults and alarms with remote commands, every action audited
- Settings inherited from the product line down to one asset
What their systems receive
Signed webhooks and documented REST APIs, so device data lands where they already work.
- SCADA, EMS and historians
- Measurements and events, in order, with gaps filled after an outage
- Billing and asset management
- Signed webhooks for usage, faults and service events
- Your own apps
- Documented REST APIs for the whole fleet
What it solves for energy devices
Three problems every device maker in this industry runs into, and how the platform handles them.
Assets in the field for 15 years
Identity is rooted in hardware and certificates renew automatically. Version floors stop an old unit from being downgraded to a vulnerable release.
A fleet across a whole region
Rollouts go in waves by region or model, pause on failures and roll back on their own. Data is buffered over cellular or satellite gaps.
Security questions from every utility
Mutual TLS on every connection, an SBOM with every release and a tamper-evident audit trail answer the questionnaire before it arrives.
Questions energy device makers ask
How does an asset prove its identity?
Each unit carries a birth certificate installed in your factory and, where available, a TPM. On first contact it is enrolled and receives an operational certificate that renews automatically.
Can we run the Fleet Server in our own cloud?
Yes. On premises, your cloud or hosted by SVH run the same platform, and an installation can move between them.
Our meters speak a utility protocol. Can they connect?
Through the SVH Device Bridge. It speaks MQTT today; other protocols are built as an adapter, scoped with you on the first call.
Making something else? The Connected devices page covers every device the platform runs.
Can SVH connect your assets?
Answer six short questions. Within two business days we reply with the path for your device. Then we book a demo with your engineers.