Industries / Industrial devices
Every machine you ship, one fleet your customer can run
For makers of machines, controllers, test stands and production equipment. Each unit gets a verified identity, signed updates rolled out in waves, and settings managed per plant, line and machine. Your customer gets a console in your brand, on their own network.
A fleet console in the device maker's brand: devices online, an update rolling out in waves and a live heartbeat.
- Runs on the plant network, no internet needed
- Signed updates in waves, with rollback
- Settings per plant, line and machine
- Machine data to MES, ERP and historians
How your devices connect
Two ways in, one fleet. Devices that can run the agent do; everything else connects through the bridge.
- CNC and machine tools
- Packaging and filling lines
- Test and inspection stands
- Compressors and pumps
- Industrial controllers
- Robots and cells
SVH Device Agent
Machines with an embedded-Linux controller or HMI run the SVH Device Agent next to your application.
Hardware-rooted identity, an offline queue, signed updates and a sandbox for your application.
SVH Device Bridge
Older machines and PLC-based equipment connect through the SVH Device Bridge on the plant network, 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 machine by plant, line and cell, with live status
- Firmware and software version per machine, and who approved each update
- Settings inherited from the product line down to one machine
- Faults and remote commands, with an audit trail of every action
What their systems receive
Signed webhooks and documented REST APIs, so device data lands where they already work.
- MES and historians
- Machine events and measurements, in order, with gaps filled after an outage
- ERP and CMMS
- Signed webhooks for faults, counters and service events
- Your own apps
- Documented REST APIs for the whole fleet
What it solves for industrial devices
Three problems every device maker in this industry runs into, and how the platform handles them.
Plants without internet
The Fleet Server runs on premises. Devices buffer data while a line is isolated, and updates and licenses arrive as signed bundles.
One bad update stops a line
Rollouts go in waves, pause on failures and roll a failed machine back on its own. Version floors stop downgrades.
Every plant is configured differently
Settings live in layers: your defaults, the model, the plant, the machine. Change one layer and every machine below it follows.
Questions industrial device makers ask
Does it need a connection to the cloud?
No. An on-premises Fleet Server runs the plant fleet without internet. Updates and licenses reach it as signed bundles, applied by your customer.
Our equipment uses a PLC, not Linux. Can it connect?
Yes, through the SVH Device Bridge. It speaks MQTT today; other protocols are built as an adapter, scoped with you on the first call.
Can plant IT keep control of the network?
Yes. Devices connect outbound only to the Fleet Server, over mutual TLS, and the server exposes two ports: one for devices, one for people and apps.
Making something else? The Connected devices page covers every device the platform runs.
Can SVH connect your machines?
Answer six short questions. Within two business days we reply with the path for your device. Then we book a demo with your engineers.