Serach Icon

    Platform scale & architecture

    This article documents Vemcount's production scale and end-to-end technical architecture as observed from the live super-admin account. It is intended for technical admins, partners, and integration teams.

    Platform scale (live metrics)

    Total users

    17,870

    Shop locations

    15,914

    Total sensors

    24,753 (22,823 active)

    Sensor vendors

    63 — Xovis, Brickstream, Axis, Hikvision, Hanwha, Eurecam, Elsys, IMBuildings, and more

    Active subscriptions

    2,497

    Licenses

    23,070 (638 missing)

    White-label brands

    119

    Currencies

    157 (live EUR rates, auto-updated daily)

    On-premises servers

    132 total / 23 active

    Gateways / Screens

    33 / 45

    Emails sent (MTD)

    62,806

    SMS / WhatsApp (MTD)

    1,650

    Active health issues

    7,403

    6-layer architecture

    Layer 1 — Physical sensors

    24,753 devices across 63 sensor vendors: Xovis, Brickstream, Axis, Hikvision, Hanwha, Eurecam, Elsys, IMBuildings, and more. Sensors are installed overhead at entrances, zones, queues, and parking areas. Each sends count data (entries, exits, occupancy, demographics, IoT metrics) to the platform.

    Layer 2 — Data transport

    Data travels from sensors to the platform via two paths:

    • Cloud servers — direct outbound push from sensors over TCP 80/443

    • On-premises servers — 132 installed in customer environments (23 active), bridging sensors on isolated networks to the cloud platform

    • 33 Gateways — protocol translation devices for LoRaWAN and other non-IP sensor types

    • Reverse-proxy bridge — allows remote access to physical sensors for configuration and diagnostics (see Device Manager article)

    • ~2 second delay — typical latency from sensor event to live dashboard update

    Layer 3 — Vemcount platform

    • Dashboards — 13 widget types, real-time and historical

    • Reports — custom, snap, scheduled, with prediction/forecast

    • Maps 2.0 — 7 view modes including live heatmap and visitor tracking

    • Tenant module — 7 sections for mall/property analytics

    • IoT widgets — Presence Overview (desk/seat grid) and Realtime (any sensor metric)

    • Admin settings — full company, device, user, and data management

    • White-label layer — 119 brands with custom domains, logos, CSS, and feature toggles

    • OAuth / Azure SSO — per-brand Microsoft Entra ID integration

    Layer 4 — Alert engine

    • Health Checks — 13 rule types, configured per company, run on schedule

    • Per-widget alerts — Min/Max value thresholds with reset hysteresis, optional schedule

    Layer 5 — Output channels

    Visual

    In-browser notification with optional sound chime

    Email

    62,806 sent per month

    SMS

    Instant text to any phone number

    WhatsApp

    1,650 SMS/WhatsApp combined per month

    Webhook

    HTTP GET or POST to any URL — Slack, Teams, PagerDuty, custom APIs

    MQTT

    Topic-based publish to any MQTT broker

    Layer 6 — Physical IoT device triggers

    Webhook and MQTT outputs can trigger real physical devices via Raspberry Pi, ESP32, Home Assistant, or any MQTT/HTTP-capable controller:

    • Occupancy limit → siren relay activation

    • Entry detected → door bell or welcome chime

    • Fire door opened → instant SMS to security team

    • Queue threshold → sliding door open/close command

    • Wait time exceeded → WhatsApp alert to floor manager

    • Occupancy data → digital signage real-time display update

    Related articles: Device Manager deep-dive · Health Checks — all 13 rule types · Widget alerts & IoT automation (MQTT)

    clock

    7PM

    GMT+2

    clock

    7PM

    GMT+2

    clock

    7PM

    GMT+2

    Become Our Supplier Or Partner