01
Node projects
Astro, Vite, SvelteKit static, Next with static export, Nuxt generate, Eleventy, Docusaurus, VitePress. Node 22 with npm, pnpm and yarn available.
Powerups / Builds
We run the build. You keep the folder.
Point us at a repository, tell us the command, and we produce the site the way your laptop would — then publish it. No build minutes to budget, no queue to sit in, and no separate service to sign up for.
Install commandnpm ci
Build commandnpm run build
Publish folderdist
Three fields. That is the whole configuration.
What runs
Any framework that ends in a folder.
We do not maintain a list of blessed frameworks, because we do not need one. If your build writes files to a directory, we publish that directory.
02
Static generators
Hugo, Jekyll, Zola and anything else you can install in a build step. The container is yours for the duration.
03
No build at all
Leave the commands empty and we publish the repository as it stands. Handy for hand-written HTML kept in git.
04
Or keep building locally
Builds are a powerup, not a requirement. Upload a folder with one command and skip all of this — that path is still the fastest.
How it is isolated
Your build runs nowhere near anyone’s site.
A build executes your code and every dependency it pulls in. That is arbitrary code, and the one place it must never run is a machine serving other people’s websites.
Container
Created for you, destroyed after
Every build gets a fresh container that is thrown away when it finishes. Nothing survives between builds and nothing is shared between customers.
Credential
Reaches one site, works once
The container holds a token that can publish to your site and nothing else, can be used a single time, and expires after thirty minutes. Code inside can read its own environment, so what it holds is deliberately worthless to steal.
Output
Published the ordinary way
A build ends by deploying the folder exactly as your own upload would, so releases, previews and rollback all behave identically however the files were made.
When it fails
A failed build cannot take your site down.
Publishing is atomic: the release that is live stays live until a new one is complete. A build that fails to compile leaves your visitors on the last good version and puts the log in your dashboard.
You get the full output, the exit code and the commit it was building — the same information you would have had locally.
Get started
Connect a repository and watch it build.
Builds are included on every tier, including the free one.