An employee changes locations
An administrator finds their record and updates the permitted zones. Current permissions remain available for review.
Cameras and access control from different vendorsin one console
We connect the cameras, recorders and access controllers already installed on your sites, without replacing equipment or tying you to one vendor.
- Different manufacturersCameras over ONVIF or a video service, controllers over their own protocol.
- Open systems and APIsA standard protocol or an API connects through an adapter.
- Your equipment staysWe replace only what fails the compatibility check.
What you can do in the console
Choose a task to explore
Open a camera at the site you need
Select a location and camera for live viewing. When investigating an incident, check the recording for the relevant period.
Archive availability and playback options depend on the connected source.
- Choose a site and camera
- View an available video stream
- Open recordings by time
Define who can enter each area
Maintain employee and card records in a shared list. Assign access zones, update permissions when a person changes roles, and block cards when they leave.
Access zones and card status are synchronised with supported controllers. Changes take effect according to connectivity and device mode.
- Employees and assigned cards
- Permitted access zones
- Card blocking and revocation
Find out what happened on site
Filter the event log by site and period. Inspect an access event and its associated camera when that link has been configured.
Available events depend on the equipment. Notifications require recipient and delivery-channel configuration.
- A filterable event log
- Date, device and event type
- Linked video when a recording exists
Bring attendance records together
Select employees and a date range. Reports consolidate recorded entries and presence. Assigned working days and daily hours provide a baseline for report comparisons.
Results depend on reader configuration and complete card records. A responsible person must review working hours and disputed entries.
- Attendance over a selected period
- Comparison with daily hours
- Export for further review
As your sites grow
Each location brings its own cameras, employee lists and access rules. A shared console helps your team administer them centrally.
An event needs investigating
Security staff select the device and time in the log, then review available video from the associated camera.
You support customer sites
Work with devices and users in the relevant organisation’s console. Each organisation’s data is separated.
How we connect the system
We first check your cameras, controllers and requirements, then name the scope, timeline and cost.
On site
Cameras and access controllers
Platform
Devices, employees, permissions, event log and reports
In the browser
Administrator and security workspaces
Will our existing equipment work?
Compatibility depends on the exact model, firmware and available protocol. A network connection or ONVIF support alone does not confirm every feature will work.
Before implementation, we agree on a device list and test the required actions: viewing, receiving events, applying permissions and accessing recordings. Another manufacturer may require a separate adapter.
Where are video and recordings stored?
This depends on the source: a camera, recorder or connected video service. The platform provides access to supported streams and recordings.
Retention, network capacity and archive availability are agreed for the site. A clip cannot be opened if the underlying recording is missing.
How is data access separated?
Users work within their organisation’s context. Organisation data is separated in the database; assigned permissions govern actions in the console.
During integration, we define who administers the system, who reviews events and who can view video. Source credentials and personal-data handling require a separate review.
How do notifications work?
Telegram notifications for warnings and alarms are available to users who have linked their chat and enabled the relevant preferences. Examples include denied access, controller alarms and lost equipment connectivity. Available events depend on the integration.
We test delivery and latency against an agreed scenario. Site connectivity, processing and the messaging service all affect delivery. Camera motion notifications are excluded from this event selection.
Separate integration
When you need video analytics
Computer vision can be considered for a specific task, such as detecting a person in a defined zone.
The scenario, equipment and detection quality are evaluated separately using video from the site. This is an additional project, not a requirement for access management or camera viewing.
Before launch, we agree on recording conditions, acceptable missed detections and false alarms. Results from another site do not replace this evaluation.
See a working scenario
Leave a contact. We will discuss your requirements and arrange a demonstration of the system.
- Choose a scenario: cameras, access, events or a report.
- Review the equipment and site constraints.
- Agree on scope, cost and implementation steps.
The demonstration does not change access permissions at your site. Connecting your equipment requires a separate agreement.