Skip to content

Dashboard

A static site shares the same dashboard layout as a web service. The tabs that matter for a static site:

Live deployment history, current status, and the basics: type, build command, publish directory.

From here you can Trigger Deploy, Cancel an in-flight build, or Rollback to any previous successful deploy.

Build logs from your most recent deploys.

  • Live tail — watch the build as it runs.
  • Time windows — view logs for the last 1h, 4h, 24h, 2 days, 7 days, 14 days or 30 days.
  • Pause / Resume the live stream while you read something.
  • Download the current view as a file.

Static sites don’t have a runtime, so there are no request logs — only build logs.

Build-time environment variables (e.g. VITE_*, NEXT_PUBLIC_*, public API URLs).

  • Add, edit and delete variables inline.
  • Bulk import from a .env file, or export the current set back to .env.
  • Built-in secret generator for tokens and keys.

Values are injected into the build only — there’s no runtime to read them at request time.

All configuration for the site, grouped:

  • Domain — your subdomain on runsite.site.
  • Custom Domains — attach your own domain, verify DNS, automatic TLS. See Domains.
  • Build & Deploy — branch, build command, publish directory, root directory, the Auto-deploy on push toggle.

You’ll also see Metrics, Shell and Disk tabs in the UI — these are shared with Web Services and don’t apply to static sites (no container, no runtime, no persistent disk). You can ignore them.