Public safety software

// The problem

A police service's members take notes in the car, return to the station to type reports, and re-enter call details the dispatch system already holds.

// What we would build

An iOS and Android app and a web workspace that start each report from the dispatched call, work offline in the car, capture photos and statements, route reports for supervisor review and keep a full audit trail. Built to pass the service's security review, with that review shown as a lead time.

// What is in it

// Stack

• React Native
• Next.js
• PostgreSQL
• CAD integration
• Azure Canada

// The problem

A police service tracks physical and digital evidence on paper logs between the property room, the forensic lab and court, and each transfer depends on a signature that can go missing.

// What we would build

Barcoded evidence labels printed at intake, every transfer scanned and signed, and digital files fingerprinted at intake with each fingerprint and transfer recorded on a private ledger the service and its partner forensic lab each run a node of, on servers the service controls. A well-audited database with signed logs often does this job alone, and we will say so.

// What is in it

// Stack

• Next.js
• Hyperledger Besu (private, permissioned)
• PostgreSQL
• Barcode label printers and scanners
• On-premise servers

// The problem

Departments in a region arrange mutual aid by phone, cannot see which engines and crews are available next door, and volunteer availability lives in a group chat.

// What we would build

A regional web board and app showing apparatus and crew availability across departments, reading incidents from the dispatch centre, with volunteer availability set from a phone and call-outs sent to the right members.

// What is in it

// Stack

• Next.js
• React Native
• PostgreSQL
• WebSockets
• AWS Canada

// The problem

Supervisors return a large share of reports for missing elements, and officers wait days to find out a report needs a change.

// What we would build

An assistant that checks a report against the service's own report standards before it is submitted, pointing out missing elements and inconsistencies for the officer to fix. It never writes the narrative. It runs on an open-source model on a GPU server inside the service, so no report leaves the building.

// What is in it

// Stack

• Llama or Mistral (open-source)
• vLLM
• PostgreSQL with pgvector
• Next.js
• Lenovo GPU server on premises

// The problem

A regional emergency management office tells residents about wildfires and floods through social media, a website and a sign-up list, and evacuation orders reach some people hours late.

// What we would build

An iOS and Android app and a web console for alerts by area, evacuation orders and alerts, reception centres and updates, in English and French, with each message's wording, area and time recorded. It complements the national public alerting system; it does not replace it.

// What is in it

// Stack

• React Native
• Next.js
• PostgreSQL with PostGIS
• Push and SMS services
• AWS Canada

// The problem

A fire department's annual report and council briefings are assembled by hand from dispatch exports and incident reports, and the same question gets different answers depending on who pulls the data.

// What we would build

A dashboard on your own servers that loads dispatch and incident report data every night, maps incidents by type and area, shows call volume by hour and season, and produces the annual report tables from the same agreed definitions.

// What is in it

// Stack

• PostgreSQL with PostGIS
• dbt
• Apache Superset
• Python
• Docker