Static sites

A static site serves files straight from object storage. There is no container, so nothing to size, nothing to keep warm, and no cold start. You are billed on the data stored and served, not on CPU or memory.

Use it for marketing sites, documentation, single-page apps, and the built output of tools like Vite, Next.js (static export), Astro, or Hugo.

Creating a site

1. Click + Add and choose Static Site.
2. Enter a name.
3. Click Apply in the Apply Changes bar.

The site gets a Site URL immediately. Until you publish files, it has nothing to serve and shows as not being served.

Publishing files

Open the service panel and upload your built files — the contents of your dist, build, out, or public directory. Upload the contents of that directory, not the directory itself, so index.html sits at the root of the site.

Publishing replaces what is there. The file count and last published time in the panel tell you what is currently live.

Files can also be published through the CLI or through an AI agent — the site accepts file contents directly, so you do not need Docker to deploy one.

Index and error documents

Two settings control how paths are resolved:

For a single-page app that does its own routing, set the error document to index.html too. Any unknown path then loads your app, which reads the URL and renders the right view.

Custom domain

1. Open the service panel → Custom domain.
2. Enter your domain, for example www.example.com.
3. Copy the CNAME target shown under Point your DNS here.
4. Create that CNAME record at your DNS provider.

Once the record is visible, the domain goes live and HTTPS is set up automatically. You do not upload a certificate, and renewals are handled for you.

To remove the domain, click Delete Domain, then delete the CNAME record at your provider.

Deleting a site

Open the service panel → Delete Site, then apply the change. All published files are deleted with it.