Mobile app management · audit records · multi-site scope · private or local deployment route · model-specific connection review. Standard supply 200 units; OEM/private label 500; ODM 1,000.
Review multi-site scope, role permissions and status visibility against the selected account and controller configuration.
iOS and Android management app: add users, issue mobile keys, remote unlock, view live audit trail, receive instant alerts — from anywhere.
Documented external-interface and event scope can be reviewed for a named workflow, controller and target system. Confirm the test method, version and delivery responsibility before supply.
Every access event (granted, denied, forced entry, tamper) timestamped and stored. Exportable audit reports for compliance, insurance, and incident investigation.
A private or local deployment route can be reviewed for the customer's infrastructure. Confirm the deployment boundary, data location, privacy documents and operating responsibility in the written project scope.
Offline credentials, event buffering and reconnection behavior are confirmed against the selected controller and firmware.
| Doors per Unit | 1-door or 2-door controller configuration |
| Reader Interface | OSDP v2, Wiegand 26/34, RS-485 |
| Local Credentials | 100,000 |
| Local Event Log | 500,000 records |
| Network | 10/100M Ethernet (PoE optional) |
| Relay Output | 1 × Form C, 5A at 30V DC |
| Alarm Inputs | 4 supervised (REX, door contact, tamper, PIR) |
| Certifications | CE LVD, CE RED, RoHS 3, EN 50131-1 Grade 2 |
| Deployment | Hosted (EU DC), Private cloud, On-premise (Docker) |
| External interface | Named interface or event scope by model and deployment |
| Mobile App | iOS 14+ / Android 10+ (white-label available) |
| Users per Account | Confirmed by account and project scope |
| Sites per Account | Confirmed by account and project scope |
| Service terms | Confirmed in the written deployment scope |
| Security documents | Requested and reviewed for the selected deployment |
| Access roles | Role and authentication route confirmed by model and account |
White-label mobile app, branded management route and external connection scope are reviewed under the OEM/private-label programme. Private or local deployment is confirmed through the written project quotation.
Traditional access control stores credentials and audit logs on a local server, while a cloud route moves selected management functions to a hosted service. Confirm local-door behavior, offline fallback, data location, update responsibility and multi-site scope for the exact controller and deployment. If a named HR, property-management or building workflow must connect, review the documented interface and acceptance workflow rather than assuming a universal connection.
A hosted, private-cloud or on-premise route can be reviewed for the selected controller, account and destination. Confirm the storage region, data roles, offline behavior, deployment responsibility and security documents in the written project scope; do not assume one hosting route satisfies every GDPR or sector requirement.
External interface documentation, event scope and connection boundaries can be reviewed for the selected controller and deployment. Name the required user, credential, event or door action and the target HR, property-management, co-working or BMS workflow; confirm the test method, version and delivery responsibility before calling the connection ready.
Site, door and credential capacity depends on the selected controller, account configuration and deployment. Role-based permissions, multi-site visibility and any reseller or white-label boundary can be reviewed for the named project; confirm the required limits and data separation in the written scope.
Local-door behavior, cached credentials, event buffering and reconnection handling depend on the selected controller and firmware. Confirm which credentials and schedules remain available during an outage, how records are retained, and how changes are reconciled before deployment.
Branding, dashboard, mobile-app, account and deployment options can be reviewed for the selected OEM scope. Confirm the requested assets, account ownership, data separation, documentation, support responsibility and any platform terms in the written agreement; no universal white-label package is assumed.
Security controls and documents depend on the selected hosting route, controller and destination. Request the current encryption, access-control, logging, vulnerability-management and data-processing evidence for the exact deployment; certification or audit status must be confirmed in writing rather than inferred from a product label.