Platform / SVH Device Bridge
Connect the fleet you already have.
Some devices can't embed the agent but still need to connect to the platform; others sit on closed networks that can't reach it at all. The SVH Device Bridge runs on site, next to them, and brings every one into the same Zero Trust fleet.
SVH Device Bridge
- Runs on
- The site network, as a container or appliance
- Talks to
- Existing devices; the SVH Fleet Server, outbound only
- You need it if
- Devices are fixed, already installed or on closed networks
- Industries
- Medical devices and Connected devices
- In the device
- Site network
- Fleet Server
- Partner Portal
Translate
Devices that will never run an SVH agent connect in the protocol they already speak — ASTM, POCT1-A2, HL7® v2 over MLLP, or MQTT. Each one becomes its own enrolled device, with its own identity, twin, sync state, and presence.
Relay
Agent devices on closed networks, such as lab VLANs or plant-floor segments, reach the platform through the bridge. The relay is TCP passthrough — mutual TLS stays end to end between device and platform, so the bridge sees only ciphertext and cannot impersonate a device.
Update proxy
The bridge updates itself over the air, and carries signed firmware to translated devices whose protocol can transfer it — bringing them into the same update program.
A new model is a profile, not a release
Each device model is described by a signed driver profile that maps its dialect to platform events. Profiles hot-reload; adding a model on a known protocol needs no new software build.
Admits only what you registered
An administrator pre-registers each device against its bridge by model and serial. Anything else that connects is quarantined and reported, never silently admitted.
Outbound only, managed centrally
The bridge opens no management port. It dials out to the platform, joins with a single-use code, and takes its listeners, relay settings, and allowlist from the server.
At a glance
The numbers your engineers will ask for.
| Device protocols | ASTM E1381 / E1394, POCT1-A2, HL7® v2 over MLLP, MQTT; custom protocols as adapter modules |
|---|---|
| Data flows | Device events, status and faults for any device; for IVD devices also results, QC and calibration runs, orders and host query, operator lists and consumables |
| Identity | Per-bridge sub-CA issued by platform PKI; one enrolled identity per device |
| Relay | TCP passthrough; device mutual TLS stays end to end |
| Connectivity | Outbound only to the platform; no inbound management port |
| Data at rest | Durable per-device outbox; patient data encrypted with AES-256-GCM |
| Storage | SQLite or PostgreSQL |
| Deployment | Rootless container under systemd, or a bootable appliance image |
Bring your installed base online.
Answer six short questions. Within two business days we reply with the path for your device. Then we book a demo with your engineers.