Static Sites
Static Sites host pre-built front-ends — HTML, CSS, JavaScript and assets — straight from a Git repository. No runtime, no container, no scaling to think about.
Each site gets a free *.runsite.site subdomain and can serve any custom domain you attach.
Pricing & plans
Comparing options or looking for the free tier? See plans, specs and pricing on the Static site hosting page.
What it’s for
Section titled “What it’s for”Marketing pages, documentation, single-page apps (SPAs) and JAMstack sites built with Astro, Vite, Next.js, Nuxt, SvelteKit, Hugo, Jekyll or plain HTML.
Static Sites vs Web Services
Section titled “Static Sites vs Web Services”| Web Services | Static Sites | |
|---|---|---|
| Runtime | Long-running container | None — files only |
| Pricing model | Pay for CPU/RAM time | Pay per deploy storage |
| Suited for | APIs, full-stack apps, workers | Front-ends, SPAs, docs |
| Sleep on idle | Yes | Not applicable |
Framework presets
Section titled “Framework presets”Pick the matching pair when you create the site — or let Runsite auto-detect.
| Framework | Build command | Publish directory |
|---|---|---|
| Astro | npm run build | dist |
| Vite | npm run build | dist |
| Next.js (static export) | npm run build | out |
| Nuxt 3 (static) | npm run generate | .output/public |
| SvelteKit (adapter-static) | npm run build | build |
| Hugo | hugo | public |
| Jekyll | bundle exec jekyll build | _site |
Where to next
Section titled “Where to next”- Deploying — auto-deploy from Git, build configuration, limits.
- Dashboard — what each tab does for a static site.
- Domains — default subdomain and custom domains.
Need a backend with your static site?
Static Sites are pure front-end. If you need APIs, dynamic rendering or background work, deploy them as a Web Service and call it from your static site over HTTPS.