GetLaunchGetLaunch
Try it free

Static Site Deployments

Deploy static websites with automatic builds, global CDN, and instant cache invalidation.

Supported Frameworks

getlaunch.dev supports various frameworks that generate static files, including:

  • Next.js (static export)
  • React (Create React App, Vite)
  • Vue.js
  • Hugo
  • Jekyll
  • Gatsby
  • Plain HTML/CSS/JS

Build Configuration

When creating a static site project, getlaunch.dev automatically detects your framework and sets the Build Command and Output Directory for you.

You can override these values by clicking the Edit (pencil icon) button in the build configuration section — both during project creation and in your project settings.

  • Build Command: The command to build your site (example: npm run build)
  • Output Directory: The directory where static files are generated (example: dist, build, out)

Example: Next.js Static Export

// next.config.js
const nextConfig = {
  output: 'export',
}
module.exports = nextConfig

// Configure in getlaunch.dev:
// Build Command: npm run build
// Output Directory: out

Example: React (Vite)

// Configure in getlaunch.dev:
// Build Command: npm run build
// Output Directory: dist

Example: Hugo

// Configure in getlaunch.dev:
// Build Command: hugo
// Output Directory: public

Environment Variables

You can use environment variables during the build process by setting them in your project settings. They will be injected during the build phase.

# .env.local (build-time)
NEXT_PUBLIC_API_URL=https://api.example.com
ANALYTICS_ID=abc123

Global CDN

Static sites are served through CDN edge locations around the world. Content is cached and delivered from the location nearest your users to ensure fast load times across all regions.

  • Automatic cache invalidation on every deploy
  • Global edge caching for instant delivery

Custom Domains

Each static site gets a default URL:

project-name-xxxx.gtlnch.app

You can configure custom domains in your project settings (available in Starter plan and above). Custom domains come with automatic SSL/TLS certificates and are served through our global CDN.

Limits & Quotas

Static site quotas depend on your subscription tier and may change as plans evolve. Check Pricing or your dashboard quota summary for the current static site, storage, file, and build limits.

Cache is automatically invalidated on every deploy. If you still see old content in your browser, try a hard refresh with Ctrl+Shift+R (Windows/Linux) or Cmd+Shift+R (Mac).

Best Practices

  • Optimize images using compressed formats and sizes.
  • Use code splitting and minification to reduce bundle size.
  • Add cache headers with long TTLs for static assets.
  • For SPA routing, ensure your router is configured to handle all routes and fallback to index.html.

Troubleshooting

  • Build failed: Check the build log for errors in your build command.
  • Files not found: Ensure the output directory is correct and matches your configuration.
  • SPA routes not working: Ensure the build generates a fallback index.html for all routes.
  • Cache not updated: Cache is automatically invalidated on each deploy. If you still see old content in your browser, try a hard refresh.