Yetty vs GitHub Pages
GitHub Pages is free static hosting for developers who edit via git. Yetty is the same site, fully looked after - no git, no code.
GitHub Pages is a great free way to host static files from a repo, and for a docs site or a personal page it's hard to beat. It's built for people comfortable with git, and it stops at serving files: no forms, no CMS, no analytics, no backend. Every change is a commit; there's nothing a non-technical owner or a client can use.
Yetty takes the same files and runs them as a living website for $13 per site: click-to-edit content, a lead inbox, SEO, analytics, versioned changes with one-click rollback, and a dashboard a human can use. Your HTML stays exactly as you wrote it. Developers: ship it, hand over the dashboard, keep the repo if you like. And any AI can run it over MCP.
| Yetty | GitHub Pages | |
|---|---|---|
| Owner edits any text, no developer | ||
| Change content without git | ||
| Forms → lead inbox | ||
| SEO handled (titles, sitemap, share cards) | DIY | |
| Analytics the owner can read | ||
| Versioned changes + 1-click rollback | git | |
| Your domain + SSL, set up for you | DIY | |
| Client-ready CMS handoff | ||
| Run the whole site from any AI (MCP) | via git |
GitHub Pages is its owners' trademark. Comparison reflects typical plans.
Which one is for you?
You want your site live and fully managed - no git, no code - or a CMS to hand a client.
You publish once and it's fully looked after - editing, leads, SEO, backups, rollback - from a simple dashboard or your own AI. Hand it to a client and they can run it too.
You're a developer hosting a static or docs site from a repo and happy editing via git.
Then GitHub Pages is the better fit, and that's fine. Yetty is for the finished site that just needs to be live, editable and looked after.