Publishing and rollback

Say "publish it" to your AI, or press Publish in the portal.

Publishing needs a paid plan. It puts your site live at https://<name>.lazyfrog.app, and on your own domain if you connect one. On Free your AI builds and shows you the preview, which anyone with its link can open while it's awake; when you want a live site, choose a paid plan, and everything you built comes with you.

What happensCopy Anchor Link

1. Your AI's work is committed and tagged in git.
2. A copy is built and started exactly as the live site will run, and its health is checked.
3. Database changes (migrations) are tried on a copy of the live database first.
4. Only then is the live database migrated, after a snapshot, and traffic switched to the new version. The old one finishes the requests it was serving.

Visitors see no downtime. If any step fails, nothing changes on the live site and the reason is shown.

Rolling backCopy Anchor Link

Deployments in the portal lists every publish. Roll back puts the previous version live in seconds. The database stays as it is unless you ask to restore it to just before that publish's changes.

Before the first publishCopy Anchor Link

Your AI handles this, but if a publish is refused, it's usually one of these:

• The app needs a start command for the live site and a health check page (a /health route).
• Every secret set for the preview also needs a live value.
• A database change would remove data, so publishing it needs your confirmation.

Free sites that were live beforeCopy Anchor Link

Free used to include a live site. A Free site that was live before 29 October 2026 keeps running for 30 days after we email its owner. Then visitors see "This site is paused. Its owner can bring it back by upgrading." Nothing is deleted, and the site comes back within a few minutes of choosing a paid plan.