Feature
Deploy status dashboard for Netlify, Vercel and GitHub
See the live release, latest deploy attempt, open pull requests and CI runs for every site from Netlify, Vercel and GitHub, beside the project's health.
Updated 5 min read
A failed deploy is quiet. The old version keeps running, nothing looks broken and the change you promised the client never goes live. The deploy status dashboard puts every site's release, build and pull requests in one place.
What does the deploy dashboard show?
For each project you connect:
- Live release: which build is serving visitors, and when it went live.
- Latest attempt: whether the most recent deploy succeeded, is building or failed.
- Open pull requests: how many are open and what they are called.
- CI runs: recent workflow runs and whether they passed.
- Health beside it: the uptime of the same project, so you can tell whether a problem is the site or the last release.
Why are the live release and the latest attempt separate?
They are two facts. When a deploy fails, the previous release keeps serving traffic, so the site looks healthy while the new work is stuck. If a dashboard showed only the latest attempt, a failed build would look like an outage. If it showed only the live release, a failed build would be invisible. Datumboard shows both.
Which services does it connect to?
- GitHub: repositories, the latest commit, pull requests and workflow runs.
- Netlify: sites and their deploys.
- Vercel: projects and their deployments.
You map a repository and a hosting site to a project, so each client's deploys appear on that client.
What access does it need?
Connections only read data. For GitHub you can use a fine-grained token limited to the repositories you choose.
| Permission | Access | Used for |
|---|---|---|
| Metadata | Read, automatically included | Repository details |
| Contents | Read-only | Latest commit |
| Pull requests | Read-only | Open pull request count |
| Actions | Read-only | CI workflow runs |
Datumboard does not deploy, merge, restart or roll anything back.
How does it relate to Lighthouse scores?
Datumboard keeps Lighthouse results over time and shows a score drop next to the deploy that came before it. That tells you where to start looking after a regression. It is timing, not proof of cause. Our guide on tracking Lighthouse scores over time explains how to read it.
How do I get started?
Datumboard is in early access. You can join the list below and, when it opens, connect GitHub, Netlify or Vercel and map each site to a project.
Frequently asked questions
Why does Datumboard show both the live release and the latest attempt?
Because they can be different. If the latest deploy fails, the previous release keeps running, so the site looks fine while the new change never went out. Showing both tells you whether the site is current and whether the last attempt succeeded.
Which hosting and code services does it read?
GitHub for repositories, commits, pull requests and workflow runs, and Netlify and Vercel for sites, projects and deployments. Connections only read data.
What GitHub permissions does the token need?
Four read permissions on the repositories you choose - Metadata, Contents, Pull requests and Actions. A fine-grained token limited to those repositories is enough.
Can Datumboard deploy or roll back for me?
No. It only shows what exists, and it does not deploy, merge, restart or roll anything back.
Keep reading
- How-toTrack Lighthouse scores over timeA single Lighthouse run is noisy. Learn how to run it consistently, store the results, compare them with your deploys and tell a real regression from variance.Read
- Use caseDashboard for managing multiple client websitesSee uptime, SSL and domain renewals, deploys, Search Console and costs for every client site on one screen, and hear about problems before your client does.Read
- ChecklistWebsite monitoring checklist for freelancersA practical checklist of what to monitor on every client website, from uptime and SSL to domains, deploys and search, and how often to check each.Read