Dashboard

Every web service has seven tabs. Here is what each one is for.

Overview

Live deployment history, current status, and the basics of your service: type, CPU, memory, port, disk.

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

Status badge

The colored badge next to the service name reflects its current state:

Badge	State	One-line meaning
🟡	DEPLOYING	Building image or rolling out a new container.
🟢	RUNNING	Live and serving traffic.
🔵	STARTING	Coming up after Start or restart.
🔵	RESTARTING	Container restart in progress.
⚪	STOPPING	Stop in progress.
⚪	STOPPED	Manually stopped — compute released, env vars and disk kept.
💤	SLEEPING	Idled out; next request wakes it.
🔴	FAILED	Build or runtime failure — previous version keeps serving.

For the full semantics and transitions, see Runtime → Deploy states.

Metrics

Live charts of CPU, memory and instance count. Pick a window: 10 minutes, 30 minutes, 1 hour or 2 hours. Charts auto-refresh while the service is running.

Logs

Application logs from your container.

• Live tail — real-time stream of new lines as they arrive.
• Time windows — view 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.
• Filter by level — error, warn, info, debug, trace.

Shell

A terminal inside your running container — handy for debugging, running one-off scripts or checking files. Available while the service is running.

Environment

Manage environment variables and secrets.

• Add, edit and delete variables inline.
• Values are masked by default; click the eye to reveal.
• Bulk import from a .env file, or export the current set back to .env.
• Built-in secret generator for tokens and keys.

When saving, you pick how aggressively the change applies:

Mode	Effect
Save	Stored only. Applied on the next restart or deploy.
Save & Deploy	Restart the container now with the new values.
Save & Rebuild & Deploy	Build a new image and deploy. Use when the change affects build-time.

Disk

Visible only when persistent storage is enabled. Shows disk size, mount path and current usage. The disk survives restarts and redeploys — perfect for SQLite, uploaded files or local caches.

Settings

All configuration for the service, grouped:

• Domain — your subdomain on runsite.app.
• Custom Domains — attach your own domain, verify DNS, automatic TLS. See Domains.
• Build & Deploy — branch, build / start / pre-deploy commands, Dockerfile path, root directory, the Auto-deploy on push toggle.
• Scaling — min and max instances. See Scaling & resources.