Clear answers before you change how you operate.

PatrolCore is designed for guarding companies running static security, mobile patrol, keyholding and alarm response, events, control rooms, K9 deployments or a mix of those services.

Yes. PatrolCore Free is designed for up to five guards, with the same platform foundation so your data can remain in place as the company grows.

The aim is to connect rota, deployment, frontline reporting, incidents, patrols, credentials, clients, sites and live operations so teams do not maintain the same operational truth in several disconnected systems.

The guard experience is designed to use location in operational contexts such as duty, clock-in, live response and geofence workflows. Production mobile behaviour will be documented clearly before rollout.

The client portal is designed around scoped access to the client organisation and its sites, reports and relevant operational information rather than exposing the wider security-company estate.

Credential tracking, evidence, verification status, expiry awareness and deployment eligibility are core parts of the product direction. Unverified credentials should not silently grant deployment eligibility.

PatrolCore Response is being designed around the whole activation lifecycle: receive, assess, identify a suitable responder, dispatch, navigate, arrive, capture evidence, close out and report to the client.

In-car response is on the product roadmap. It should be implemented through the native templates and safety restrictions of each platform rather than simply mirroring a phone interface.

No. The product direction is human-reviewed AI assistance: help structure or summarise operational information, then let an authorised person review and approve the result.

Yes. The most useful demo is built around how your company runs today — control room, mobile response, events, compliance, clients or whatever causes the most friction.