Git deploy
Connect a repository once. After that, every push to the branch you chose puts the new version live — no dashboard to visit, nothing else to remember, 99¢ a month for the site it lands on.
$ git push origin main → change detected → 42 files queued ✓ live in 4s
How it works
Four steps to set up, and after that only the push repeats.
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
You choose the folder; we publish exactly what's in it. The version you looked at on your own machine is the version your visitors get — same files, same result, every push.
# 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
Your toolchain, unchanged
Run your build where you always have — on your laptop, or in your own CI — and push the result. Publishing is a copy, not a compile, so it starts the second your push lands and there are no minutes to buy while you wait.
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?
Start from a template, change the words in your browser, press publish.
Just the files, dropped straight into the browser.
npx lemonade-host deploy, from wherever your files already are.
Connect the MCP server and ask it to deploy, in plain language.
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.
Yes. Run your generator the way you already do — Hugo, Eleventy, Astro, your own script — and point the deploy at the folder it writes to.
See what every site includes, or check pricing — 99¢ a month per site, cancel any time.