One platform, from the device to your customer's systems
Four products, each with a place: an agent in the device, a bridge on the site network, a Fleet Server for each site, and a partner portal at SVH. Every connection between them is mutually authenticated.
A fleet console in the device maker's brand: devices online, an update rolling out in waves and a live heartbeat.
- Agent written in Rust
- Mutual TLS on every connection
- Offline-first data delivery
- On premises, your cloud or hosted by SVH
Where it runs
Four products, each with one place to run. Your customers see your brand on every screen; SVH stays behind it.
-
Partner back office, run by SVH
SVH Partner Portallicenses, birth certificates, signingYou, the device makerrequest licenses, release updatessigned bundle, applied offline · no live link from the portal
-
In your device
Your device appnever touches the networkSVH Device Agenthardware identity · offline queue · signed updates · Agent App APImutual TLS to the Fleet Server
-
On the site network
Devices already in the fieldno agent, no firmware change · ASTM · HL7 · POCT1 · MQTTSVH Device Bridgetranslates their protocol · relays closed networksmutual TLS to the Fleet Server
-
SVH Fleet Server · on premises, your cloud or hosted by SVH
SVH Fleet ServerFleet, certificates, device sync · Updates, configuration, licensing · Data pipeline and audit · consoles in your brand -
Your customer's systems
Business and clinical systemswebhooks · FHIR · HL7Your own appsopen REST APIsAdmins and operatorssingle sign-on
- In your device
- The SVH Device Agent gives it an identity, queues data offline and applies signed updates.
- On the site network
- The SVH Device Bridge connects devices that run no agent, in the protocol they already speak.
- SVH Fleet Server
- One per customer site. Fleet, updates, data and integrations, with consoles in your brand.
- Partner back office
- The SVH Partner Portal issues licenses and certificates. It reaches sites only through signed bundles applied offline.
Four products
Each has one place to run, and nothing else is needed in between.
- SVH Device Agent In the device
- A hardened, memory-safe agent that gives any embedded-Linux device a hardware-rooted identity, offline-first data delivery, safe updates and a local API your device app connects through.
- SVH Device Bridge On the site network
- Brings devices that run no agent into the fleet in the protocol they already speak, and relays agent devices on closed networks with mutual TLS end to end.
- SVH Fleet Server One per site: on premises, your cloud or hosted by SVH
- Enrollment and certificates, device sync, updates, configuration, device data and integrations, with consoles in your brand.
- SVH Partner Portal At SVH
- Your back office: license codes, device birth certificates, signing-key custody and signed bundles. It has no live link to any site.
Agent or bridge: what each can do
The agent is the recommended path, and the more secure one: each device holds its own identity and is encrypted end to end. Use the bridge for devices that can't run new software, such as an installed base or third-party equipment. A site can use both, and one bridge serves many devices.
| Capability | SVH Device Agent | SVH Device Bridge |
|---|---|---|
| Where it runs | Inside your device (embedded Linux, ARM or x86) | On the site network beside the devices, as a container or appliance |
| Change to your device | Add the agent. Your device app stays as it is and connects to the agent through the Agent App API, a local API on the device | None: the device keeps its own protocol (ASTM, POCT1-A2, HL7® v2 over MLLP, MQTT; others as a custom adapter) |
| Device identity | The device's own key, in a TPM 2.0 when present, from a birth certificate installed in your factory, with attestation | Each device is enrolled on its own and admitted only if registered by model and serial; the cryptographic identity is the bridge's, not the device's |
| Link security | Mutual TLS from the device to the Fleet Server | Mutual TLS from the bridge to the Fleet Server; between device and bridge, the device's own protocol, protected by network isolation unless it supports TLS (MLLP or MQTT over TLS) |
| Data when offline | Stored on the device, delivered in order when the network returns | Stored at the bridge per device, delivered in order; the device is acknowledged only once its message is stored |
| Software updates | Signed updates in waves with rollback, including offline USB | The bridge updates itself; device firmware only where the device's protocol can carry it, checked against its signature at the bridge |
| Remote configuration | Layered settings synced to the device | Only where the device's protocol can carry settings; otherwise the device keeps its own |
| Remote commands | Signed commands to the device | Only what the device's protocol supports, such as operator lockout and firmware |
| Your software on the device | Your device app runs as it does today, outside any sandbox; it only declares which events it sends and which server calls it makes. Add-on agent modules, yours or third-party, run sandboxed (native or WebAssembly) with signed permissions | Not available |
| Device health | Memory, storage, battery, network and module health | Status and faults, where the device's protocol reports them |
| Operator logins | Operator list and lockout managed centrally; the device checks logins, even offline | The same, for devices whose protocol carries an operator list (such as POCT1-A2) |
Agent devices on closed networks. The bridge also relays agent devices that can't reach the Fleet Server, such as devices on a lab or plant-floor network. It passes their encrypted traffic through untouched, so it can't read or impersonate them, and they keep every agent capability above.
Everything a connected fleet needs
Six capabilities, the same in every industry.
Device Management
Every device gets a cryptographic identity at enrollment and reports its operating status and faults for the rest of its life. Inventory, health, certificate status and lifecycle state, from enrollment to retirement, live in one console.
Data Management
Device data is delivered at least once and in order, acknowledged end to end and durable through network outages. Devices buffer what they cannot send and deliver it when the network returns.
Analytics & Insights
Dashboards over device and fleet data: utilization, reliability and status across sites. For medical devices, analytics run only on de-identified data.
Remote Upgrade
Signed updates rolled out in waves, paused automatically on failure, with rollback and version floors. Devices that live offline update from signed USB media using the same trust chain.
Device Configuration
Settings layered by product line, model, site and device, declared centrally and delivered by device sync: each device pulls only what changed since it last checked, so one that was offline catches up when it reconnects. Every change is authorized and recorded in a tamper-evident audit trail.
Interoperability
Signed webhooks and documented REST APIs for any business system. IVD devices add FHIR® R4, HL7® v2, ASTM and POCT1-A2 to the LIS and EHR, with delivery tracked per result.
What your customers get
Features of your product from the first installation, without your team building them.
- Device identity and security
- Per-device certificates, mutual TLS, secure enrollment, encrypted payloads
- Fleet management
- Device inventory, naming, grouping by site and area, live status
- Remote configuration
- Layered settings by product line, model, site and device, delivered by device sync: each device pulls only what changed, and catches up after time offline
- Software updates
- Signed update bundles, staged rollouts, update status per device
- Data and events
- Reliable device-to-server delivery, with offline buffering
- Integrations
- Webhooks and standard connectors to customers' business systems
- User and operator access
- Single sign-on (LDAP or OIDC), roles and permissions; operator PINs, roles and lockout managed centrally and pushed to every device, whether it runs our agent or connects through our bridge; devices check logins themselves, even offline
- Admin console
- Web console for fleet, users, configuration, updates and dashboards, in your branding
- Open APIs
- Documented REST APIs (OpenAPI) for your own apps and customer integrations
- Multi-language
- Translatable screens and messages, with language packs loaded at runtime
- Licensing
- One signed license code per installation, carrying its device band, platform features and your device features
- Device feature licensing
- Turn on paid features of your devices (a test menu, an advanced module) for every applicable device at a site; devices check the license themselves, even offline
- Compliance support
- Software bill of materials (SBOM) and security documentation for each release
Three ways to run it
The same Fleet Server runs in all three, and an installation can move between them.
Your field team installs; your customer's IT hosts it. For strict data-location rules or no reliable internet.
You operate it for your customers, alongside your own services.
We operate it for you. No infrastructure of your own.
Each installation runs as a single appliance or as independently scaled services, from the same signed images.
Can SVH connect your device?
Answer six short questions. Within two business days we reply with the path for your device. Then we book a demo with your engineers.