The whole price list
| What | Limit |
|---|---|
| Private hosting | Free. Unlimited pages. |
| Publishes per day | Unlimited — no daily cap on uploads. |
| Active sites | Unlimited. |
| Custom domains | Unlimited. |
| Seats | Unlimited. There is no per-seat charge and no workspace to buy. |
| Viewers | Unlimited, and they never need an account. |
| Retention | Whatever expiry you set, up to never. |
| Upload size | MAX_UPLOAD_BYTES in your own config. |
So what does it actually cost?
Whatever Cloudflare bills you, which for the workloads this thing was built for is typically nothing. Workers, D1, R2, Queues and scheduled triggers all have free allowances; a few hundred private pages and their traffic sits inside them comfortably.
Where the money would go if it went anywhere
| Component | What it does here | Free allowance |
|---|---|---|
| Workers | The runtime — every request | Generous daily request budget |
| D1 | Site records, feedback, counters | Row reads and writes per day |
| R2 | The stored documents | Storage plus zero egress fees |
| Queues / Cron | Purge and the daily digest | Included at this scale |
| Resend | One outbound email path | A free tier for low volume |
Three workloads, honestly estimated
What you are not paying for
- A per-publish fee. The first publish and the ten-thousandth cost the same: nothing.
- A seat. Add colleagues without arithmetic.
- Custom domains as an upsell — they are two DNS records, not a plan feature.
- Analytics as an add-on. Engagement data is part of the page.
Why the original had tiers and this does not
A hosted product carries support, abuse handling and a margin, and tiers are how that gets paid for. None of it applies to a deployment running in your own account: the infrastructure bills you directly, and there is no one in between to price the difference.
The limits that do exist
| Limit | Set by | Why |
|---|---|---|
| Upload size | MAX_UPLOAD_BYTES | A runaway publish should fail fast. |
| Anonymous publish rate | Fixed window per address | An open endpoint attracts a file host. |
| Platform ceilings | Cloudflare | Request duration, object size — the usual physics. |
Raise them by editing the config and redeploying. That is the entire negotiation.
Anonymous publishing
Free, no account, rate-limited by address, 24-hour link. It exists so the first thing you do here does not require a decision:
curl -X POST https://read.botook.ai/v1/publish -F file=@index.htmlKeyed publishing
Also free. A key gets you permanence, gates, custom domains, engagement data and the dashboard.
claude mcp add --transport http opentree https://read.botook.ai/mcp \
--header "Authorization: Bearer otr_live_YOUR_KEY"What about support?
It is source-available software you are running. Read the code, open an issue, or mail hello@botook.ai. Nobody is on call for your deployment except you.
Will this start charging?
It cannot. There is no billing code in it and no account to bill — the deployment is yours. If you stop paying Cloudflare, Cloudflare stops running it; that is the only commercial relationship involved.
Humans and agents pay the same
Nothing. There is no per-call rail here, deliberately — see agent payments for the machinery that was left out and why.
The ceiling that is actually real
One limit is not yours to set, and pretending otherwise would be the dishonest part of a page like this. The free tier of the underlying platform caps daily requests to the worker, and every page view, API call and preview fetch counts against it. For the traffic these pages see it is not close to binding — but an automated test suite that walks the whole site on a loop can reach it, and when it does, the response comes from the edge rather than from this deployment:
$ curl -sD- https://read.botook.ai/health
HTTP/2 429
server: cloudflare
# error code 1027 — a platform daily limit, not this service's rate limiterThe tell is that there is no retry-after header and the body is not this
service's JSON error shape; a path that has no rate limit of its own, like /health,
answers 429 as well, which means the request never reached the worker. It resets at
00:00 UTC, and raising it is a matter of the platform's paid tier rather than anything
in this configuration.
Compared with the hosted alternatives
| Typical hosted product | Here | |
|---|---|---|
| Monthly cost | A subscription per month | Your own infrastructure bill |
| Sites | Capped by tier | Unlimited |
| Custom domains | A paid feature | Included |
| Seats | Per-seat | Not a concept |
| Your data | On their infrastructure | In your account |
Questions
Is there a trial?
There is nothing to trial. Publish anonymously without an account.
What if I outgrow the free allowances?
You pay Cloudflare's normal rates. There is no tier in between, and no feature gets switched off.
Can I run it for a team?
Yes — see self-host.