In development
That's what the deploy API will do: hand it your files from anything you already run - a CMS, a build server, a script, a product of your own - and it publishes them. It's being built now, and this page is the honest state of it. It will be announced in the changelog the day it opens.
What it will do
Publish a client's site the moment your own system says it's ready, roll out fifty landing pages from a spreadsheet, or put a preview online from a build server - the same action the CLI and the MCP server already perform, offered as a plain HTTP call anything can make. No client to install, no dashboard in the loop.
Why it comes first
The deploy queue, the file guardrails, and the validation that keeps a bad upload from becoming a bad deploy all need to exist exactly once. Building them as an API means the CLI and the MCP server both call the same primitive instead of each reimplementing it, and anything built after them inherits it for free rather than needing its own copy of the same logic.
That's also why it isn't rushed. A REST endpoint is a public contract - once other systems are calling it, changing its shape gets expensive. The CLI and MCP server can absorb rough edges internally while it's still being worked out; a published API can't.
The plan for it
The same principle already governs the MCP server's tokens, and it carries over here rather than getting reconsidered from scratch.
A token authenticates to the API and can create, update and check the status of sites - the same actions available today, nothing wider.
No token, however it's scoped, will be able to see or change billing details. That boundary sits outside what any deploy credential can reach.
Removing a single site is in scope. Deleting the account underneath it is not - that stays a human action in the dashboard.
On the roadmap
Will sit underneath the CLI and the MCP server, which both publish today without it. Watch the changelog for the day it opens.
Room for data behind a site, for the ones that outgrow what a page can hold. Planned as a paid add-on once the publishing routes underneath are solid.
Meanwhile
None of these are waiting on the API - they're the real way sites go live, and they'll keep working exactly the same once it ships underneath them.
Start from a template, change the words in your browser, press publish.
Connect a repository once. Every push after that puts the new version live.
Just the files, dropped straight into the browser.
npx lemonade-host deploy, from wherever your files already are.
Connect the server once; your AI assistant deploys from the conversation.
Questions
Five routes: edit a design in your browser, drag a folder in, push from Git, run one command, or ask an AI assistant through the MCP server. None of them is waiting on the API.
Sites stay 99¢ a month each. Whether the API itself carries a price isn't decided yet - when it is, we'll say so plainly here and on the pricing page.
There's no date to promise yet. It will be announced in the changelog the day it opens, with its documentation.
While the API is being finished, every other route works today. See what every site includes, or check pricing - 99¢ a month per site.