staticweb.site
Your workspace

Frontend
publishing.

Publish a frontend from Git, a folder or a ZIP. Keep build configuration, domains, delivery and release history together.

Release examplePublished
↳
web / reactmain a83f02c
Build command
npm run build
Output directory
dist/
index.html
assets/app.js
assets/main.css

Your build.
Your settings.

Use the tools already in your repository. Choose what to run and which folder to publish. StaticWeb serves the result.

Next.js needs a static export. Server-rendered pages and API routes run on a separate backend.

Read the framework guide
Project configuration
websitemain
Framework presetReact
Build commandnpm run build
Publish directorydist/
sws deploy --prod

Already built? Publish files directly from your terminal.

A release
you can trace.

A new build doesn’t replace your working site until it is ready. See the commit behind a deployment and keep a route back to an eligible release.

Explore releases
Release history example
Latest releaseThe current site keeps serving.

If the next build fails, this deployment remains the live version.

Keep your domain.

Add the DNS records provided in your workspace and follow verification. Your project has a live address while you prepare a custom domain. HTTPS is configured after the domain points correctly.

Domain setup

Keep your backend.

Your browser can call an existing HTTPS API. StaticWeb serves generated frontend files; it does not execute server-side rendering, database queries or API routes inside that deployment.

Supported frameworks

Know what runs here.

Generated HTML, CSS, JavaScript, images and fonts. React, Vue, Astro, Vite and Next.js static exports work. Server rendering, databases and API routes need a separate runtime.

Read the documentation