Skip to main content
A static site is built once and served from the CDN. There is no container, so there is no compute allocation and no compute charge. You are metered on bandwidth only.

Prerequisites

A site in a GitHub or GitLab repository whose build writes to a directory.

Add slipway.yaml

slipway.yaml
Getting publish wrong is the most common failure: the deploy goes green and the URL returns 404. The build log reports how many files were uploaded, and the service’s Files view lists what is there.

Point it at an API

A static site’s env applies to the build, so the value is baked into the files:
slipway.yaml
Anything referenced in a static site’s env ends up inside the built files, which are public. Never put a secret there.
Use public_url, not url. A browser cannot reach the in-cluster address.

Redirects and headers

slipway.yaml
slipway also reads _redirects and _headers files in the Netlify and Cloudflare Pages format, so a site moving from either works unchanged. See Redirects and headers.

Upload instead of building

A static site is the one thing slipway serves with no repository. In New → Static site, switch the source to Upload a build and drop a .zip of your output.

Next steps

Static sites

Caching, SPA fallback, atomic deploys and rollback.

Custom domains

Serve under your own zone.