How versioning works
Every time a build completes successfully, Myndlab automatically creates a snapshot of the full project — frontend source, backend source, database migration files, and environment variable stubs. Think of it as an automatic commit after every successful generation.
Snapshots are stored for 90 days on the Free plan and indefinitely on Pro and Business plans. Failed builds do not create snapshots — only clean, deployable states are saved.
Opening version history
Reading the build log timeline
Each snapshot entry in the timeline can be expanded to reveal the build log for that run. The log is split into three phases:
Timestamps, token usage, and any warnings emitted during generation are all visible inside the expanded log view.
Comparing two versions
To diff any two snapshots, click the checkbox to the left of the first snapshot, then hold Shift and click the second. A Compare button appears at the top of the panel.
The diff view shows a side-by-side (or unified) view of every file that changed:
Files that did not change between the two snapshots are hidden by default. Toggle the "Show unchanged files" switch to see the full file tree.
Restoring a previous version
Click any snapshot in the timeline and select Restore this version. Myndlab will start a new build using the selected snapshot as its base — it does not overwrite or delete the current state.
The restored build goes through the normal deploy phase. Once complete, your live preview URL will reflect the restored version.
Version history and GitHub
If your project is connected to a GitHub repository, every snapshot maps 1-to-1 with a commit pushed to your repo. The commit message includes the Myndlab build number and the timestamp, so you can correlate version history entries with your Git log at a glance.
Restoring a previous version also creates a corresponding commit on the connected branch — the repo always stays in sync with Myndlab's snapshot state. To connect GitHub, see the GitHub sync guide.