Deploying
Edit a design in your browser and press publish, drag a folder in, push from Git, run one command, or ask your assistant. Every route ends the same way: your site live at your own address, the padlock already there, 99¢ a month.
Every route ends at the same place: your site live at its own address, the padlock already there, and yesterday's version kept safe in case you want it back. What changes is only how the pages get in — a design you edit in the browser, a folder you drag in, a repository you already push to, one command, or an assistant you ask in plain language.
All five publish through the same queue, so a busy afternoon on one route never slows anyone down on another. Pick the one that suits how you work — switching later costs nothing, and it's the same 99¢ a month whichever you use.
The chooser
Same account, same price, same queue behind all five — this is the shortcut if you'd rather skip the reading below.
| Route | Best for | What you need | Time to live |
|---|---|---|---|
| Editor | Getting a real site up without it becoming a project | A design you like and your own words | An afternoon at most |
| Upload | A folder that came out of any other tool | A zip with index.html at the top | Seconds, once it queues |
| Git | Already keeping the site in a repository | A repo, a branch, a folder to point at | The next push |
| CLI | Scripts, CI pipelines, terminal habits | npx, and a token | When the command finishes |
| Assistant | A site built inside a chat window | The MCP server added once, a scoped token | As soon as it calls the tool |
A REST deploy endpoint is on the way too — one HTTP call, so anything you build can publish the same way.
Five routes in
Pick a card for the full walkthrough — the steps, and the gotchas that trip people up.
Start from a template, edit it in your browser — the words, the pictures, the colors — and press publish. This is how most people here get online.
Already have a site somewhere else? Drop the folder or the zip into the browser and it's live before the upload bar finishes.
Connect a repository once. Every push to your chosen branch puts the new version live, straight from the folder you point at.
Run npx lemonade-host deploy from your project folder. Nothing to install, and it prints the live URL when it's done.
Connect the MCP server once and your assistant publishes on your behalf — handy, since it may have built the site in the first place.
Questions
No. Pick a design, change the words and the pictures in your browser, and press publish. The other four routes are there for people who'd rather use them.
No — all five publish to the same 99¢-a-month account. There's no per-route fee, and nothing about which one you use changes the bill.
Yes. Every route lands in the same account, the same site and the same queue, so moving from one to another costs nothing and loses nothing.
A REST deploy endpoint is on the way — one HTTP call, so anything you build can publish the same way. Join the list and we'll email you the day it opens.
See what every site includes, or check pricing — 99¢ a month per site, cancel any time.