This is the first in a series where we walk through the actual stack we run Inside Intelligence on — the same self-hosted, agent-driven infrastructure we sell as Operator. The point isn't to show off. It's to prove something: the "operations team in a box" isn't a slogan. It's the system we run our own company on.
We start with the least glamorous, most important piece: the books.
Why accounting, first
Every business runs on money, and money runs on records. If you can't trust the books, you can't trust anything else. So when we decided to dogfood our own stack, accounting was the first thing we put on it — not because it's exciting, but because it's the thing that has to be right.
We run a self-hosted accounting application on our own hardware — on our private infrastructure, never exposed to the internet. The database, the app, the whole thing lives in our building, under our control.
The part that matters: an agent drives the books
Here's where it stops being "we installed accounting software" and becomes Operator. We didn't just stand up a bookkeeping system and log in manually. We wired it so an agent can drive it — the same way Operator would drive a client's books.
That meant three things, and each one is a real decision, not a checkbox:
- Secrets live in a vault, not in config files. The database password, the app key, the API credentials — all in our secrets vault, pulled once at startup into memory, never written to disk. No plaintext secrets sitting in a repo.
- A least-privilege API user. The agent doesn't log in as the owner. It has its own account with exactly the permissions it needs to read and write the books — and it can't touch user management. If the agent is ever compromised, it can't create accounts or escalate.
- The agent is the operator. It can create invoices, record transactions, reconcile — through the API, on a schedule, without a human in the loop. That's the difference between software and an operations team.
We don't sell software. We sell the operations team that runs it. The books are proof: an agent, on our own hardware, keeping the company's records — with the same discipline we'd bring to a client's.
One honest wrinkle
Self-hosting isn't frictionless. Some off-the-shelf software gates features behind a hosted plan even when you run it yourself. When we hit that, we removed the cloud-only restriction — we run the software, we're licensed to use it, and the gate was artificial. So we patched it, kept a backup, and moved on. That's the kind of thing you only discover by actually running the thing — which is exactly why we dogfood.
What this means for you
If you run a law, medical, financial, or licensed-trade office, you don't care about our bookkeeping software. You care about this: the same system that keeps our books can keep yours. An agent that reads your files, drafts your work, and never lets a byte leave the building — running on the same discipline we hold ourselves to.
We're not asking you to trust a promise. We're showing you the receipts.
We'll walk through the rest of the stack — ticketing, the wiki, the vault — and then tie it all together with how Operator uses the whole thing. Each piece is a real system we run, not a slide.
← Back to Field Notes