Deployments and rollback - Fluid

Each publish is a deployment. Fluid keeps the files of a site’s 25 newest deployments, so you can make one of them live again at once, with nothing to rebuild.

Deployments, rollback, logs and traffic need the sites gateway, which Fluid turns on for each company. Until then these commands and their API operations answer 404. To turn it on, contact support.

Roll back

fluid sites rollback            # back to the deployment before the current one
fluid sites rollback <id>       # back to a particular one, by its deployment or bundle id

The command asks before it changes the live site. Pass --yes to skip the question, for example in CI. A rollback is refused, and nothing changes, when:

the deployment’s build has a db/schema.json, because restoring a site’s database isn’t available yet;
the deployment is older than the 25 newest, so its files are gone;
a company admin took the site down. A rollback never brings a site back.

List deployments

fluid sites deployments          # newest first
fluid sites deployments --json   # the same list as one JSON object

Each deployment shows when it was published, who published it, how many files it holds and their size, whether it’s the live one, and whether a rollback can still reach it. From Claude with the Fluid MCP server, site_rollback does the same for a company Site. See Deploy from Claude.

Through the API

List a site’s deployments and make an earlier bundle current, for a site you own.
List a company site’s deployments and make an earlier bundle of a company site current, as an admin.