Flagship platform

ArchGuard

A modular platform for security operations and response coordination.

ArchGuard is under active development. Capability availability depends on implementation progress and customer requirements.

The problem

Detection without coordination.

Security infrastructure is often fragmented. Cameras, guards, alarms, dispatch and reporting live in separate systems. When detection and response are disconnected, information arrives late, incidents are mishandled, and operational learning is lost.

The proposed solution

One operational chain.

ArchGuard is being developed as a modular platform that connects the full operational chain — from first signal to final resolution — through a common workflow that authorised organisations can configure for their operations.

Capabilities

Modular by design.

ArchGuard is built as a set of modules that can be configured for different organisations and service models. Each capability carries an honest status.

Incident Management

Available in MVP

Structured intake, classification, lifecycle tracking and closure for security and emergency incidents.

  • Incident intake from multiple sources
  • Classification and priority assignment
  • Explicit lifecycle states (reported → closed)
  • Audit record of every state change

Dispatch & Coordination

Available in MVP

Assignment of authorised responders with full status visibility from acknowledgement to resolution.

  • Responder availability and assignment
  • Status updates through response lifecycle
  • Escalation procedures
  • Operational reporting

Residential Identification

Available in MVP

Structured property, unit and occupant records that support accurate incident location.

  • Property and unit registration
  • Owner, landlord and occupant records
  • Residential identification numbers
  • Location retrieval during incidents

Command & Oversight

Available in MVP

Consolidated views for authorised command personnel across active incidents and available resources.

  • Active incident monitoring
  • Responder availability views
  • Operational performance reporting
  • Appropriate permission boundaries

Multi-Tenant Operations

In development

Support for multiple independent organisations on a shared platform, with enforced data isolation.

  • Organisation and tenant model
  • Resource-level access enforcement
  • Cross-tenant security testing
  • Configurable role structure

Equipment Integration

In development

Approved cameras, alarms and sensor events feeding into the incident workflow as structured signals.

  • Device event ingestion layer
  • Event-to-incident rules engine
  • Signal vs. verified incident distinction
  • Integration audit trail

AI-Assisted Classification

Planned

Assistance for operators in classifying incoming events, with human review retained for consequential decisions.

  • Event classification assistance
  • Confidence and risk assessment
  • Human-in-the-loop workflow
  • Measured false-positive rates

Emergency Partnerships

Planned

Coordination with authorised medical, ambulance and fire-service providers under service agreements.

  • Provider availability integration
  • Authorised emergency workflows
  • Status and handover records
  • Service-level agreements

Status labels describe the current state of each capability. Only capabilities marked Available in MVP are operational today. Planned and exploratory capabilities are not available for deployment.

How it works

From first signal to resolution.

Every incident passes through an explicit lifecycle. The platform records who did what, when, and why — so the operational record is trustworthy.

This is an illustrative workflow. Actual implementations are configured per customer and per deployment.

  1. Reported

    An incident enters the platform from an authorised source — a person, an alarm, or an integrated device.

  2. Recorded

    The platform captures structured incident data, location information and supporting context.

  3. Verified

    An authorised operator assesses the report and classifies its nature, priority and appropriate response.

  4. Assigned

    The responsible organisation assigns a qualified responder or team, with full status tracking.

  5. Coordinated

    Response progress is tracked from acknowledgement through arrival and resolution.

  6. Resolved

    The incident outcome is recorded, and the audit trail preserves what occurred.

  7. Reviewed

    Authorised users generate reports and learn from the operational record.

Architecture

A separated frontend and backend.

ArchGuard runs as a web application backed by a REST API and a relational database. Each layer has a clear responsibility.

Detailed infrastructure, network topology and integration specifications are shared with prospective customers and partners under appropriate agreements.

Web application
Next.js + TypeScript

Server-rendered interfaces and dashboards for operators, responders and administrators.

Backend API
Yii2 REST

Business logic, authentication, authorisation and permission enforcement.

Database
PostgreSQL

Persistent storage for organisational records, incidents, users and audit logs.

Integrations
Controlled connections

Authenticated communication with approved external systems and device integrations.

Security approach

  • Token-based authentication with short-lived access tokens
  • Role-based access control enforced at the API layer
  • Tenant isolation enforced in the backend, not only in the interface
  • Audit logging for security-relevant actions
  • HTTPS in transit, protected storage at rest
  • Designed in alignment with Uganda’s Data Protection and Privacy Act, 2019 framework

See whether ArchGuard fits your operations.

If you would like a walkthrough of what ArchGuard does today — or to discuss a possible pilot — get in touch. We will tell you honestly whether the platform is a fit.