Supracontrol Enterprise
Supracontrol Enterprise is the browser-based platform operators use to run a Supracontrol deployment. It brings environmental monitoring, access control, video surveillance, hardware management, and rule-based automation into one interface, so a single team can watch a site, understand what happened, and act on it without moving between separate systems.
A deployment can be one building or hundreds of sites belonging to several organisations. The same interface covers both.
[IMG — Supracontrol Enterprise main window showing the module tab bar and the Monitoring dashboard]Why one platform
Each of these functions is normally its own product, with its own login, its own event log, and its own export. Supracontrol Enterprise merges them. A temperature excursion, a door forced open, and a camera detecting motion all arrive in the same event log, are narrowed with the same filters, notify people through the same notification rules, and leave the system through the same reports and exports.
That has a practical consequence: an operator investigating an incident does not have to correlate three systems by timestamp. The access event, the sensor reading, and the recorded video clip are already linked to each other.
The modules
| Module | What you do there |
|---|---|
| Monitoring | Watch live sensor state as a card grid, on customisable dashboards, or on a geographic map of your locations |
| Video | View live camera streams, build named video walls, and search and replay recorded footage |
| Events | Review every alarm and event the system recorded, and trace every configuration change in the audit log |
| Access | Define who may enter which locations and when, manage cards and groups, and review attendance |
| Devices | Inventory and configure controllers, peripherals, and cameras, and drive outputs directly |
| Automation | Write rules that react to sensor values, alarms, and schedules - on a controller or across the whole system |
| Settings | Configure the location hierarchy, users and roles, business units, notification channels, licences, and scheduled reports |
What the platform gives you
Real-time state, three ways
Monitoring presents the same live data in the form that suits the moment: a uniform card grid for a fast status sweep, a dashboard canvas you compose yourself from freely placed cards including live video and event grids, and a map that shows which locations currently hold an alarm. An alarm-count badge in the toolbar filters any view down to what is actually wrong.
Video attached to the incident
Camera-sourced events in the event log open their recorded clip directly in Playback. Recordings are browsable by calendar date on a 24-hour timeline, filterable by camera, alarm type, and recording state, and downloadable as screenshots or as a ZIP of selected clips.
Alerts that reach people
Notification rules deliver alarms, system events, and audit events over email, SMS, and voice call. Delivery outcomes are recorded per event, so you can confirm whether a notification actually reached its recipient rather than assuming it did.
Automation that survives a network outage
Automation rules come in two forms. Local rules are pushed to the controller and execute on the device itself, so a relay keeps following its sensor even when the server is unreachable. Global rules run centrally and are the ones that can span multiple devices and locations and notify people.
Structure that matches your organisation
A location hierarchy organises every device, camera, and sensor, and Business Units group locations, users, and data into separate scopes. A BU Admin sees and manages only their own unit’s hardware and users, which makes it practical to run several sites, tenants, or customers from one deployment without them seeing each other’s data. Seven role levels, from Viewer up to Superadmin, decide what each person can open and change.
A record of what changed
Beyond the alarm log, the Audit Log records every create, update, and delete performed on users, licences, devices, cameras, and schedules, with a side-by-side previous → current diff of each changed field. Operators can also flag events and attach free-text notes for follow-up.
Data that leaves the system cleanly
Practically every list view exports to Excel or PDF. Scheduled Reports generate and deliver reports to recipients on a recurring schedule, and API keys open the same data to your own integrations.
How the pieces fit together
| Layer | What it is |
|---|---|
| Field hardware | Controllers running the on-site logic, and the peripherals wired to them - temperature, humidity, flood, smoke, power, air quality, locks, readers, and relays - plus IP cameras |
| Server | Collects device data, evaluates global rules, stores events and recordings, and sends notifications |
| Clients | This web platform for operators and administrators, the mobile app for the field, and the controller’s own web interface for commissioning |
See the Devices section for the hardware specifications and the Controller Web Interface, and the Mobile Application section for the companion app.
Where to start
- New to the platform - open Monitoring to see how live state is presented.
- Setting up a deployment - start with the Location Manager, then Business Units and Users and Roles.
- Adding hardware - follow Adding a Controller and Adding a Camera.
- Getting alerts out - configure SMTP, SMS, or Voice, then create a notification.
Use the sidebar to jump into any module, device type, or configuration area.