How it works covers the whole flow. These are the questions that come up beyond it.
Access and security
Does anyone else see my GitHub token?
No. It is encrypted and stored server-side, and is never sent to a browser or shown in the interface. People you invite use the tool; they never hold your credentials.
What kind of token do I need?
A classic GitHub personal access token, scoped to the repositories you intend to manage.
Can I take access away again?
Yes, at any time and per repository. Removing a grant takes effect immediately.
Do private repositories work?
Yes — on any GitHub plan, including the free one. Private repositories are free and unlimited on GitHub, and everything this service does works with them exactly as it does with public ones: browsing, editing, committing, granting a colleague access to one and nothing else.
Can I publish a private repository as a website?
That depends on where you host it, not on us.
GitHub Pages only builds from a private repository on a paid plan — Pro for a personal account, Team for an organisation. On the free plan, GitHub Pages requires the repository to be public.
If you are on the free plan, you have not hit a wall. Several hosts build a site straight from a private repository on their free tiers:
- Azure Static Web Apps — free tier, connects to a private repository and deploys through a GitHub Action
- Cloudflare Pages — free tier, same arrangement
- Netlify and Vercel — both build from private repositories on their free plans
The setup is the same either way: your repository stays private, a GitHub Action builds it on each commit, and the finished site is served publicly. Nothing about how you work here changes.
Upgrading to GitHub Pro is worth it if you specifically want Pages, but it is a convenience rather than a requirement.
What it can handle
Which kinds of site?
Static ones — React, Next.js, plain HTML — deploying through a GitHub Action to GitHub Pages, Azure Static Web Apps or anywhere similar. Applications with a database are out of scope.
Does it deploy my site?
Not directly. It commits to your repository, and the GitHub Action you already have does the deploying. Nothing new to configure.
Can I use my own domain for the site I get here?
Not at the moment. The optional site you get on signup stays on its subdomain. The sites in your repositories, of course, use whatever domain you have already set up.
Cost
Is it free?
Yes, while it is in beta. A paid plan may follow, and you will be told in advance if that affects you.
Still stuck?
Get in touch and describe what you were trying to do.