Next.Js Engineering Benchmarks
Next.Js delivery benchmarks are based on 306 merged pull requests in the last 30 days (2,282 all-time), with 15.0 hours median cycle time, 2.2 hours median review time, and 32 active contributors. AI-related signals appear on 3.3% of recent work. PR volume is down -12% compared to the prior period.
Repo vs Vercel Average
Delivery Trend and AI Signals
PR Backlog (Humans)
Excludes AI agents and automation accounts.
PR Backlog (AI Agents)
AI coding agents only.
Cycle Time by AI-Related Signals
PR Breakdown
Top AI Tools
PR Type Breakdown
Recent Pull Requests
View PR Explorer| Title | Author | AI |
|---|---|---|
| Block prefetch task until sufficient response is received | acdlite | — |
| Use a safe clock for Request Insights bookkeeping | DavidIlie | — |
| Count key length in remaining byte-budgeted LRUs | gaearon | — |
| Serve cached misses from the filesystem route cache | gaearon | — |
| Count URL key length in the filesystem route cache LRU | gaearon | — |
Methodology
Metrics are computed from merged pull request data synced daily from GitHub. AI-related metrics are directional signals inferred from pull request activity patterns and heuristics. Summary metrics use a 30-day rolling window; trends use a 90-day window. Last updated 29 minutes ago.
Updated daily from public GitHub pull requests.
See Your Team's Benchmarks