vercel/next.js

Choose this fork only if you need its custom automation and are prepared to maintain a large, stale divergence. For most adopters, upstream Next.js is the safer choice because this fork appears significantly behind and costly to reconcile.

Choose this fork only if SuperTokens-specific example/integration work is the main requirement and you are comfortable maintaining a stale, heavily diverged Next.js snapshot. If you want current Next.js capabilities or low-maintenance adoption, upstream is the safer choice.

Choose this fork only if you need its customizations and are prepared to own a large downstream maintenance burden. If you want current Next.js features, fixes, and release cadence, upstream is the safer choice.

Choose this fork only if you want a deeply customized Next.js base and are willing to own long-term maintenance. For most adopters, upstream is the better choice because this fork is far behind and substantially diverged.

Prefer this fork only if you need its specific Turbopack/runtime modifications and are willing to own a large ongoing merge burden. For most adopters, upstream Next.js is the safer choice because this fork is materially stale and heavily diverged.