Vercel deployments, with production kept separate from previews
Production state, build times, and deploy history for one Vercel project on a single tile.
Get early access to the Vercel integration
dev-views is in active development. Join the waitlist and we will note your interest in Vercel.
The question you ask about a Vercel project is almost always the same one: is production fine, and did the last deploy work? Vercel answers it, but the answer lives behind a project switcher and a deployment list that mixes previews in with the thing actually serving traffic.
dev-views reads one project through the Vercel API and separates those two concerns. Production state, the commit currently serving it, and how long ago it changed sit apart from the general deploy stream. Build health — success rate, average build time, what failed this week — is its own group. dev-views never triggers a deployment, promotes one, or changes a setting.
What dev-views reads from Vercel
25 readings, computed from the Vercel API. There are no defaults — you choose which become tiles and in what order, because guessing which of 25 matters to you would be wrong for most people.
Production state
The result of the deployment currently serving production, kept separate from whatever preview deployed most recently.
Production commit
The commit actually serving traffic right now, next to the domain pointing at it — the answer to 'is my fix live yet'.
Deploy success rate
The share of finished deployments that reached ready. A build that fails intermittently shows up here before it becomes a pattern you notice by hand.
Average build time
Mean time from build start to ready across successful builds, with the most recent build's time beside it so a slow trend is obvious.
Building now
Deployments queued or building at this moment, so a stuck build is visible without opening the deployments tab.
The full list
- Deploys, 30 days
- Deploys, 7 days
- Deploys today
- Preview deploys, 30 days
- Last deploy
- Last deploy state
- Last deploy branch
- Deploy success rate
- Failed deploys, 7 days
- Building now
- Average build time
- Last build time
- Production state
- Last production deploy
- Production commit
- Production domain
- Domains
- Framework
- Node version
- Function region
- Git repository
- Created
- Web Analytics
- Speed Insights
- Deployment protection
How the connection works
- 01Create an access token in Vercel under Account Settings → Tokens. Scope it to one team and set an expiry date.
- 02Paste it into dev-views, which verifies it against the Vercel API before storing anything.
- 03Pick the project to watch. Personal and team projects both appear, provided the token can see them.
- 04Choose which of the 25 readings become tiles and arrange them.
- Credential
- A access token (24 characters), created under Account Settings → Tokens.
- Watches
- One project, chosen after connecting.
- Refresh
- Every 60 seconds, cached per user so browsing does not re-spend your API budget. A manual refresh forces a read immediately.
- Storage
- Encrypted with AES-256-GCM before it is stored. The encryption key lives in the environment, never in the database, and the credential is never sent back to the browser.
Vercel tokens cannot be made read-only. What they can be is narrowed to a single team at creation time and given an expiry date — do both. dev-views only ever reads, but the token itself carries the permissions of whoever created it, and you should know that before you paste it.
What your dashboard shows
- Production treated as its own thing: state, commit, domain, and time since it last changed, rather than buried in a list where the top entry is usually a preview.
- A failed deployment or a stalled build surfaced in the attention band above the dashboard even if you never added that tile.
- Project facts that are otherwise three clicks into settings — framework preset, Node version, function region, and whether previews sit behind deployment protection.
Who this is for
- Solo developers shipping to Vercel several times a day who want production state visible without a project switcher.
- Anyone running previews for a team and needing failed builds to be loud rather than discoverable.
- Developers watching build times creep up and wanting a number for it instead of an impression.
Vercel questions
Which Vercel metrics does dev-views track?
Twenty-five readings for one project: deployment counts over today, 7 days, and 30 days with previews counted separately; build health including success rate, failures in the last week, deployments building right now, and average and last build time; production state, the commit and domain currently serving it, and when it last changed; and project configuration such as framework preset, Node version, function region, connected Git repository, and whether Web Analytics, Speed Insights, and deployment protection are enabled.
Can I give dev-views a read-only Vercel token?
Vercel does not offer one. Its access tokens inherit the permissions of the account that created them, and there is no read-only variant. Two things do help: a token can be scoped to a single team when you create it, and it can be given an expiry date. dev-views recommends both on the connect screen, stores the token encrypted with AES-256-GCM, and has no code path that writes to the Vercel API.
Does it show preview deployments as well as production?
Yes, but deliberately apart. Preview deploys over 30 days are their own reading, while the production group tracks only the deployment actually serving traffic. Mixing them is what makes the Vercel deployments list hard to read at a glance — the newest entry is usually a preview, not the thing your users are hitting.
Can I watch a project owned by a team?
Yes, as long as the token has access to that team. Personal and team projects both appear in the picker. A token narrowed to one team will only show that team's projects, which is the trade-off for scoping it tightly.
How often does it refresh?
Every 60 seconds, cached per user and project so navigating between pages does not refetch. A manual refresh button forces a read immediately when you have just pushed something and do not want to wait out the window.
Works alongside
dev-views is most useful when more than one service is on the board. These are the ones people connect next to Vercel.
Watch Vercel alongside the rest of your stack
One read-only surface for every service you run. Join the waitlist for early access.