thin.host vs GitHub Pages
GitHub Pages publishes a site straight from a GitHub repository and is free for public repositories. thin.host takes an uploaded build instead of a repository, so an agent can publish without Git, and adds access gating and transactional email.
Facts about GitHub Pages are taken from GitHub 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 | GitHub 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. | Free for public repositories on GitHub Free: sites up to 1 GB, a soft 100 GB/month bandwidth limit, and not meant as free hosting for an online business, e-commerce or SaaS. |
| Cheapest paid plan | Domain API tiers: Indie $29/month, Platform $199/month. End users pay $8/month per domain provisioned through the claim flow. | Publishing from private repositories needs GitHub Pro, Team (listed at $4 per user per month) or Enterprise. |
| Custom domains | Yes, several per site, added from the dashboard with a CNAME to cname.thin.host. | Yes, apex domains and subdomains. |
| HTTPS | Automatic for custom domains and thin.host subdomains. | A Let's Encrypt certificate once DNS is correct; Enforce HTTPS is a separate setting. |
| 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. | No Pages-specific MCP server. GitHub's official MCP server works with repositories and Actions. |
| Transactional email | Yes: transactional email over MCP, REST or SMTP from a verified sending domain (access is approved per account). | No. |
| 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. | git push to a publishing branch (root or /docs), or a GitHub Actions workflow. |
| Deploy without an account | No, an account is needed to deploy. | No, a GitHub account and repository are required. |
| Server-side features | Static files only, plus built-in form capture and password or email gating. No serverless functions. | None. |
When GitHub Pages is the better choice
- The site is the docs or homepage of a repository and should live next to the code.
- You want free hosting for an open-source project, built by GitHub Actions on every push.
When thin.host is the better choice
- An agent publishes the site from a folder or zip, with no repository involved.
- Some pages need a password or an email allowlist, set from the dashboard.
- The app also needs to send transactional email.
Moving from GitHub Pages to thin.host
- Build the site yourself: a branch-published site is built with Jekyll, so run
bundle exec jekyll buildand use_site/(see the Jekyll guide); an Actions-built site runs the same build command locally. - 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. - Keep deploying on push if you like: add a workflow step that zips the build and POSTs it to
/v1/websites/<slug>/archive, with the API key in a repository secret. - 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 the repository's Pages settings once thin.host's certificate is live.
What does not carry over
- Automatic builds on push (replace with a CI step that calls the archive API)
- The CNAME file (the domain is set in the dashboard)
- username.github.io addresses (update links that point at them)
Deploy commands for your framework are in the deploy guides; agent setup is in Quickstart (MCP).
FAQ
Can I keep deploying on every git push?
Yes. Add a GitHub Actions step that zips the build output and POSTs it to /v1/websites/<slug>/archive with an API key stored as a secret; files missing from the new zip are removed.
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
GitHub Pages facts checked on 2026-10-14 against: