Declare incidents, assign responders, track timelines, write postmortems. Incident.io without the $8/user/mo. Your incident management process on your own infrastructure.
When regulators or clients ask where your incidents data is stored, the best answer is a specific server you own in a specific jurisdiction you chose. Inquest makes that answer straightforward because the data never leaves your infrastructure.
A regulated company runs Inquest inside their air-gapped network. No data leaves the building. Compliance auditors can inspect the SQLite file directly. When the team needs a report, they query the API and format the output however the auditor expects.
The data model stores each incident with 6 fields: title, severity, status, commander, root cause. All fields are queryable through the search API. The dashboard renders incidents as cards with color-coded status indicators and inline metadata. Creating, editing, and deleting records is immediate — no save-and-deploy cycle.
GET /api/incidents — List all incidents. Supports ?q=keyword for search and ?status=value for filteringPOST /api/incidents — Create a new incident. Send JSON with at least titleGET /api/incidents/{id} — Fetch one incident by IDPUT /api/incidents/{id} — Update fields on an existing incidentDELETE /api/incidents/{id} — Remove a incidentGET /api/stats — Returns total count and breakdown by statusGET /api/health — Returns {"status":"ok"} for uptime monitoringSelf-hosted incident manager. Self-hosted on your infrastructure. Your data never leaves your server.
curl -fsSL https://stockyard.dev/install.sh | sh -s -- --tool inquest
PORT=9340 ./inquest
http://localhost:9340
Single binary. Embedded SQLite. No Docker. No database. No dependencies.
Your license key arrives by email within 5 minutes of checkout. Set it as an environment variable and restart the binary.
export INQUEST_LICENSE_KEY=stockyard_xxxxxxxxxxxxxxxxxxxx ./inquest
No cloud connectivity required. The binary validates the key offline with Ed25519 signatures.