The Zero Trust Device Operations Platform
Give every device you make a verified identity, safe updates and data that always arrives. You ship it under your own brand.
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 · sandboxmutual 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 twins · 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.
Why device makers partner with SVH
Four things change the quarter you sign.
Launch a connected product in months, not the years it takes to build and staff a platform team.
Device certificates, signed updates and an SBOM come with every release, ready for customer security reviews.
Sell connectivity, fleet management and integrations to your customers as a subscription, under your brand.
We maintain, secure and extend the platform; your engineers stay on your core product.
Ship a connected product without building the platform.
Device makers spend years on plumbing that never differentiates the product. SVH is that plumbing, already built, secured and maintained.
Build it yourself
- A certificate authority and enrollment system
- An update system you trust in the field
- A queue that survives every network outage
- An integrations team on permanent staff
- Security evidence for every customer review
Ship it with SVH
- Device identity from the factory, per device
- Signed updates with staged rollout and rollback
- Data delivery that buffers offline and arrives in order
- Integrations through standard connectors and webhooks
- An SBOM and security documentation with every release
Four products. Each one has a place.
Where it runs and who runs it, at a glance.
SVH Device Agent
- Runs in
- Your device, embedded Linux
- Talks to
- SVH Fleet Server
- You need it if
- You can change the device software
Identity, offline data delivery, safe updates and a sandbox for your app.
SVH Device Bridge
- Runs on
- The site network
- Talks to
- Existing devices, Fleet Server
- You need it if
- Devices are fixed or on closed networks
Brings devices that can't take an agent into the same fleet.
SVH Fleet Server
- Runs
- On premises, your cloud or hosted by SVH
- Talks to
- Devices, customer systems, people
- Operated by
- You or your customer's IT
Fleet, updates, configuration, data and integrations for one site, in your brand.
SVH Partner Portal
- Runs at
- SVH
- Used by
- You, the device maker
- Reaches sites by
- Signed bundles, no live link
Licenses, device birth certificates and update signing for your product line.
One platform. Built for your industry.
The core is the same everywhere. Each industry adds the workflows and standards it needs.
Medical devices
- IVD analyzers
- Patient monitors
- Infusion and therapy
- Point of care
Sealed patient data, signed updates and the SBOM and audit evidence a regulated product needs. For IVD, results to the LIS and EHR over FHIR, HL7 v2, ASTM and POCT1-A2.
Industrial and connected devices
- Machines and controllers
- Scanners and handhelds
- Chargers and meters
- Building systems
Fleet, updates, configuration and device data for any device, with signed webhooks to your customer's business systems.
Something else? Other connected devices
How partnering works
You own the brand, the customer and the price. We build, secure and maintain the platform, and our fees grow only as your fleet grows.
- Discovery callYour devices, customers and integrations.
- Proof of conceptOne of your devices on a branded demo.
- Paid pilotOne customer site, success criteria agreed up front.
- Partner agreementBased on the pilot results.
- Launch and growYou roll out; we build from your roadmap.
For sites with strict data-location rules or no reliable internet.
You operate it for your customers.
No infrastructure of your own. Move between options at any time.
Questions we hear first
Who buys SVH?
Device makers. You license the platform from SVH Software Inc. and sell connectivity, fleet management and integrations to your customers as part of your product.
Will my customers see the SVH name?
No. Consoles and documents carry your brand, and SVH supports your team behind the scenes.
Does it need the cloud or a live internet connection?
No. An on-premises installation runs fully offline. There is no live link from the SVH Partner Portal to your sites; licenses and trust updates arrive as signed bundles.
Can you connect devices that are already in the field?
Yes, through the SVH Device Bridge. It speaks the protocol the device already uses, with no firmware change.
What hardware and operating system does the agent need?
Embedded Linux on ARM or x86. A TPM 2.0 is used when present; a software key covers hardware without one.
Does SVH give us regulatory approval?
SVH is designed to support your security and compliance programs, with an SBOM, signed updates and audit trails built in. It does not by itself constitute certification or regulatory clearance.
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.