The recurring work that runs the company, running itself.
SOPs, vendor reviews, board-prep packets, and reconciliations become scheduled routines. The institutional knowledge that usually lives in one ops person's head lives in files instead.
Open source · self-hosted · bring your own AI
The status quo
Ops is a thousand recurring tasks held by memory
Process lives in one person's head and a folder of out-of-date SOPs.
Recurring reports are assembled by hand, the same way, every single week.
Data has to be reconciled across tools that don't talk to each other.
Your AI team
Onboard the team operations 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.
Ops Coordinator
ProcessKeeps SOPs current and runs the recurring checklist so nothing slips.
Reporting Analyst
ReportingAssembles the weekly and monthly packets from source exports.
Vendor Watch
SpendTracks renewals, flags overlap, and drafts the review agenda.
Reconciler
DataCross-checks numbers across CSV exports and flags mismatches.
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.
Run the ops checklist and assign anything overdue.
Assemble the board-prep packet from the latest exports.
Open a vendor review with usage and cost context.
Outcomes
on recurring packets
process that outlives any one person
things falling through cracks
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 operations already uses
From the field
Illustrativeon the monthly board packet
“The recurring work that used to live in my head is documented and scheduled. The packet assembles itself from the source exports.”
Head of Ops · Scale-up
Hire your Operations team. Keep your data.
Start free in minutes, or get a guided walkthrough. Begin from the cabinet:ops-room template.
Cabinet for every team