Skip to content
SVHSoftware

Industries / Connected devices

Run every device you ship as one fleet

For makers of scanners, pumps, industrial equipment and field units. Each device gets a verified identity, signed updates and settings you control centrally. Your customers get a console in your brand.

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

Devices run the agent, or connect through the bridge if they can't. One Fleet Server per customer site runs the fleet and feeds your customer's systems.

  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 customer's devices

    Your devicesscanners, pumps, field units
    SVH Device Agenthardware identity · offline queue · signed updates · sandbox

    mutual TLS to the Fleet Server

  3. On the site network

    Devices without the agentno firmware change · MQTT · custom adapters
    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, groups and live status · Updates in waves, with rollback · Layered settings, device data · consoles in your brand

  5. Your customer's systems

    ERP and business appssigned webhooks
    Your own appsopen REST APIs
    Admins and operatorssingle sign-on
In your customer's devices
The SVH Device Agent gives each device an identity, queues data offline and applies signed updates.
On the site network
The SVH Device Bridge connects devices without the agent over MQTT or a custom adapter.
SVH Fleet Server
Groups, live status, updates in waves with rollback, layered settings and device data.
Partner back office
The SVH Partner Portal issues licenses and certificates. It reaches sites only through signed bundles applied offline.

Ship an update to the whole fleet without holding your breath

You sign the update. The Fleet Server rolls it out in waves and stops on its own the moment devices start failing.

  1. Sign the release Devices install only software signed with your key.
  2. Pick who gets it By group, site or model. Start immediately or schedule.
  3. Roll out in waves A small first wave, then wider ones, with status per device.
  4. Stop automatically Too many failures pause the rollout. A failed device rolls back on its own.
  5. Never go backwards Version floors stop devices from being downgraded to a vulnerable release.

Settings in layers, not per device

Set a value once at the level it belongs to. Lower layers override higher ones, and every device ends up with the right values.

Product line
Defaults you ship with every device
Model
Values for one model and firmware version
Site
Your customer's choices for one location
Device
The one unit that needs to be different

Everything a fleet needs

From the first enrollment to your customer's business systems, in one console.

Fleet

  • Inventory and naming
  • Groups by site and area
  • Live presence and status
  • Faults and remote commands

Data

  • Device records delivered reliably
  • Buffered on the device when offline
  • Retention you set
  • Signed webhooks and REST APIs

People

  • LDAP or OIDC single sign-on
  • Roles and permissions
  • Operator sign-in on the device, offline
  • Screens in your customer's language

Business

  • Your brand on every screen
  • Signed license codes turn on features per site
  • Audit trail of every change
  • SBOM with every release

Is your device a fit?

Most embedded-Linux devices run the agent as they are. Everything else connects through the bridge.

Devices we're built for

  • Security and mail screening
  • Pumps and flow control
  • Industrial controllers
  • Kiosks and terminals
  • Field and remote units
  • Lab and test equipment

What your device needs

Operating system
Embedded Linux, ARM or x86
Identity
TPM 2.0 if present; software key otherwise
Network
Outbound only, to the Fleet Server
Your app
Talks to the agent locally, never the internet
No Linux?
Connect through the SVH Device Bridge

Industry pages

The same platform, seen through the devices and systems of four industries. Everything else is covered here.

Industrial devices

CNC and machine tools, Packaging and filling lines, Test and inspection stands

Logistics devices

Barcode and RFID scanners, Rugged handhelds and tablets, Vehicle and trailer units

Energy devices

EV chargers, Inverters and battery systems, Smart meters and gateways

Building devices

HVAC and air quality controllers, Access control and intercoms, Fire and safety devices

Questions device makers ask

How is this different from a cloud IoT service?

SVH runs where your customer needs it, including fully on premises and offline. It ships in your brand, and device identity, signed updates and licensing come built in instead of being assembled from parts.

Our device doesn't run Linux. Can it still connect?

Yes. The SVH Device Bridge connects devices that can't run the agent, in the protocol they already speak, such as MQTT or a custom protocol through an adapter. No firmware change.

Does it need a live internet connection?

No. Devices buffer data while offline, and an on-premises installation runs without internet. Licenses and updates reach the site as signed bundles.

Can we get device data into our own systems?

Yes. Signed webhooks push device events to your systems, and documented REST APIs let your apps read and act on the fleet.

What do we pay for?

Pricing is set per partner, based on your devices and fleet size. We walk you through it on the first call.

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.

Tell us about your device.

Check my device

Prefer to talk first? Book a demo