How Static Web works: from git push to your live site

Push your code and we build it and put it live. Every successful build is kept as a release you can roll back to.

Yougit push1Git repoGitHub · GitLab · Bitbucket2WebhookBuildinstall → build → output3Live siteFree URL / your domainBuild logLive on the Builds tab · last 20 keptReleases (latest 5 kept)R1R2R3R4R5Roll back a release4
A successful build becomes a new release and goes live right away. Earlier releases are kept so you can roll back.

Step by step, following the numbers

  1. Push your code to the branch you set.
  2. Your Git provider sends us a webhook, or you can click New build yourself.
  3. We fetch the code, run the install and build commands with the Node.js version you set, then put the files in the output folder live. Longest build time: Free 5 minutes · Starter 10 minutes · Business 15 minutes.
  4. If the new release has a problem, click Use this release on an earlier one (see Webhooks, build logs and rolling back a release).

Static Web or a drag-and-drop website

Website (drag and drop)Static Web
EditingClick to edit in the editorChange the code and push
Going backRoll back a versionUse an earlier release
Business AppsYes (Starter and up)No
QuotaShares the website count and publishesShares the website count and builds
Your own domainPaid plansPaid plans

Static Web only serves files your build makes (HTML, CSS, JavaScript, images). If you need a server that runs code or an API, use Containers.

Still stuck? Let our team help

Open a ticket from the Console. Tell us the site or service, what you did and the message on screen. Our reply comes back in the same ticket, so everything stays in one place.