EdgeVISS Cloud Manager
Fleet Management
Every customer, every site, one screen — enrollment, health, remote commands, releases, and licensing for every EdgeVISS Local install you run.
EdgeVISS Cloud ManagerSite 1
EdgeVISS Local
Site 2
EdgeVISS Local
Site 3
EdgeVISS Local
Everything, per gateway or per fleet
Device enrollment
One-time activation token per EdgeVISS Local install. Health and container status roll in automatically from heartbeats — no manual check-ins.
Remote commands
Deploy, start, stop, restart, or update any device from one screen, across every site.
Application releases
Version and release single- or multi-component applications, pulled from your own private registries, rolled out to one device or a whole fleet.
Two-layer licensing
Fleet licenses cap how many devices a customer may enroll. Node-locked, fully-offline gateway licenses unlock feature tiers per device — independent, both auditable.
On-device
Point Diagnostics
Before you trust a reading, verify it end to end — one screen per device on EdgeVISS Local, not a support ticket.
Southbound
Write Gateway
The one supported path for an IT system to write a value back to OT: publish to a configured MQTT topic or call a REST endpoint, both authenticated and audit-logged, and EdgeVISS Local resolves the target device and executes the write.
IT system
MQTT publish or REST call, with token/session auth
EdgeVISS Local
Resolves the device, executes the write, logs it
OT device
Receives the write, result reported back