Previews and instant rollback

Push a branch and it gets its own address to review. Production points at one finished deployment, so putting a preview live or going back to last month takes seconds, with no rebuild.

Pushing the redesign branch of a real project built a preview in 45 seconds at its own address, kept out of search engines, ready to promote to production.

Every branch, its own address.

Each branch you push builds on its own and answers at its own URL. Send it to a client, check it on your phone, then merge. Your production site does not move.

Preview branches of the project
BranchPreview addressLast build
redesignredesign-blog.previews.deploybase.eu22 Jul · 45 s
draft-postdraft-post-blog.previews.deploybase.eu6 Apr · 35 s

Slashes become hyphens and capitals become lowercase, so any branch name makes a valid address.

Kept out of search

Every preview answers with a header that tells search engines not to index it, so drafts never compete with your real pages.

x-robots-tag: noindex, nofollow

You choose which branches

Preview every branch, none, or a list. The default branch always builds, because it is your production site.

include  *
exclude  renovate/*

Roll back to any deployment, even March's.

Every build is kept exactly as it was, and production is a pointer to one of them. Here is every production deployment of one real blog. Any row can be live again in seconds.

  1. 3ea7b2c 4 Aug built in 40 s Live
  2. 645e615 22 Jul built in 40 s Roll back to this
  3. d15f140 21 Jun built in 85 s Roll back to this
  4. f3c4c5c 13 Apr built in 35 s Roll back to this
  5. 9818262 9 Apr built in 40 s Roll back to this
  6. 661b4f3 2 Apr built in 30 s Roll back to this
  7. fb574ed 30 Mar built in 30 s Roll back to this

Everything moves together

Promote a deployment and your custom domains follow it, and so do its functions. There is no half-rolled-back state.

If it cannot switch, nothing changes

Production moves only once the new route is written. If that fails, you are told so and the previous deployment keeps serving.

Production routing could not be updated. Nothing changed; the previous deployment is still live.

Share a draft, with a password.

For a client who should see a deployment and nothing else: a share link to exactly that build, with an optional password and an end date. Revoke it and it stops working.

Share link one deployment, nothing else
Address app.deploybase.eu/draft/{a 64-character token}
Password optional, stored only as a bcrypt hash
Expires after 24 hours, 7 days or 30 days
Search noindex, nofollow never indexed
Revoke Revoke link

Passwords on every plan

Free has three active share links at a time, paid plans have no limit. A password is never a paid extra.

Built for agents too

An agent with an API key can create and revoke share links through our MCP server, so the agent that made a change can hand you the link to review it.

create_share_link
revoke_share_link

What previews do not do yet.

  • A preview link on your pull request We do not comment on pull requests or post the address back to your Git host yet. Copy it from the dashboard.
  • A password on the preview itself Preview addresses are public but unindexed. Use a share link when a draft must stay private.
  • Clean-up when a branch is deleted Deleting a branch or closing a pull request leaves its preview up. Delete it from the dashboard.
  • Approval before production A push to the default branch goes live when it builds. There is no approval step or switch to turn that off yet.

Questions about previews and rollback.

Something else? Write to support@deploybase.eu. A person answers.

What address does a preview get?

The branch name, cleaned up, then your project's preview name: a branch called feature/new-pricing on a project called my-site answers at feature-new-pricing-my-site.previews.deploybase.eu. You can rename the preview part in settings.

How previews work
Does a rollback rebuild my site?

No. Every deployment is kept as it was built, and production is a pointer to one of them. Rolling back moves the pointer, so the older deployment serves again within seconds, with its own functions and on your custom domains.

How far back can I roll back?

To any deployment that built successfully. We do not delete old deployments, so the project above can still go back to its first build in March.

How many previews can I have?

Three active preview branches and three share links on Free. Every paid plan has no limit on either. Redeploying a branch that already has a preview never counts against the cap.

Plan limits
Can I password-protect a preview?

Not the preview address itself. Create a share link for the deployment instead: it can carry a password and an expiry, and you can revoke it at any time.

Do previews expire?

Not today. A preview stays until you redeploy the branch or delete the preview. Automatic clean-up after a period without pushes is planned.

Push a branch, send the link.

Create a team on the free plan, connect a repository, and every branch gets its own address.