Docs

Local-first by default

Every incident lives only in your browser's localStorage. There is no account, no server call, and no network dependency for the core console — you can compute deadlines even if your network is the thing that's compromised. The optional cloud tier is strictly opt-in.

The deterministic-law firewall

Deadlines, who-to-notify, and required letter contents are always computed by the rules engine from the versioned jurisdiction dataset — never by an AI model. When the BYO-AI copilot ships, it only fills narrative prose; it can never override the legal scaffolding. Every letter carries a banner saying so.

Core flow

1. Declare an incident → roles + append-only timeline.
2. Enter facts → the engine computes obligations + a live deadline clock.
3. Launch a playbook → tasks auto-created.
4. Generate jurisdiction-correct letters; export the deadline calendar.
5. Run tabletops to test the plan; generate the after-action report.

Help Center

Exhaustive, self-service support documentation — getting started, the incident workflow, obligation clocks, notification letters, timeline integrity, the what-changed feed, opt-in scheduled push, security & privacy, and a full troubleshooting / FAQ with a "How do I…?" recipe index.

Open the Help Center