How to roll back a site to a previous version

A rollback is done in the panel: site page → Deploys tab → the Roll back to this button on the version you want. It goes live instantly: the files are already in storage, nothing is rebuilt. The same is available to an AI agent over MCP (activate_deploy) and from the terminal (npx @tuqo/cli promote). The only limit is how many past versions your plan keeps.

Rolling back in the panel

The tab lists every kept version with its date and size. The active version has no rollback button, since it’s already on the live address. Past deploys have Roll back to this; versions that were built but never published have Publish.

Not sure which version you need? On the Start plan and above, every kept version except the published one can get a secret preview link: open it, look at the site, and only then roll back, instead of choosing blindly by date. The link opens without a password even on a gated site, so give it only to people you trust. More on the build preview page.

Next to it is a Delete button: a version that will never be published takes up storage quota and holds a kept-version slot. You can’t delete the active version, as the site would be left without files. The deploy entry doesn’t disappear either: it moves to the Deploy history tab.

How many versions are kept

Rollback depth is a plan limit:

Plan	Kept versions
Free	1
Start	3
Pro	5
Business	8
Scale	15
Enterprise	30

On the Free plan only the active version is kept, so there’s nothing to roll back to: you have to publish again. That alone is why the Start plan at 590 ₽/month pays for itself on the first bad deploy. Full comparison and approximate dollar and euro prices: pricing.

Versions count toward your plan’s storage: three copies of a photo-heavy site take three times the space. If you hit the quota, reduce the number of kept versions or buy a storage pack.

Retention settings

The site’s Settings tab has a Kept deploy versions block with two fields:

• Copies to keep: how many past versions to keep for rollbacks;
• Delete older than (days, 0 = off): an extra age limit for copies.

A value above your plan’s ceiling is lowered automatically, and the panel tells you so. Anything outside the retention window is cleaned up: the files are removed from storage, while the deploy entry stays in the history. You can no longer roll back to such a version; the attempt returns an error, and you need to publish again.

Rolling back over MCP

One tool is all an agent needs:

Show the site's deploys and put the previous version back on the live address

The model calls list_deploys, then activate_deploy(deploy_id): it makes the given deploy live and returns the updated site with the new active deploy. For cleaned-up versions the tool refuses plainly: the files are gone, so deploy again. How to connect an agent: the Connect an AI page.

Rolling back from the CLI

In the terminal and in CI, a rollback is the same command as publishing a deferred build:

TUQO_API_KEY=tqk_… npx @tuqo/cli promote <deploy_id>

promote prints the live address. Take the version ID from the panel or from the output of an earlier deploy: deploy prints the deploy_id as the first line. A useful pattern when working with a client: build a version with --no-activate, show it via a preview link, and publish it with promote once approved. Details on the CLI page.

FAQ

Is a rollback a rebuild?

No. The files of the earlier version are in storage; a rollback just switches the live address to them. It takes seconds and uses no build minutes.

What happens to the domain and site settings?

Nothing: domains, forms, gated access and analytics belong to the site, not to a specific deploy. Only the set of files being served changes.

I rolled back, but I needed the opposite

The newer version stays in the list: roll forward the same way, as long as the retention limit hasn’t pushed it out.

No version has a Roll back to this button

Then only one version is kept, which is how the Free plan works. Upgrade your plan or raise Copies to keep in the site settings: new deploys will start being kept, but copies already removed can’t be restored retroactively.

Plans and kept versions → · CLI docs → · Why a deploy failed →