Vercel pushed 35 Next.js release events in 30 days, with 419 commits backing them. Every single recent release in the ToolVitals data is a canary build, not a stable tag. That is not a criticism. It is the signal.
The canary pipeline is where Vercel’s real bets show up. Recent builds focus on three areas: prefetch inlining (now enabled by default), Turbopack native binary management (switching to cargo-binstall, sharing binaries via GitHub artifacts), and streaming rendering improvements with new forkpoints for Node.js streams. The trace server got a port conflict fix and sort mode redesign. None of this is cosmetic. Prefetch inlining changes how navigations feel. Turbopack work is about build speed at scale. Streaming forkpoints matter for React Server Components performance.
The 16.3.0 canary series also landed a blocking route dev overlay redesign and a fix for images.maximumResponseBody applying to local images. Small details, but the kind that affect daily developer experience.
What the data does not tell you
ToolVitals sees commits, releases, and GitHub stars (139k, which is massive). It does not see adoption numbers, revenue, or whether the Next.js 16 canary builds are stable enough for production. The health score of 86 and shipping score of 88 look strong, but those measure activity and consistency, not user satisfaction. The data confidence is 100 percent, but note that Vercel’s GitHub org and repo fields are null in this payload, so the metrics likely aggregate across the vercel/next.js repository specifically.
We also cannot tell how much of this shipping velocity translates to the Vercel platform (deployments, edge functions, analytics) versus Next.js core. The data is heavily Next.js weighted.
Comparisons
PostHog edges Vercel on hot score (271.9 vs 220.7) and ships more release events per month (51 vs 35), but PostHog is a different category entirely. LangChain has similar star count (134k vs 139k) but a shipping score of 32 versus Vercel’s 88, meaning LangChain’s release cadence has slowed dramatically. GitHub itself, the platform Vercel builds on, ships only 5 release events per month with a shipping score of 82.
Recommendation
If your frontend stack depends on Next.js, subscribe to the canary release notes. The prefetch inlining default and Turbopack binary changes will land in stable builds soon. If you are evaluating deployment platforms, Vercel’s shipping velocity on Next.js core is unmatched, but remember that 35 canary releases in a month also means frequent breaking changes if you track canary. Pin to stable and test upgrades deliberately.