Vercel
Vercel is a cloud platform for static frontends and serverless functions.
What detecting Vercel tells you about a site
Vercel is the hosting and edge platform from the makers of Next.js. It is one of the most candid hosts to detect: a Server: Vercel header, X-Vercel-Id and X-Vercel-Cache (HIT/MISS/STALE) headers, and assets served from its edge network with /_next/ paths when it is running a Next.js app. Spotting it tells you a modern front-end team that deploys via git push to a serverless/edge platform — strongly correlated with Next.js, preview-deploy workflows and a JAMstack or hybrid-render architecture.
The detail that matters for Vercel
The X-Vercel-Cache header is a live read on rendering strategy: frequent HIT values mean statically generated or ISR-cached pages served from the edge, while consistent MISS on dynamic routes means server-rendered or edge-function responses computed per request.
Vercel in a real-world stack
When you find Vercel, it rarely travels alone. Almost always Next.js, frequently with a headless CMS (Contentful/Sanity) and an edge/serverless data layer.
About
Vercel is a cloud platform for static frontends and serverless functions.
Categories: PaaS
Quick facts
Detection methodology for PaaS
Platform-as-a-Service offerings show up as response headers and deployment domains. Heroku's `Server: Cowboy` plus `*.herokuapp.com`; Render's `*.onrender.com`; Fly.io's `*.fly.dev`. We pair the host detection with framework signals so you can tell what's running on the platform — a Heroku dyno serving Rails looks very different from a Heroku dyno serving Node, even though both fit the same hosting fingerprint.
How we detect Vercel
Sourcemap Explorer carries 4 fingerprint signals for Vercel, spread across 1 channel — response header. The exact patterns are listed below, and you can replay each one in Chrome DevTools to confirm a match by hand.
Each signal alone is rarely conclusive — Sourcemap Explorer cross-references all of them and weights by confidence. You can reproduce any of these checks yourself in Chrome DevTools.
Server-side fingerprint: the response header reveals the technology behind the page. Visible in DevTools → Network → response headers.
server: ^now|Vercel$
x-now-trace:
x-vercel-cache:
x-vercel-id:
FAQ
How do I check if a website is using Vercel?
Open the page in Chrome, click the Sourcemap Explorer toolbar icon, and read the Stack tab. Vercel's specific fingerprints here are response header, and the popup flags Vercel whenever any combination of them is found. The same checks can be reproduced manually in DevTools — see the "How we detect" section above.
What Vercel version can Sourcemap Explorer detect?
Vercel ships as a hosted paas rather than a bundled npm package, so version-specific detection isn't always possible. Where the platform leaks a version in response headers (`X-Powered-By`, `Server`, generator meta tags) we surface it; otherwise we report presence only.
How much does Vercel cost?
Vercel's pricing model is documented as: freemium, low, recurring, poa. Detection is independent of the pricing tier — Sourcemap Explorer flags the technology by its fingerprints, regardless of which paid plan a site is on. See the official site for the current pricing page.
Where can I read more about Vercel?
Official site: https://vercel.com. For Sourcemap Explorer's detection guide, see the deep-dive link below or the related guides in the cross-link section.
Keep reading on Sourcemap Explorer
Alternative tools
Detected by Sourcemap Explorer
Open the popup on any page running Verceland you'll see the exact version pulled from the bundled package.json when sourcemaps are exposed.