thin.host vs tiiny.host
tiiny.host makes sharing a single HTML file, zip or PDF quick for non-developers, with QR codes, passwords and analytics built in. thin.host covers quick sharing too, and adds build-folder deploys from agents, framework guides, and a custom domain on a free account.
Facts about tiiny.host are taken from tiiny.host'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 | tiiny.host | |
|---|---|---|
| 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. | 1 active project, 3 MB uploads, 5,000 visits and 5 GB bandwidth a month, with a tiiny.host banner and no custom domain. |
| Cheapest paid plan | Domain API tiers: Indie $29/month, Platform $199/month. End users pay $8/month per domain provisioned through the claim flow. | Tiny, $9/month (1 project, 25 MB uploads). Custom domains start with Solo, $18/month. |
| Custom domains | Yes, several per site, added from the dashboard with a CNAME to cname.thin.host. | Solo plan and above. |
| HTTPS | Automatic for custom domains and thin.host subdomains. | Included with custom domains on paid plans. |
| 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 MCP server (publish, update and delete projects) on Solo and above, authenticated with an API key. |
| Transactional email | Yes: transactional email over MCP, REST or SMTP from a verified sending domain (access is approved per account). | No transactional email; the Pro plan can capture visitor emails. |
| 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. | Drag and drop a zip or file, paste HTML, an API (Solo and above), MCP, Zapier and Make. |
| Deploy without an account | No, an account is needed to deploy. | Unclear: tiiny.host's own pages disagree on whether you can upload without signing up. |
| Server-side features | Static files only, plus built-in form capture and password or email gating. No serverless functions. | None. Password protection, analytics and email capture are built in. |
When tiiny.host is the better choice
- You share single files or PDFs and want QR codes, analytics and visitor email capture built in.
- The simplest possible upload page for non-technical teammates.
When thin.host is the better choice
- Framework builds: up to 30 MB per upload, or 150 MB through the local MCP server.
- A custom domain and MCP access on a free account.
- Transactional email for the app behind the site.
Moving from tiiny.host to thin.host
- Use your local copy of the files, or download them from tiiny.host (archived projects offer a download).
- 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. - Recreate password protection in the site's Access Protection settings.
- Move the domain: add it to the site under Custom Domains in the thin.host dashboard, change its DNS record to the CNAME the dashboard shows (cname.thin.host), and remove it from tiiny.host once thin.host's certificate is live.
What does not carry over
- Analytics and link-tracking history
- Captured email lists (thin.host's form capture collects new submissions)
- QR codes
Deploy commands for your framework are in the deploy guides; agent setup is in Quickstart (MCP).
FAQ
Can I password-protect a page like on tiiny.host?
Yes. Password or email-allowlist protection can be set for a whole site or a single page in the dashboard.
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
tiiny.host facts checked on 2026-10-14 against: