Docs / Compute

Static Sites

Static sites build your frontend (React, Vue, Next.js static export, Hugo, etc.) and serve the output over HTTPS from nginx inside a container. They get the same default URLs and custom domain support as web services.

Create a static site

  1. Click + New → Static Site in the dashboard.
  2. Connect a Git repository or upload source.
  3. Set the build command (e.g. npm install && npm run build) and publish directory (e.g. dist or out).
  4. Deploy. The platform serves files from the publish directory after a successful build.

Publish directory

Point the publish directory at the folder your build produces — not the repo root unless that is where assets land. Configure it under Service settings → Build.

Routing and SPA fallback

nginx serves static files. For single-page apps, ensure your build includes an index.html and configure client-side routing as usual — the platform does not rewrite all paths to index.html automatically in v1; use framework-specific static export settings.

Deploys

Static sites use the same deploy pipeline as web services: auto-deploy on push, deploy hooks, rollbacks, and preview environments. See How deploys work.