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.
How the platform fits together
One record, written where the work happens, read by everyone entitled to see it. This is the shape of the platform — what is running today, and what is not, is stated capability by capability below.
Field
A guard checks in against a published shift, runs a patrol and reports an incident from a phone on the post.
Record
Each action is written once — timestamped, attributed, and kept. Exceptions are recorded as exceptions, not discarded.
Platform
One record store behind every screen. No screen keeps its own copy of what happened.
Supervision & control room
Supervisors see their own personnel, attendance and patrols. The control room takes incidents, escalates and tracks response.
Client visibility
Client accounts see their own sites and incidents, export them, and raise requests — and nothing belonging to anyone else.
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 Presence Verification
Device location is captured at check-in and check-out and the distance to the site's configured boundary is computed on the server, never on the device. It runs in record-only mode: the result is recorded and attendance is never refused on it. No site boundary has been surveyed and signed off yet, and no verification record exists in production. Continuous location tracking is deliberately not implemented.
Emergency / Assistance Alerts
Guards can send an in-app assistance alert to L'Anubis control-room staff and, where assigned, their supervisor. Alerts are recorded as Critical incidents, remain visible until handled, support acknowledgement, dispatch, escalation and audit tracking, and persist across page refreshes. This feature does not automatically contact police, ambulance or fire services. SMS and email emergency delivery are not currently connected, and push delivery is not considered operational until real subscribed devices are verified.
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 built end to end, but no device is subscribed in production — so no push has ever had a recipient, none has ever been attempted, and delivery to a real handset has never been observed. Nothing here should be relied on to reach a person.
Email & SMS Notification
Automated message delivery from the platform to employees, applicants and clients. One transactional email is live: a security notice sent to an account holder when their own password, second factor or role is changed. No operational workflow sends email yet — not shifts, incidents, applicants or client requests — no SMS provider is connected, and nothing in the product claims a message was opened or read. This stays partial until those operational workflows actually send. Company email at lanubis.com is an ordinary mailbox, separate from this platform.
CCTV / Video Security Platform
Camera inventory, site location hierarchy, camera health monitoring and normalized video events, running against a simulator. No camera, recorder or video stream is connected to L'Anubis: there is no live view, no recorded playback, no snapshot, no export and no PTZ control. Simulated cameras, health records and events are stored and displayed as simulated. Video events are machine observations and none becomes an incident without a person.
How we label status
Every capability on this platform carries one of these 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.
Live (in-app)
Running in production and verified there, but only inside the platform — no external channel or third-party service is involved, and the card says so.
Live (account security only)
Running in production and verified there, but deliberately limited to one kind of message — a security notice to an account holder about their own account. No operational workflow uses it.
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.
And how we draw it
Each card above carries a rule down its left edge. The rule only ever gets less solid as a capability gets less proven — it can never make something look more settled than its label says. The label is always the authority; the rule is a second way of reading it at a glance.
- verifiedA solid rule. Running in production and verified there — at whatever scope the status word states.
- unverifiedA dotted rule. Built and connected, but not proven end to end, so it is not called live.
- simulatedA dashed rule. The workflow runs, but on simulator data rather than field hardware.
- plannedA dashed, recessed rule. Not built. Nothing on this page currently carries it.