NIMS & ICS aligned

Run the incident, not the software.

WatchKat is the emergency operations centre platform for counties, cities and agencies — one shared command picture covering incidents, FEMA community lifelines, ICS forms and org chart, mapping, resource requests and public alerting. Self-hosted, on your infrastructure, with a tamper-evident record of everything that happened.

Built by SARAem LLC · Deployed on your servers · No per-incident pricing

The problem

When the EOC activates, the tooling should disappear

Most emergency operations still run on a spreadsheet, a whiteboard and a group text. The record is reconstructed afterwards from memory. WatchKat is built so the documentation is a by-product of doing the work.

🗂️

One command picture

Incident status, lifelines, resources, assignments and the activity log all reference the same incident. Change something on one screen and every other position sees it live.

🧾

A defensible record

Every entry is timestamped and attributed. Corrections are amendments — the original is preserved and marked superseded, so the log holds up in an after-action review or a public-records request.

🏛️

Yours to run

Installs on your own server. No cloud tenancy, no data leaving your jurisdiction, and licences that verify entirely offline — the software never phones home.

Capabilities

Everything the EOC touches, in one place

Screens below are the live product — not mock-ups.

Community lifelines

FEMA's eight lifelines, reported the way you brief them

Track every lifeline component with a status, an impact statement and an estimated restoration time. Roll-ups drive the dashboard so command sees stabilisation at a glance rather than reading a list.

  • All eight lifelines with their standard components
  • Impact and restoration estimate captured with each change
  • Every status change mirrored into the incident activity log
  • Colour-blind-safe status marks — shape and label, never colour alone
● Operational ◆ Degraded ▲ Disrupted
Mapping & GIS

Draw the incident, don't describe it

Plot command posts, shelters and staging areas; draw evacuation zones and road closures. Features are stored as real geometry in PostGIS, so a zone can answer which points fall inside it.

  • Pins, lines, polygons and evacuation zones
  • GeoJSON and KML import for plans you already hold
  • Selectable basemap provider with your own API key
  • Reference overlay layers from your existing map services
ICS organisation

The command structure, filled and current

Assign the standard ICS positions by section — Command, Operations, Planning, Logistics and Finance/Admin. Assignment picks from your directory, so the org chart and the contact list stay the same set of people.

  • Standard ICS positions grouped by section
  • Assigning a filled position releases the previous holder automatically
  • Every assignment written to the activity log
  • Position counts per section show gaps at a glance
Resources

Requests with a decision trail

Typed inventory with an enforced status lifecycle, and a request queue where every approval, denial and fulfilment carries a reason back to the person who asked.

  • NIMS-typed resources with an eleven-state lifecycle
  • Requests capture category, priority, quantity, unit and justification
  • Denials require a reason; the requester is notified
  • Filter inventory by status and category as it grows
Public alerting

Two people before the public hears it

Draft, content-approve, then release. The server enforces the separation: the person who drafts cannot approve, and the approver cannot release. Released alerts emit standards compliant CAP 1.2 for onward distribution.

  • Two-person control enforced server-side, not by convention
  • Approvers see the full message body, not just a headline
  • Valid CAP 1.2 XML generated per alert
  • Everbridge dispatch adapter included
Activity log

ICS-214 that writes itself

The log is always on screen and always attributed. Status changes, assignments, requests and decisions all land in it automatically, alongside what your staff type.

  • Search and filter by type, priority and author
  • Amendments preserve the original and mark it superseded
  • Export any view to CSV for the after-action file
  • Live updates to every signed-in position

Security & accountability

Built to survive the review after the incident

Public agencies get audited. WatchKat is designed so the answers already exist.

Tamper-evident audit

Every administrative action is written to an append-only, SHA-256 hash-chained log. A built-in verifier proves the chain has not been altered.

Roles and capabilities

Six role tiers plus granular capability grants, scoped globally or to a single incident, with an approval queue for new accounts.

Modern credentials

Argon2id password hashing, breached-password screening, account lockout, session control and TOTP multi-factor with an enforceable policy.

Separate environments

Live and Training run side by side in the same install. Exercise data can never reach a live incident — the server blocks it at the write.

Records & disclosure

Full incident export for public-records requests, a data-classification banner across the apps, and legal-hold marking.

SIEM forwarding

Stream the audit log to your existing SIEM over syslog in CEF or RFC 5424 for continuous monitoring.

Accessibility

Built to WCAG 2.1 AA and Section 508 intent: keyboard navigation, screen-reader labelling, a high-contrast theme and colour-blind-safe status.

Offline licensing

Licences are Ed25519-signed and verified entirely offline. No licence server, no phone-home, no outbound dependency.

More screens

Admin, directory and incident management

The administration platform is a separate site, so day-to-day EOC staff never see it.

Incidents — every activation, past and present
Directory — agencies, mutual aid and 24-hour contacts
Audit & logs — with chain verification
Users & permissions
Security policy — enforced, not decorative
Sign-in — Live and Training, side by side

Deployment

Installs where your data already lives

A single server binary with PostgreSQL. No container platform to adopt, no cloud account to open, no per-seat metering.

On your Windows server

Runs as a Windows service with a control application for start, stop and status. Ships with an SBOM for supply-chain review.

On your Linux server

A single static binary plus PostgreSQL and PostGIS. Runs under systemd behind whichever reverse proxy and certificate authority you already use.

Disconnected sites

Licence validation is fully offline, so an install with no outbound internet works exactly the same as one with it.

See it running against your own scenario

Tell us your jurisdiction, roughly how many people staff your EOC, and what you use today. We will walk you through a live environment and answer the procurement questions properly — licensing, hosting, data ownership and accessibility.

Visit the live demo

Talk to us
info@saraem.com Email us

Demo credentials are issued on request — just ask.