Saving and restoring versions
A version is a saved snapshot of your project that you can return to later. Save one before a risky change, and roll back to it if something goes wrong.
What a version captures
Section titled “What a version captures”A version is a full snapshot of your project’s files — your code and the built app — together with a dump of its database. Restoring a version brings both back. Versions are stored safely off the project’s own server, so they survive even if the project itself is deleted.
Save a version
Section titled “Save a version”On a live project card, open Versions and save the current state. Give the version a name, and an optional description. Saving happens in the background with no downtime.
How many versions you can keep depends on your plan — the Versions control shows how many you’ve used out of your allowance. When you reach the limit, saving prompts you to upgrade or to delete an existing version first.
Restore a version
Section titled “Restore a version”Open Versions, pick the one you want, and select Restore. Your project’s files are rolled back to the snapshot and the app restarts — this takes about a minute, and the project is briefly unavailable while it happens. Restoring does not use AI credits.
Restoring replaces your project’s current state, so anything you haven’t saved as a version is lost — save the current state first if you want to keep it. Restoring needs a running container, so wake a sleeping project before you restore.
Automatic restore points
Section titled “Automatic restore points”livemy.app also keeps a few versions for you automatically — for example, a restore point taken right before each redeploy — so you can roll back even when you didn’t save one yourself. These don’t count against your version limit.
Related
Section titled “Related”- Your projects — where the Versions control lives.
- Pausing and resuming projects — wake a project before restoring.