Pricing
Config sync is free. Conversations are $1 a GB.
The clai CLI is free and open source, and so are the Hub and syncing your config. Synced conversations cost $1 per started GB a month.
Local CLI
$0forever
One static Go binary on your machine, with your own vendor keys.
- Open source, MIT licensed
- Your own vendor keys or local Ollama
- No account; nothing sent to clai.chat until you sync or publish
Hub and config sync
$0no card
Share configs, and keep yours the same on every machine.
- Read and download any Hub config, no account
- Publish and rate with a sign-in
- Profiles, MCP servers, skills, shell contexts, mode configs and themes synced
- Up to 1 GB of config, no card, no trial
Conversation sync
$1per started GB a month
Every session from every coding agent, in one store and on every machine.
- Billed on the month's peak, rounded up to whole GB
- Any conversation storage is at least $1 a month
- A card on file before your first conversation commit
- Pulls keep working even if a payment fails
How conversations are billed
- Metered on the peak
- You pay for the month's highest conversation storage, rounded up to whole GB. A month with none costs nothing.
- Config is free
- Profiles, MCP servers, skills, shell contexts, mode configs and themes sync for free, up to 1 GB, on as many machines as you use.
- Imports count too
- Sessions clai found from Claude Code, Codex, Cursor, OpenCode, Gemini CLI, Qwen, Antigravity or pi are committed with
--imports, and then count like any other.
| Peak storage | You pay |
|---|---|
| Config only | $0 |
| 40 MB of conversations | $1 |
| 1 GB | $1 |
| 1.4 GB | $2 |
| 10 GB | $10 |
If a payment fails
Days 1 to 7
Stripe retries the payment. Everything keeps working.
After 7 days
Commits are refused until it is paid. Pulls keep working.
After 30 days
Your synced conversations are deleted. The config store is never trimmed.
Connect the CLI
Run clai cloud login once per machine and approve the code in your browser. Logging in syncs nothing: like git, you pull and commit when you want to, and a query never waits for the network. A config file that holds an API key is never uploaded. Conversations are uploaded as they are and are not end-to-end encrypted, so keep secrets out of the ones you commit. A Hub config is still a file you download; see Share and rate configs.
clai cloud login # once per machine clai cloud pull # bring in other machines clai cloud commit # send what changed
Questions
Do I need an account to read a config?
No. Every Hub page and every raw config file is public. An account is only needed to publish, rate or sync.
Is there a hosted sync or backup service?
Yes, and it is opt-in. Nothing syncs until you run clai cloud commit, and no key is uploaded: a config that holds one is skipped. Without it the CLI runs entirely on your machine.
What does an account hold?
Your email, the sessions that keep you signed in, the configs you published, the ratings you gave, your CLI logins, and what you commit. See Privacy.
What happens when I delete my account?
Your published configs, every rating you gave or received, and your synced stores are deleted with it, and a card subscription is cancelled at once.
How is conversation storage measured?
By the size of each distinct file you committed to the conversation store, as it sits on your disk, images included. Two paths with the same bytes count once. A month is billed on its peak, so deleting lowers the next month, not the current one.
Where is my data stored, and is it encrypted?
In Cloudflare R2, which encrypts every stored object at rest. It is not end-to-end encrypted: our Worker reads the files to store and return them. A config file that holds an API key is never uploaded, but conversations are uploaded as they are.
Start with the CLI
It runs on its own. Add the Hub and sync when you want them.
Priced to last, not to extract
I'm deliberately not pricing clai.chat to get as much as I can out of the people who use it. I'd rather trust that careful engineering, an implementation that's cheap to run, and fair service are worth more than maximising profit. Config costs almost nothing to store, so it's free. Conversations grow without end, so they cost roughly what keeping them costs. The goal is for clai.chat to pay for itself, and keep running.
Lorentz, who builds clai