Is OpenNext really the key to Next.js portability?

Next.js, originally created to facilitate building full-stack applications with React, has faced criticism for its limited compatibility with serverless platforms other than Vercel, the company responsible for its development. As Next.js evolved to incorporate more backend features like server-side rendering and API routes, it became optimized for Vercel's serverless infrastructure, leading to issues when deploying on other platforms like AWS Lambda and Cloudflare Workers. In response, the community developed OpenNext, a project that allows Next.js applications to be compatible with various serverless platforms by repackaging the build output to work with their respective infrastructures. OpenNext facilitates this process by providing adapters for platforms such as AWS, Cloudflare, and Netlify, enabling features like Incremental Static Regeneration and image optimization outside Vercel's ecosystem. Despite concerns about Vercel's influence over the React and Next.js ecosystem, OpenNext demonstrates the community's ability to advocate for increased portability and openness, with Vercel now collaborating on standardizing deployment adapters to enhance cross-platform compatibility.