Deploying
Four routes to the same result: a live site, its own SSL certificate, and a place in the daily backup. Pick whichever fits how you already work.
Every route ends at the same place — files on a server, a subdomain live, SSL already attached, a spot reserved in the daily backup. What changes is how the files get there: a repository you already push to, a folder you drag in, one command, or an assistant you ask in plain language.
All four publish through the same queue, so a wave of deploys from one route never slows down anyone using another. Pick based on how you already work — switching later costs nothing.
The chooser
Same account, same guardrails, same queue behind all four — this is the shortcut if you'd rather skip the reading below.
| Route | Best for | What you need | Time to live |
|---|---|---|---|
| Git | Already keeping the site in a repository | A repo, a branch, a folder to point at | The next push |
| Upload | A folder exported from any tool, no repo involved | A zip with index.html at the top | Seconds, once it queues |
| 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 endpoint is also in development — it will underpin the CLI and the MCP server, and eventually let anything else publish the same way.
Four routes in
Pick a card for the full walkthrough — steps, guardrails, and the gotchas that trip people up.
Connect a repository once. Every push to your chosen branch republishes the site, straight from the folder you point at.
No Git, no terminal. Drop a folder or a zip into the browser and it's live before the upload bar finishes.
Run npx lemonade 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 deploys on your behalf — useful, since it may have built the site in the first place.
Questions
No — all four 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 guardrails, and the same queue, so moving from one to another costs nothing and loses nothing.
No, on any route — we publish whatever's already in the folder you point at. Run your own build first, wherever you already do.
A REST API is in development — it will underpin the CLI and the MCP server, and eventually let anything else publish the same way.
See what's included on the static hosting page, or check pricing.