Compare
OpsCentre vs the usual approaches.
Most communities run on spreadsheets, chat-bot stacks, form builders or a self-hosted script — and for some communities those are the right call. The comparison covers tool categories rather than named products, and where the usual stacks are ahead of OpsCentre today, the table says so.
| Dimension | Spreadsheets & shared forms | Chat-bot dispatch stacks | Generic form builders | Self-hosted terminal scripts | OpsCentre |
|---|---|---|---|---|---|
| UK & Irish jurisdiction fidelity | Whatever you type in — nothing is seeded, checked or kept current. | Presets tend to be US-styled; UK or Irish fidelity is manual rework. | None built in — every field, rank and reference is yours to invent. | Depends entirely on the script; UK/Irish variants are rare. | Four jurisdictions seeded end to end — ranks, legislation, courts and terminology for England & Wales, Scotland, Northern Ireland and the Republic of Ireland. Live today. |
| Records depth | Flat rows. Linking a person to a vehicle, a case and a custody record is manual cross-referencing. | Lookups return what a command was coded to return — records rarely connect to each other. | Each form is an island; responses land in separate result lists. | Usually person and vehicle lookups; deeper records depend on the script author. | Cross-linked records: case files, person/vehicle/property/firearms lookups, intelligence, custody, safeguarding and court applications reference each other. Live today. |
| Permissions granularity | Sheet-level sharing — anyone with the link can usually see (or break) everything. | Chat-role gates: whoever holds the role can run the command. | Per-form access at best; no concept of rank, unit or record type. | Whatever the script hard-codes; changing it means editing source. | 100+ per-action permission keys; grants scoped by action, record sub-type and org unit, with an approval queue for sensitive access. Live today. |
| Tenant isolation & UK GDPR posture | One shared document — deletion requests mean hunting through tabs and version history. | Data lives in a bot database you do not control, under terms you have not read. | Data sits in a general-purpose account; no roleplay-specific safeguards. | You are the data controller AND the hosting provider — the compliance burden is entirely yours. | Every record scoped to your community at application level, with database-level hardening in progress. DSAR workflow, breach and retention registers built in. Live today. |
| Hosting & maintenance | Free, but the structure decays as the sheet grows and owners move on. | Bot hosting, uptime and updates are someone else's hobby project. | Hosted for you, but built for surveys — not operational records. | Your server, your patches, your downtime, your backups. | Nothing to host. Subscription service; every update and every new module included. Live today. |
| Auditability | Version history shows cell edits — not who looked at what, or why. | Command logs if the bot keeps them; typically overwritable. | Response timestamps only. | Whatever logging the script author bothered with. | Dedicated audit trails for record access, searches and staff actions; selected evidentiary records carry database-level immutability controls. Live today. |
| CAD / MDT dispatch console | No. | Often the headline feature — live dispatch through chat commands works today. | No. | Yes — a live dispatch screen is exactly what these scripts are for. | Live today — a full control-room console and officer terminal, including pursuit and firearms command, reading from the same duty and records data as the rest of the platform. Point to Point and a live map are coming soon. |
Where each approach works well.
These tools are popular for good reasons. A fair comparison says what they do well — and where the strain shows as a community grows.
Spreadsheets & shared forms
Free, familiar, and a reasonable fit for a brand-new community tracking a dozen members. Nothing to learn, nothing to pay.
Strain appears with scale: no record linking, no per-record access control, and one mis-shared link exposes everything.
Chat-bot dispatch stacks
Live dispatch inside the chat platform your community already uses — convenient, and the dispatch experience works today.
Records tend to be shallow name-lookups, permissions are chat roles, and your data lives in someone else's database.
Generic form builders
Excellent at what they were built for — collecting structured submissions like applications and incident reports.
They were never meant to be a records system: no linking, no rank model, no jurisdiction awareness, results in flat lists.
Self-hosted terminal scripts
Deep in-game integration and full control — for a community with a capable, committed developer they can be a great fit.
You inherit hosting, patching, backups, security and the full data-protection burden — and the bus factor is usually one person.
How to read this comparison.
The comparison is between broad approaches; individual products within a category vary. It was last reviewed on 15 July 2026.
Each OpsCentre claim above maps to a module that is live today — you can check them against the modules page. Progress on planned items lives on the roadmap.
Where OpsCentre is behind
- Pre-launch: billing is closed, and the platform is in an evaluation phase ahead of its 2026 launch.
- Single operator: OpsCentre is built and run by one person, with no external SLA or support team.
- Newest modules settling in: the dispatch console, officer terminal and duties board are the most recently shipped and are still being tested against real control-room use.
See what the depth looks like.
Every module, every jurisdiction, one subscription — and a status label on everything.