Docs that stay alive because agents keep them honest.
Link your repos, and agents draft RFCs, keep runbooks current, write incident retros, and answer 'how does this work?' against the actual codebase, all in markdown, all in git.
Open source · self-hosted · bring your own AI
The status quo
Your docs are wrong the moment they're written
Runbooks and architecture docs rot the second the code changes.
Onboarding is tribal knowledge and a graveyard of stale wiki pages.
Incident retros never get written because everyone's already on the next fire.
Your AI team
Onboard the team engineering actually needs
Each agent is a Markdown persona with a goal, skills, and a schedule. Edit the file, the agent updates. Delete it, it's gone. Every change is in git.
Docs Keeper
MaintenanceWatches linked repos and flags docs that drifted from the code.
RFC Drafter
DesignTurns a problem statement into a structured RFC with prior-art links.
Incident Scribe
ReliabilityDrafts the retro from the timeline so the team just edits and ships it.
Onboarding Guide
Ramp-upAnswers 'where is X' and 'how does Y work' from the real codebase.
Always-on
Work that runs on a schedule, not when someone remembers
Routines are scheduled prompts attached to an agent. Same agent, same shape, every time, 24/7, whether or not anyone's online.
Re-check the runbooks that reference the changed paths.
Draft a blameless retro from the timeline and chat thread.
Summarize merged work into a changelog the whole company can read.
Outcomes
to a useful, current doc
of incidents get a retro
history on every doc change
Illustrative. Real benchmarks coming as teams report them.
Why Cabinet
The only one of these you actually own
Your work lives on disk
Everything is Markdown in a folder you own. Grep it, git it, back it up. No export, no lock-in, no vendor holding your knowledge hostage.
Bring your own AI
Cabinet routes to the model accounts you already pay for. No bundled inference marked up on top, no new AI vendor through procurement.
Self-hosted by default
Run it on your machine or your cloud. Your data never leaves your infrastructure: sovereignty first, with SSO and audit on the enterprise track.
Works with what engineering already uses
From the field
Illustrativeof incidents now get a retro
“Docs used to rot the moment code changed. Now an agent flags the drift and drafts the retro, and we just edit and ship.”
Staff Engineer · Fintech platform
Hire your Engineering team. Keep your data.
Start free in minutes, or get a guided walkthrough. Begin from the cabinet:eng-handbook template.
Cabinet for every team