Step 1
Connect
One button. GitHub asks which repositories we may see — pick as few as you like, and change your mind later.
Powerups / GitHub
Connect GitHub once, choose a repository, and every push builds and goes live. No workflow file to write, no deploy key to generate and paste, no secrets to rotate.
Step 1
One button. GitHub asks which repositories we may see — pick as few as you like, and change your mind later.
Step 2
Select it from a list and name your branch. Your build commands go in the same form.
Step 3
That is it. The next commit on that branch builds and publishes itself, and the release appears in your dashboard with its commit message.
What you do not have to do
The usual way to deploy a static site from GitHub is a workflow file, a deploy key or token stored as a repository secret, and a job you now own forever. All of that exists to solve a problem we solved on our side instead.
01
Nothing added to your repository. Your repo stays a repo, not half a deployment system.
02
We ask GitHub for permission through their app flow. Nothing is copied between browser tabs and nothing long-lived is stored on your side.
03
Included, not a paid tier. Access is short-lived and scoped to the repositories you picked, and it is fetched fresh for each build.
04
Disconnect here or uninstall from GitHub. Either ends our access immediately; we do not keep a copy of anything to fall back on.
When something breaks
A push that fails to build does not fail silently in somebody else’s log viewer. The build appears in your dashboard marked failed, with the commit, the exit code and the full output.
Meanwhile the site carries on serving the last release that worked. Publishing only happens once a build has produced something complete.
Or not
Deploy from your laptop with one command, from any CI you already run using a deploy token, or from GitHub. The site cannot tell the difference and neither can your visitors.
Get started
Included on every tier, private repositories and all.