An AI agent that runs your back office, under spend caps it cannot break.
Kerdos pays vendor invoices, bills your customers, procures, and keeps double-entry books, and anything above your caps waits for your approval on your phone.
What stops a robot from spending your money.
Kerdos runs behind six controls. Each one is a mechanism you can check, not a promise.
The cap holds in code
Checked at the payment call, not asked of a prompt.
You tap to approve
Spend over your threshold sends a card to your Telegram. It charges after you tap.
Decisions above a threshold are signed
A one-decision page is signed with a passkey or a six-digit code.
The ledger is hash-chained
Every action links to the one before it, so a change breaks the chain.
Egress is default-deny
The network policy is proven with Z3. The model never sees credentials.
It starts in rehearsal
Every deployment runs on test rails until you opt in, one rail at a time.
The whole back office, on one agent.
Installed once per business, it operates every function below under the same caps.
Vendor invoices are matched three ways against the purchase order and the receipt before anything pays.
Customer invoices and usage billing go out on Stripe, with webhook reconciliation on the way back.
Purchases run against a vendor allow-list and the budget line they belong to.
Recurring software and infrastructure costs track against their own caps.
Balanced double-entry books export as CSV and QuickBooks IIF.
Burn spikes, runway, and reserve arrive as concrete proposals. Approving one runs it under your caps.
Cash, runway, burn, pending approvals, and audit-chain badges on the owner phone.
Four steps to a back office you control.
Onboarding interview
We map your vendors, your customers, and how money moves through the business.
Caps and budgets
You set the master spend cap and a budget line for each function. The cap invariant is wired in.
Rehearsal month
Kerdos runs your real back office on Stripe test rails so you can watch every decision it makes.
Owner-gated go-live
Nothing touches real money until you opt in, one rail at a time.
One deployment, installed and run for you.
It runs in rehearsal until you approve go-live, and every dollar above your caps waits for your tap. That is the guarantee: mechanism, not promises.
- Onboarding interview
- Caps and budget-line configuration
- Vendor allow-list setup
- Telegram dashboard on your phone
- Rehearsal-mode first month
- Go-live only when you opt in
What owners ask first.
What happens when it gets something wrong?
It holds the action for your approval and never moves money above your caps. A wrong call waits for your tap instead of executing.
Will it spend real money on day one?
No. Every deployment starts in rehearsal on Stripe test rails. Moving real money is a deliberate opt-in, one rail at a time.
What will it not do?
It does not run live ads and it does not read your email inbox. You drop files in and it ingests them. There is no self-serve signup; it is installed per business.
Whose Stripe account does it use?
Yours. Virtual cards, invoices, usage billing, and webhook reconciliation all run on your own Stripe account.
What does my accountant get?
Balanced double-entry books as CSV and QuickBooks IIF, plus a hash-chained audit ledger they can verify.
How do approvals reach me?
On your phone. Spend over your threshold arrives in your Telegram chat, and higher-value decisions are signed with a passkey or a six-digit code.