Hosted isn't self-hosting — here's the split
Self-hosting means forking the code and running the whole thing yourself. Hosted is
different: we run the brain — the wallet, the approvals, the audit log,
the updates, all of it — and you keep one small lockbox: a last-mile
worker on your own Cloudflare, where your key actually seals. Only ciphertext ever
reaches us. That one worker is the whole reason your key sealing on your side is a fact
you can check, not a promise you have to trust.
Setup happens once, and there's nothing to generate: deploy the lockbox
(one click to Cloudflare), paste its URL into the wallet,
tap approve. We claim the link for you — no keys to issue, no tokens to
copy. Your agent can even do the wiring; you just approve.
You're not paying to do it yourself — you're paying us to run the hard part. The lockbox
is just what keeps us honest.
Why pay me $8 a month?
Fair question — the code's open, you could fork it for free. Here's the honest line:
self-host and you run everything. Pay the $8 and I run everything — the wallet,
the approvals, the audit, the upkeep — while your key still seals in a lockbox only you
control. You're buying your way out of the ops, not out of the sovereignty.
This is built by one person, for people like me — indie devs handing API keys to agents
and rightly uneasy about it. It's priced to stay small and honest, not to chase a
valuation. Business is welcome to pay or self-host, but it doesn't get to steer the
roadmap. Ask for a compliance feature and the answer is simple: the code's open — host
it yourself. That's the deal, and it's not changing.
Want to run the brain yourself too — not just hold the key? That's self-host, and it's
free.