A digital operations platform, built in the open.
We label every capability by its real status. Nothing here is claimed as live until it actually is.
Field operations
Tools for guards and supervisors on-site.
Digital Guard Reporting
Mobile check-in and check-out against a published shift, shift status, and incident reporting from the field.
NFC Checkpoint Verification
Patrol checkpoint scanning in sequence, with QR fallback. Scans are recorded through a simulator until reader hardware is commissioned, and simulated scans are stored and displayed as such.
GPS Patrol Monitoring
Location-aware patrol tracking, configurable per site, with clear limits on what GPS can and can't confirm. No location provider is connected yet.
Emergency / Assistance Alerts
In-app alerting to supervisors and control room staff. This does not claim automatic police, ambulance, or fire dispatch — no such integration exists.
Operations & oversight
Tools for supervisors, SOC operators, and administrators.
Scheduling & Attendance
Shift creation with conflict detection, publication, employee acknowledgement, leave and swap handling, and attendance derived from scheduled versus actual time.
Incident Management
Structured incident intake, severity classification, and an enforced lifecycle from report through acknowledgement and resolution to closure.
SOC & Dispatch
Centralised incident queue, dispatch coordination with enforced response stages, time-based escalation, and a full audit trail.
Client Portal & Incident Visibility
Client accounts see their own sites and incidents and can export them, and can raise requests. Reports are read in the portal — scheduled report delivery by email is not connected.
Push Notifications
Operational alerts to signed-in devices. The channel is configured and sends without error, but delivery to a real device has not yet been observed, so we do not call it live.
Email & SMS Notification
Message delivery to employees, applicants and clients. No sending domain or SMS provider is connected, and nothing in the platform claims a message was sent.
How we label status
Every capability on this platform carries one of four labels, and we won't call something "live" until it's actually running in production and has been verified there:
Live
Deployed to production and verified there.
Configured, unverified
Built and connected, but not yet proven end to end — so we don't call it live.
Simulated
The workflow runs, but on simulator data rather than field hardware. Simulated records are marked as such.
Planned
Scoped, not yet built. No provider connected.