Platform / SVH Fleet Server
Run the fleet, in your brand.
The SVH Fleet Server is where a site's devices become one operable fleet: every device enrolled and attested, every update rolled out safely, every record delivered, and every customer system spoken to in its own language.
SVH Fleet Server
- Runs
- On premises, your cloud or hosted by SVH
- One per
- Customer site
- Talks to
- Agents and bridges, customer systems, people
- Open ports
- Two: one for devices, one for people and apps
- In the device
- Site network
- Fleet Server
- Partner Portal
Fleet operations
- Enrollment: factory birth certificate to operational certificate, approved by hand or automatically
- A certificate authority per site, with automatic certificate renewal
- Digital device twin: declare desired state, watch it reconcile
- Inventory, naming, groups by site and area, live presence and status
- Remote commands, faults and operating status
Updates and configuration
- Signed update bundles rolled out in waves, with automatic pause on failure
- Rollback, and version floors that block downgrades
- Settings layered by product line, model, site and device, synced as deltas
- Updates for the bridge itself and for devices behind it
Data and integrations
- Device data delivered at least once and in order, acknowledged end to end
- Append-only, exportable audit trail of every change
- Signed webhooks and documented REST APIs (OpenAPI)
- Industry layers add their own pipeline, such as LIS and EHR delivery for IVD devices
People and licensing
- Database, LDAP or OIDC sign-in; roles and permissions editable at runtime
- Operator sign-in at the device that keeps working offline
- Signed license codes turn features on per site, with no reinstall
- Screens and messages translated by language packs loaded at runtime
Consoles in your brand
An admin console for fleet status, enrollment queues, certificates, users, roles and audit. Approvals that matter, like admitting a device, are signed actions with re-authentication and a reason. Industry layers add their own console, such as the clinical console for medical devices.
Appliance to cloud, same code
Run everything as one process on a single host, or as independently scaled services. Rootless containers under systemd, and the same signed images everywhere.
Built like infrastructure
A modular core with enforced boundaries and a durable outbox. Every image ships with a CycloneDX SBOM, signed and digest-pinned.
Industry layers
Each installation runs one industry layer on the same core. Medical devices adds results delivery to the LIS and EHR, QC and consumables. Connected devices keeps the core lean for any kind of device.
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.