What you carry

This is the page we would want to read before paying for something like this. It is here before the price, not after it.

Your plan limits assume ordinary, individual use

Claude’s plans — and Codex’s — are sold for a person working. Agents that run while you sleep can exhaust a Pro or Max plan, and the limit is reached on your account, because it is your account they are signed in to. We cannot raise it, and we do not pay it. Start with one agent and one duty, watch what it spends, and grow from there.

If a provider decides your use is outside its terms, that decision lands on you. We support the shape the providers allow: your subscription, your machine, your session. We never hold a provider credential, which is the condition that makes any of this legitimate. Grok is not supported at all, because its terms forbid it.

Your provider login expires, and only you can renew it

A Claude session on one of your machines lasts weeks, not years. When it runs out, that machine’s agents stop working until somebody signs in again — and that somebody is you. The app makes it two clicks and one paste: it opens the provider’s own page in your browser and the hub types the code back on the right machine. We are not allowed to do it for you, and we would not want to be.

What this means in practice: a fleet left alone for long enough goes quiet. The apps tell you before it does.

An agent you grant access to acts with that access

An agent with your GitHub App installed can write to the repositories you chose. An agent with a login from your vault can act in that service as that login. It is software, it is new, and it will sometimes be wrong in a way a person would not be.

What we build around that: you decide what each agent may reach, one grant at a time; every change of access and every owner decision is a commit you can read and revert; and anything an agent cannot do by itself, it asks you for, on your phone. What we cannot build around it: the access itself. Give an agent the keys to something that cannot be undone and it may, one day, use them.

You hold the repository keys, not us. Each customer installs their own GitHub App in their own organisation, and GitHub hands the private key to their hub. We have no token, no key and no way in.

The machine is yours, which is the good news and the work

You own the server, the data, the credentials and the record. Nobody can switch your fleet off, because nothing of ours is in its path — no licence check, no call home, no expiry. The same fact makes the backups, the disk and the bill yours. Our updates keep the software current; they do not keep your machine alive.

If you stop paying, your hub keeps running exactly as it is. The updates, the app builds, the notifications to your phone and we stop. Your agents carry on until the day a platform changes under them.

What we hold

An email address, a payment record at Stripe, an entitlement for a fleet id that is derived from nothing about you, and — only if you switch it on — a heartbeat that carries version numbers and check results. No task text, no names of people, no repository names, no secrets. The privacy page says it in full.

Anything here you want to put to us plainly first: support@founderizer.com.