Framework build settings

What you can deploy

Deploy the HTML, CSS, JavaScript, and assets produced by your build. Browser-based features work normally, including live data and sign-in through external services.

Server-side services need separate hosting. StaticWeb does not run server-side rendering (SSR), API routes, Server Actions, WebSocket servers, or persistent server processes.

Connect your frontend to an API

Use your API’s public HTTPS URL in the frontend. If your API is on a different origin, allow your deployed project address and custom domain in its CORS settings. For cookie-based login, also configure your API’s allowed origins and cookie settings for your chosen domains.

Keep private API keys, database credentials, and server secrets on your backend. Frontend bundles and any configuration included in them are visible to visitors. Your backend must authenticate requests and enforce permissions; hiding a page or a button is not access control.

Test sign-in, data loading, form submissions, and page refreshes on the deployed address. Client-side routing is supported for single-page apps. For Next.js, any exported route must still exist in the generated build; fetching fresh data in the browser does not require SSR.

React or Vue with Vite

Build command: npm ci && npm run build. Output directory: dist. Commit the package lockfile so npm ci can reproduce your dependencies.

npm ci
npm run build
sws init YOUR_PROJECT_ID dist
sws deploy

Next.js

Configure output: 'export' in next.config.js or next.config.ts, then build. Output directory: out. Use unoptimized images or a supported external image loader. Dynamic routes must be generated at build time. Server-only features need a separate backend.

// next.config.ts
export default { output: 'export', images: { unoptimized: true } };

Nuxt

Run npm ci && npx nuxt generate. Use .output/public as your output directory. Pages must be prerenderable; server endpoints are not deployed.

Angular, Astro, and SvelteKit

Angular: run npm ci && npm run build. Use the directory containing the generated index.html, commonly dist/your-project/browser.

Astro: use static output and npm ci && npm run build; output is normally dist.

SvelteKit: configure adapter-static and prerender the required routes. The output directory is usually build. Check your adapter configuration before deploying.