Security software

// The problem

A guard company proves its patrols with paper checkpoint sheets, and its guards often work in parking garages and basements where a phone has no signal.

// What we would build

A guard app for iPhone and Android that scans NFC tags at each checkpoint, records the time and place even without signal and syncs later, takes incident notes and photos, and shows supervisors live tours and missed checkpoints on a web console.

// What is in it

// Stack

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

// The problem

A security firm builds its schedule in an old spreadsheet full of macros that one person understands, and finds out a guard's licence has lapsed only when a client asks.

// What we would build

We replace the spreadsheet with a scheduling app that fills posts from qualified guards, tracks licence, first aid and site training expiry dates, warns before anything lapses, and sends approved hours to payroll. Licence rules come from your compliance lead.

// What is in it

// Stack

• Next.js
• PostgreSQL
• Twilio
• Payroll API
• DigitalOcean Toronto

// The problem

A security company's clients get incident reports as email attachments in different formats, and ask the office for post orders and visit logs by phone.

// What we would build

A client portal designed around your brand where each client sees its own sites, post orders, tour history and incident reports, signs off on changes to post orders, and gets notified of incidents the way it prefers.

// What is in it

// Stack

• Next.js
• PostgreSQL
• Figma
• S3-compatible storage
• DigitalOcean Toronto

// The problem

An alarm monitoring firm keeps signals in its monitoring software, access events in two access-control systems and contracts in its billing system, and builds every invoice and client report by hand.

// What we would build

An integration hub that reads signals, events and accounts from each system through its published API, joins them by site and client, and passes billing events and report data on to your billing system and client portal. It reads only: it never arms, disarms or unlocks anything.

// What is in it

// Stack

• Node.js
• PostgreSQL
• OpenAPI
• Vendor APIs
• DigitalOcean Toronto

// The problem

Guards write incident notes in a hurry, supervisors spend hours turning them into client reports, and the reports differ from guard to guard.

// What we would build

An assistant that turns a guard's notes and photos into a first-pass report in the client's format for the supervisor to check and send, on an open-source model in your own cloud account so incident details stay private. It drafts; the supervisor decides what is sent.

// What is in it

// Stack

• Llama or Mistral (open-source)
• vLLM
• PostgreSQL with pgvector
• Next.js
• DigitalOcean GPU

// The problem

A guard company's managers cannot see hours scheduled against hours billed, or which sites keep missing checkpoints, without a week of spreadsheet work.

// What we would build

A dashboard over your scheduling, tours and monitoring data showing hours scheduled, worked and billed, missed checkpoints by site and alarm volumes by client, hosted and monitored by us with priority support.

// What is in it

// Stack

• Next.js
• PostgreSQL
• Metabase
• AWS Canada

// The problem

A security firm and a large client sometimes disagree about what an incident report said at the time, and an emailed PDF proves little once it has been forwarded and edited.

// What we would build

Each incident report and its photos are fingerprinted when the supervisor sends them, and the fingerprint is recorded on a private permissioned ledger that the firm and the client each run a node of, so either side can check a report has not changed. A signed PDF often does this job; the ledger helps when several clients or contractors share one record.

// What is in it

// Stack

• Next.js
• Hyperledger Besu (private, permissioned)
• PostgreSQL
• S3-compatible storage
• DigitalOcean Toronto