Skip to content

Preview Deployments

Preview deployments provide automatic, public URLs for every non-default branch. When you deploy from a branch other than the project’s default branch, deploybase creates or updates a preview at a predictable URL.

https://{branch}-{slug}.previews.deploybase.eu

Example: Branch feat/redesign on project my-bloghttps://feat-redesign-my-blog.previews.deploybase.eu

Branch names are sanitized for use as DNS subdomains:

RuleExample
LowercasedFeature/Authfeature-auth
/ and _ replaced with -feat/new_loginfeat-new-login
Non-alphanumeric (except -) removedfix@bug#123fixbug123
Truncated to fit 63-char subdomain limitLong names are shortened to include the slug suffix
  1. A deployment is triggered from a non-default branch
  2. Build runs normally (same process as production builds)
  3. On success, deploybase creates or updates an edge rule on the previews pull zone
  4. The preview_deployments table is upserted: (project_id, branch) → deployment_id
  5. The preview URL is immediately accessible

One active preview per branch per project. A new deployment to the same branch replaces the previous preview.

AspectProductionPreview
TriggerDefault branch deployNon-default branch deploy
URL{slug}.sites.deploybase.eu or custom domain{branch}-{slug}.previews.deploybase.eu
CDNDirect (edge rules on tenant pull zone)Direct (edge rules on previews pull zone)
AccessPublicPublic
PersistenceUntil another deployment is promotedUntil branch is redeployed or preview deleted

Any deployed deployment — including one backing a preview — can be promoted to production instantly. See Rollbacks for the promotion API and details.

  • Preview URLs are always public. For password-protected sharing, use Share Links.
  • Wildcard DNS (*.previews.deploybase.eu) is managed by deploybase — no custom domains on previews.
  • Preview deployments follow the same artifact retention rules as all deployments.