Offline DBA incident triage

The triage kit that runs where the cloud can't reach.

Decision trees, error and wait-type lookup, and DR runbooks for your database fleet — in one HTML file that opens behind bank firewalls, on jump boxes, and in air-gapped rooms. No login, no calls home, nothing to whitelist.

Zero network calls Runs from a local file Nothing leaves the browser
The gap

The best database tools stop at the firewall. The incident doesn't.

DBAs in banks, hospitals, and regulated shops work on locked-down networks where the SaaS monitoring and the Q&A sites everyone else googles are simply blocked. When Always On won't fail over at 2am, they're alone with a search bar that can't reach anything.

Cloud monitoring & SaaS runbooks

Blocked by egress rules. The one moment you need them, the proxy returns a block page.

Q&A sites & vendor docs

Often filtered on secure networks, and never structured as a decision path under pressure.

Tribal knowledge in someone's head

The senior DBA who knows the fix is asleep, and the runbook is a stale wiki page.

Field Kit

One self-contained file you carry in. Curated senior-DBA judgment, structured as triage, working exactly where everything else is dark.

One kit, every engine

Built for the whole database fleet — not one vendor.

Real shops run more than one engine. Field Kit shares one triage model across all of them: decision trees, an error / wait / state lookup, health scripts, and DR runbooks — tuned per engine.

Live

SQL Server

Always On AG triage, ~55 error codes, 43 wait types, DB-state decoder, seeding & file-move runbooks, fleet audit.

v1 · shipping now
Next

PostgreSQL & RDS

Streaming replication lag, WAL/archive triage, failover & Multi-AZ, RDS event decoder, pg_stat_activity playbooks.

in design
Planned

Oracle

Data Guard role transitions, ORA- code lookup, ASM & RAC, standby lag, RMAN restore paths.

roadmap
Planned

MongoDB

Replica-set elections, oplog window, shard balancer, secondary staleness, member-state decoder.

roadmap
How it works

Firewall-proof by construction, not by permission.

01 · No network, ever

Everything — the trees, the datasets, the search — is in the page. No API, no CDN, no fonts to fetch. A strict promise you can verify in DevTools: zero requests.

02 · Carry it anywhere

Hosted on the open web for convenience, but the same file runs from a USB stick, an email attachment, or a jump box with no internet at all.

03 · Your data stays yours

Your triage log and any custom runbooks live only in your browser's local storage. Nothing is uploaded, so nothing can leak.

Guided triage trees

Symptom → cause → numbered fix, with a jump-chip into any branch.

Error / wait / state lookup

Fuzzy search — type the number or the message. Steps, query, and GUI path.

Health & audit scripts

Copy-paste diagnostics + a PowerShell fleet runner for whole estates.

DR & migration runbooks

Seeding, zero-downtime file moves, permission builders, failover paths.

Access

Free to use. Pay when it saves your fleet.

The public kit stays free and open — it's how people find us. The paid tiers are for teams who want it inside their walls, connected, and covering every engine.

Open

Public Kit

Free · forever
  • SQL Server triage, lookup & runbooks
  • Offline single-file, carry anywhere
  • Editable trees in your browser
  • Community error/wait/state library
Open it now
For teams

Field Kit Pro

per-seat · early access
  • Every engine: Postgres, Oracle, Mongo, RDS
  • Connected local console (runs the queries for you, on your box)
  • Import your own runbooks & escalation contacts
  • Private hosting inside your network
Request early access
Assist

Copilot (local AI)

add-on
  • "Explain this in my environment" — on a model you host
  • Runs on your hardware, not a cloud API
  • Turns raw errorlog paste into a ranked triage plan
  • No prompt or data ever leaves your network
Talk to us
Grand Canyon Computers · ReliabilityOps

Try the kit that works when nothing else can reach you.

Open the SQL Server kit now — no signup, no network. For every-engine coverage, the connected console, or private hosting, tell us what your fleet runs.