thin.host vs Cloudflare Pages
Cloudflare Pages serves static sites from Cloudflare's network with unlimited free static requests, and grows into Workers when a site needs code; Cloudflare now suggests starting new projects on Workers static assets. thin.host is narrower: static hosting deployed by agents, with domains, access gating and email in one account.
Facts about Cloudflare Pages are taken from Cloudflare Pages's own pricing and documentation pages as of October 2026 (checked 2026-10-14) and listed under Sources. Plans change; check the vendor's page before you decide.
Side by side
| thin.host | Cloudflare Pages | |
|---|---|---|
| Free tier | Free account: hosted sites at thin.host/s/<slug>/ and free <name>.thin.host subdomains. The domain API's free platform tier covers 3 domains. | Unlimited static-asset requests, 500 builds a month, 100 projects and 20,000 files per site. |
| Cheapest paid plan | Domain API tiers: Indie $29/month, Platform $199/month. End users pay $8/month per domain provisioned through the claim flow. | Workers Paid, from $5 a month per account. |
| Custom domains | Yes, several per site, added from the dashboard with a CNAME to cname.thin.host. | Yes, up to 100 per Pages project; an apex domain needs its DNS on Cloudflare. |
| HTTPS | Automatic for custom domains and thin.host subdomains. | Automatic certificates for custom domains. |
| AI agent / MCP support | Official hosted MCP server (thin.host/mcp, OAuth 2.1) plus a local server (uvx thinhost-mcp), a Claude Code plugin and a REST API. | Official Cloudflare MCP servers (API and docs), and temporary deploys for agents with wrangler deploy --temporary. |
| Transactional email | Yes: transactional email over MCP, REST or SMTP from a verified sending domain (access is approved per account). | Yes: Email Sending (public beta since April 2026) on Workers Paid, 3,000 emails a month included. |
| How you deploy | MCP tool call, one REST upload of a zip, or drag-and-drop in the dashboard. No Git integration: you build locally or in CI. | wrangler pages deploy <dir>, Git integration, dashboard upload (up to 1,000 files) and an API. |
| Deploy without an account | No, an account is needed to deploy. | Yes: Cloudflare Drop and wrangler --temporary; claim within 60 minutes to keep the site. |
| Server-side features | Static files only, plus built-in form capture and password or email gating. No serverless functions. | Pages Functions and the Workers platform (KV, R2, D1, Durable Objects). |
When Cloudflare Pages is the better choice
- High-traffic static sites: static requests are free and unlimited on a global network.
- The site will need server logic, storage or queues later, all on the same platform.
When thin.host is the better choice
- You want a root domain without moving your DNS to Cloudflare.
- An agent should publish with one MCP call, and hosting, domains and email should share one account.
- Pages need a password or an email allowlist set from a dashboard.
Moving from Cloudflare Pages to thin.host
- Build locally with the project's build command and take its output directory.
- Publish the folder: ask your agent to publish it to thin.host (MCP), or zip it and run
curl -F file=@site.zip -H "Authorization: Bearer $THINHOST_API_KEY" https://thin.host/v1/websites/archive. Check the site at its/s/<slug>/preview URL. - Plan for redirects: thin.host does not read
_redirects, and redirects are not yet self-serve. Keep URL paths the same where you can; for a page that moved, deploy a small HTML page with ameta refreshand a canonical link to the new address._headersand_routes.jsonhave no equivalent. - Move the domain: add it under Custom Domains in the thin.host dashboard. If its DNS stays on Cloudflare, change the record to a DNS-only (grey cloud) CNAME to cname.thin.host so thin.host can issue the certificate, then remove the domain from the Pages project.
What does not carry over
- _redirects, _headers and _routes.json
- Pages Functions and Workers bindings
- Preview deployments per branch
Deploy commands for your framework are in the deploy guides; agent setup is in Quickstart (MCP).
FAQ
Do I have to move my DNS away from Cloudflare?
No. Keep DNS on Cloudflare and point a DNS-only CNAME record at cname.thin.host.
Can I deploy to thin.host without an account?
No. Sign up (free), then deploy with an API key, the MCP server or the dashboard's upload page.
Do I have to move my DNS provider?
No. Keep DNS where it is and create the record the dashboard shows, a CNAME to cname.thin.host. TLS is issued automatically once it resolves.
Sources
Cloudflare Pages facts checked on 2026-10-14 against: