The Deployer documentation
After you're live: the Dashboard

Dashboard overview

Once your app is live, the Dashboard is your home base. It's the first tab on any project, and it gathers everything about your running app onto one screen: its web addresses, its health, its servers, what it costs, and the history of every deployment. This page is a quick tour so you know where to look. For all your projects at once, see the Overview page.

Top actions

Two buttons sit at the top of the Dashboard:

  • Pull & Restart: pulls the latest code from your branch and restarts your app, with live logs like a normal deployment. See Pull & Restart and auto-deploy.
  • Environment variables: opens the manager for your app's settings and secret keys. Applying a change does a quick, targeted redeploy. See environment variables.

If something only you can do is waiting (a deployment paused on a manual step, or an add-on whose setup can't be automated), a box says how many things need you, with the steps for each.

The four tiles

  • App: whether the app is Live, Needs attention or Not live yet, and its address. Click it to open the app.
  • Latest deployment: what the last deployment did, its status, how it started and when. Click it for its logs.
  • Uptime: on the Pro and Team plans, The Deployer checks your app's address every few minutes. The tile shows the share of the last 7 days it was answering. Click it for the details and recent incidents. You get an email when the app stops answering and again when it's back, and when a deploy fails; choose which emails you want under Alerts on your Profile page.
  • Est. cost this month: the estimate so far this month and about what it costs a month, lower while servers are stopped. Click it to see what it costs, item by item. Your cloud provider bills you directly. See costs and billing.

The cards

  • Deployments: every deploy, pull and restart, scale and auto-deploy, newest first. Each row shows how it started (Manual, Push, Auto, Env, Domain, Scale and others) and its status. It's searchable and filterable, and clicking a row opens that deployment's logs. See searching and filtering.
  • Addresses: where people reach the app, in tabs. Services lists the app's addresses with a health badge (Healthy, Needs setup or Unreachable). Domains lists every domain pointing at the app, with Add domain (see custom domains). Logins shows the sign-in details for bundled tools like Grafana, once there are any (see service logins).
  • Who can open this app: limit the app to approved networks or a password. See who can open your app.
  • Environments: production and its copies (Dev, UAT, Staging), once there are two or more. See environments.
  • This project's server (or Runtime for managed hosting): each machine with CPU, RAM and disk meters, controls, and Connect via SSH to open a terminal. See connecting to your servers.
  • Connected services: the databases, caches, queues and buckets attached to this project, with an Attach button. See attaching a service.
  • Scaling: give your app more power when traffic grows.
  • Build settings, Automatic retries and Health check: how the app is built, how many times a failed deployment is tried again, and the route that proves the app is up.

Good to know

  • The Dashboard updates live. When a deployment moves, a server starts or stops, or the project changes stage, the page is told straight away and updates what changed, without a reload. The CPU, RAM and disk meters are measurements rather than events, so they refresh about every 30 seconds. If the live connection drops, the app reconnects by itself, and until it does, the page checks for changes every few seconds instead.
  • Redeploys of server-based apps are health-gated. When an app already running on servers is redeployed, each new container must pass its health check before the old one is removed. A first deploy isn't rolling, managed hosting uses the provider's own rollout, and resizing a single server takes it offline for about 1 to 3 minutes.
  • Some cards and tabs only appear once there's something to show. If one is missing, that part of your project usually isn't set up yet.