Deployment & security

Run it our way or yours.

Some agencies want the servers gone. Some cannot put dispatch anywhere but their own network, and are right not to. P1 is the same product either way — the same console, the same mobile, the same data model, the same upgrades.

Two ways to run it

The product does not change. The plumbing does.

Cloud We host it, patch it and back it up. No server room, no SQL administrator, and no hardware refresh sitting on your capital plan.
On-premises Everything on your own network, under your own retention policy. Core dispatch needs only the CAD and your database.
Either way Per-user accounts, enforced password policy, and an audit trail that names a person rather than a workstation.
Option A

Cloud

For agencies who would rather not run a server room. We handle the infrastructure, the patching and the backups; you handle dispatching.

  • No hardware to buy or refresh, and no SQL Server licence on your books.
  • Managed backups and failover, tested by us rather than by you at the worst moment.
  • Updates applied for you, on a schedule you agree to rather than one you are surprised by.
  • Still your data. Export is a feature, not a professional services engagement.
Option B

On-premises

For agencies whose policy, or whose network, says dispatch stays inside the building.

  • Core dispatch depends on two things — the CAD and your database, both on your network.
  • Every integration is an add-on. If a partner service is down, or an add-on was never licensed, dispatchers keep dispatching.
  • If the internet drops, the room keeps working. That is a property of the architecture, not a mode you switch into.
  • Remote and continuity positions join over your own VPN, governed by the policy your IT team already runs.

Worth testing, not assuming. A continuity position that has never been used is a plan, not a capability. We will help you exercise it.

Compliance

Built for CJIS

The controls an audit asks about are in the product rather than bolted to the side of it.

  • Per-user accounts. Shared logins destroy the audit trail — the record of who dispatched, who changed a status, who wrote a note is only worth having if it names a person.
  • Enforced password policy — complexity, expiry, lockout and reuse, set centrally and applied on every workstation.
  • Role-based permissions, granted through roles rather than one at a time, and every change logged.
  • An audit trail you can read, covering configuration as well as calls.

We will not tell you P1 makes you compliant. Compliance is a programme, not a product. What we can tell you is which controls the software enforces, and we will answer your security questionnaire in writing.

Your data

It stays yours

Whichever way you run it, the record belongs to the agency. Reporting exports are standard formats, the database schema is documented, and leaving is a supported operation rather than a negotiation.

Next step

Send us your security questionnaire.

We would rather answer it early than at the end of a procurement. Tell us which way you want to run it and we will scope it honestly.

Talk to us See the platform