Skip to content
SVHSoftware

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.

Check my device Book a demo

A fleet console in the device maker's brand: devices online, an update rolling out in waves and a live heartbeat.

Where it runs

Four products, each with one place to run. Your customers see your brand on every screen; SVH stays behind it.

  1. Partner back office, run by SVH

    SVH Partner Portallicenses, birth certificates, signing
    You, the device makerrequest licenses, release updates

    signed bundle, applied offline · no live link from the portal

  2. In your device

    Your device appnever touches the network
    SVH Device Agenthardware identity · offline queue · signed updates · sandbox

    mutual TLS to the Fleet Server

  3. On the site network

    Devices already in the fieldno agent, no firmware change · ASTM · HL7 · POCT1 · MQTT
    SVH Device Bridgetranslates their protocol · relays closed networks

    mutual TLS to the Fleet Server

  4. SVH Fleet Server · on premises, your cloud or hosted by SVH

    SVH Fleet ServerFleet, certificates, device twins · Updates, configuration, licensing · Data pipeline and audit · consoles in your brand

  5. Your customer's systems

    Business and clinical systemswebhooks · FHIR · HL7
    Your own appsopen REST APIs
    Admins 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 sandbox for your software.
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 twins, 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.

Everything a connected fleet needs

Six capabilities, the same in every industry.

Device Management

Every device gets a cryptographic identity at enrollment and a digital twin 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 reconciled through the device twin. 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, synced to devices
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, offline operator login on devices
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
Signed license codes that turn features on for each installation
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.

Customer premises

Your field team installs; your customer's IT hosts it. For strict data-location rules or no reliable internet.

Your cloud

You operate it for your customers, alongside your own services.

Hosted by SVH

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.

What kind of device?

Medical devices Other connected devices

Prefer to talk first? Book a demo