How it works
Four steps, and only the first one repeats less than daily.
Authorize access once and pick the repository. This is the only step you'll do more than once in a blue moon.
Pick the branch to watch — usually main — and the folder that holds your built files: the repo root, or a subfolder like /public or /dist.
A normal git push. Nothing special on your end — no extra remote, no deploy hook to wire up.
Your deploy joins the queue and publishes in order, so a wave of commits never makes anyone's site wait behind someone else's.
What we publish
No build command to get wrong, no dependency that fails to install, no framework version drifting out of sync with your machine — just the files, as they sit in your repo.
# if your build lands in /public, point the deploy there my-site/ ├── public/ │ ├── index.html │ ├── about.html │ └── assets/ │ └── style.css ├── src/ └── package.json # the deploy publishes /public — everything else in the repo is ignored
Bring your own build
Run your build wherever you already do — locally, or in your own CI — and push the result. There's no build-minutes clock running in the background; a deploy is a file copy, not a compile.
Before you push
Watch for these two: if the homepage loads blank, check that index.html sits directly inside the folder you pointed at, not nested a level down inside a subfolder it happens to contain. And paths are case-sensitive — a link to /About.html won't find about.html, even if it worked on your local machine. Match case exactly, everywhere.
Prefer a different route?
Questions
Yes — each push queues a fresh deploy of the folder you pointed at, and it publishes in the order it arrives.
Check that index.html sits directly inside the folder you pointed at, not nested one level down inside a subfolder that folder happens to contain.
Yes — pick any folder in the repository as the one to publish, at the time you connect it.
No — we don't run a build on our side. Push the prebuilt files from your project, whatever folder they end up in.
See what's included on the static hosting page, or check pricing.