Next.js 16.2 ships a stable, public Adapter API that provides a typed, versioned description of application build output (routes, prerenders, static assets, caching rules, etc.) that any platform can target. Built in collaboration with OpenNext, Netlify, Cloudflare, AWS Amplify, and Google Cloud, the API gives hosting providers a formal contract to build against instead of reverse-engineering build output. Key additions include a shared public test suite that all adapter authors — including Vercel — must pass, a verified adapter program hosted under the Next.js GitHub org, and a new Ecosystem Working Group for early coordination on breaking changes. Vercel's own adapter uses the same public API with no private hooks. Adapters for Netlify, Cloudflare, and AWS via OpenNext are in active development.
Table of contents
How we got hereOpenNext built the bridgeThe Adapter APIThe test suiteVerified adaptersThe ecosystem working groupLearn moreSort: