GitHub Pages password protect - for real client previews
GitHub Pages has no built-in password, and its access control needs Enterprise Cloud and gates to your org's members via SSO - internal, not an external client link. Drop the same build on Hostsmith and add a shared password or email whitelist on Pro.
Hosted in the EU on request - EU data partitions available on Pro.
The public link is free. You'll sign in free to publish it - no card needed.
GitHub Pages is a great deal: free hosting, free HTTPS, free custom domains, and a workflow that fits right into how developers already work. For open-source projects and documentation it is hard to argue with. The trouble starts when the thing you are publishing is a confidential client preview rather than a public project.
Where GitHub Pages actually stands
- No native password. There is no built-in "protect this site with a password" option.
- Private Pages exist, but only on GitHub Enterprise Cloud, and they gate access to members of your organization through SSO. That is internal access control, not a password link you hand to an outside client.
- Free-tier repos are public. On the free tier the repository behind your Pages site is public, so your source files are public too - an odd fit for client work under NDA.
So the accurate gap is scope plus plan: access control is enterprise-tier and member-scoped, not an external client password. It is not that gating is impossible.
How Hostsmith handles the same job
- Build your site locally (the same output you would push to Pages).
- Drop the output folder or a ZIP onto Hostsmith for a free public link - no repo required.
- On the Pro plan, turn on Private Sites and pick a shared password or an email whitelist.
Your source stays yours, the audience is whoever you choose, and the gate is a toggle rather than an enterprise plan. Password protection, custom domains and EU partitions are Pro features; the free tier is a public link only. For the broader hosting trade-offs, see our GitHub Pages alternatives guide.
| Capability | GitHub Pages | Hostsmith |
|---|---|---|
| Native shared-password gate | No built-in password feature | Built in on Pro - one toggle |
| Access control | Private Pages on Enterprise Cloud, gated to org members via SSO | Shared password or email whitelist (Pro) |
| Audience | Internal org members | Any external client you choose |
| Deploy method | Git push (public repo on the free tier) | Drag and drop a file or ZIP |
| EU data partition | GitHub-hosted; no EU-only data choice | EU partition on Pro |
| Free public link | Yes, with free HTTPS and custom domain | Yes - free tier, public link |
Frequently asked questions
Can you password protect a GitHub Pages site?
Not natively - GitHub Pages has no built-in password feature. The closest thing is private GitHub Pages, which requires GitHub Enterprise Cloud and limits access to members of your organization through SSO. That is access control for internal people, not a shared password link you can send to an outside client. It's a scope and plan gap, not 'you can't gate it at all'.
GitHub Pages is free and great - why move?
For open-source and docs, GitHub Pages is excellent: free HTTPS, free custom domains, generous limits. The mismatch is narrow - a confidential client preview on the free tier means a public repo (your source is public too), and the only gate is Enterprise + org membership. For that one job, a drop-and-gate host is simpler.
How do I gate the same build on Hostsmith?
Run your build, then drop the output folder or a ZIP onto Hostsmith for a free public link. On the Pro plan, turn on Private Sites and choose a shared password or an email whitelist. Gating is the paid part; the public link is free.
Send a private preview, not a public repo
Drop your build for a free link, then add a password or email whitelist on Pro.
Free public links. Password protection, custom domains and EU data partitions are on Pro.