Internal reference — super-admin and partner functions. Not for end customers.
The platform's end-to-end data flow runs through six layers, from physical sensors to physical device triggers.
Layer 1 · Physical sensors — devices from many vendors (Xovis, Brickstream, Axis, Hikvision, Hanwha, Eurecam, Elsys, ImBuildings and others).
Layer 2 · Data transport — on-premises servers + cloud servers, LoRaWAN gateways, and the reverse-proxy bridge for remote sensor access. Live data has roughly a 2-second delay.
Layer 3 · Vemcount platform — Dashboards (all widget types), Reports (custom + snap + prediction), Maps 2.0 (7 view modes), Tenant (all sections), IoT widgets (Presence + Realtime), and admin settings. The white-label layer sits here with per-brand feature toggles and OAuth/Azure SSO.
Layer 4 · Alert engine — company-level Health Checks (13 rule types) plus per-widget alerts (min/max value, reset threshold, schedule).
Layer 5 · Output channels — Visual (in-browser sound), Email, SMS, WhatsApp, Webhook (GET/POST to any URL), and MQTT (topic-based publish).
Layer 6 · Physical device triggers — a Raspberry Pi / ESP32 / Home Assistant subscribes to MQTT or receives webhook calls to drive sirens, sliding doors, entry bells, fire-door SMS, digital signage and BMS systems.
In short: sensors feed transport, transport feeds the platform, the platform's alert engine evaluates thresholds, and the output channels can close the loop back to physical devices — making Vemcount both an analytics platform and an automation hub.