Compute

Static Sites

Deploy static sites and JAMstack apps. Push your code, get a fast site with SSL and your own domain.

Supported Technologies

Next.jsGatsbyHugoViteAstroNuxtSvelteKitRemix11tyJekyll

~20 seconds

Build Time

10+ regions

CDN Locations

100 GB/mo

Bandwidth

Automatic

SSL

Unlimited

Deploys

Per PR

Preview URLs

Features

Everything You Need

Built-in tools and capabilities to deploy and manage with confidence.

Instant Builds

Optimized build pipeline with Docker layer caching reduces build times by up to 40%. Incremental builds for supported frameworks.

Global CDN

Assets served from edge locations worldwide for sub-100ms load times. Automatic cache invalidation on every deploy.

Preview Deploys

Every pull request gets a unique preview URL. Share with your team for visual review before merging to production.

Custom Domains & SSL

Map your own domain with automatic SSL certificate provisioning and renewal via Let's Encrypt. Supports apex and wildcard domains.

Build Configuration

Specify publish directory, build commands, and environment variables. Framework auto-detection handles the defaults.

Headers & Redirects

Configure custom response headers, URL redirects, and rewrite rules for SEO, security, and single-page app routing.

CDN Pipeline

Build, cache, deliver globally

Static sites are built once and served from edge locations worldwide for blazing-fast load times.

1

Build Triggered on Push

RunSite detects your framework, installs dependencies, and runs your build command. Docker layer caching reduces repeat build times by up to 40%.

2

Assets Optimized & Hashed

Output files are fingerprinted with content hashes for infinite caching. HTML files get short cache TTLs so visitors always see fresh content.

3

Distributed to Edge Locations

Built assets are pushed to 10+ edge locations worldwide. Every deploy triggers automatic cache invalidation across all nodes.

4

Served with SSL & Custom Headers

Requests are routed to the nearest edge location. Custom response headers, redirects, and rewrite rules are applied at the edge layer.

Code

Get Started in Minutes

Simple integration with your existing tools and workflows.

// next.config.js
module.exports = {
  output: 'export',
  images: { unoptimized: true },
}
Use Cases

Built for Your Workload

Common scenarios where this service shines.

Marketing Sites

Launch landing pages and marketing websites with blazing-fast load times and zero server management.

Documentation

Deploy Docusaurus, VitePress, or GitBook documentation with auto-deploy on every content update.

Portfolio & Blog

Deploy Gatsby, Astro, or Hugo blogs and portfolios with custom domains and global CDN distribution.

E-commerce Storefronts

Build headless e-commerce frontends with frameworks like Next.js connected to any CMS or backend API.

Pricing

Simple, transparent pricing

Pay only for the resources you actually use. Switch between monthly and hourly to see what you'll spend.

JAMstack & static frontends

Landing pages · Docs · Portfolios

Deploy Next.js, Astro, Vite, Hugo and friends to a global CDN. Auto-deploy from Git, preview on every PR, free SSL.

Static Sites

Free

Popular
Free

No cold starts on active apps · no card

CDN
Global
Bandwidth
100 GB
Builds
~20s
Sites
Unlimited
Start free
Free during public beta. Pay-as-you-go bandwidth above the included quota will be introduced after launch — we'll notify you before any change.
FAQ

Frequently Asked Questions

Common questions about this service.

RunSite supports all major static site generators and frameworks: Next.js (static export), Gatsby, Hugo, Vite, Astro, Nuxt, SvelteKit, Remix, 11ty, Jekyll, and any tool that outputs static HTML/CSS/JS to a publish directory.

Static sites are pre-built at deploy time and served as static files via CDN, resulting in faster load times and lower cost. Web services run a server process (Node.js, Python, etc.) and handle dynamic requests. Choose static for content-focused sites and web services for dynamic applications.

Static sites on RunSite serve pre-built files only. If you need server-side rendering (SSR), deploy as a Web Service instead. Frameworks like Next.js support both — use static export for static, or deploy as a web service for SSR.

When you deploy, RunSite distributes your built assets to edge locations worldwide. Cache is automatically invalidated on every new deploy, so visitors always see the latest version. Assets with content hashes are cached indefinitely for optimal performance.

Your app deserves to be online

Free to start. Deploy in under a minute. No credit card needed.