|
| 1 | +--- |
| 2 | +description: From an AWS-focused serverless adapter to a universal Next.js portability initiative backed by Cloudflare, Netlify, and the broader community. Today, an important milestone in the OpenNext story was achieved. More still to come. |
| 3 | +--- |
| 4 | + |
| 5 | +import { Callout } from "nextra/components"; |
| 6 | + |
| 7 | +import styles from "../../styles/News.module.css"; |
| 8 | + |
| 9 | +# 3 Years of OpenNext |
| 10 | + |
| 11 | +<time dateTime="2026-03-25" className={styles.date}> |
| 12 | + March 25, 2026 |
| 13 | +</time> |
| 14 | + |
| 15 | +## Origin of OpenNext |
| 16 | + |
| 17 | +OpenNext began as a serverless adapter created by [SST](https://sst.dev) specifically for AWS Lambda, addressing the challenge of deploying Next.js applications on serverless platforms outside of Vercel's ecosystem. |
| 18 | + |
| 19 | +## OpenNext V3 and Community Expansion |
| 20 | + |
| 21 | +The launch of [OpenNext V3 in May 2024](https://github.com/opennextjs/opennextjs-aws/releases/tag/v3.0.0) marked a pivotal shift, transforming the project from an AWS-focused tool into a more universal solution for Next.js portability. This version opened the door for other platforms to build their own adapters on top of OpenNext, with Cloudflare notably leveraging OpenNext's AWS adapter as a foundation for their own implementation. The expansion of OpenNext into a multi-platform initiative backed by contributions from Cloudflare, Netlify, and the broader community demonstrated the power of open-source collaboration in overcoming technical silos and making Next.js as platform-agnostic as possible. |
| 22 | + |
| 23 | +## Collaboration with Vercel |
| 24 | + |
| 25 | +What started as an independent open-source project was later joined by Netlify and Cloudflare. Soon after, we started communicating with Vercel via unofficial channels. This collaboration grew even further with the creation of the Deployment Adapters Working Group, with others such as Google and AWS Amplify joining in. This group, in collaboration with Vercel, helped design what is today the [Deployment Adapters API](https://nextjs.org/docs/app/api-reference/config/next-config-js/adapterPath). |
| 26 | + |
| 27 | +## The Adapters API: Building the Future |
| 28 | + |
| 29 | +It all started with an RFC, shared privately in December 2024, and then [publicly in April 2025](https://github.com/vercel/next.js/discussions/77740). The RFC was met with a lot of positive feedback, and the Working Group was formed. |
| 30 | + |
| 31 | +The Adapters API helps alleviate one of the biggest challenges OpenNext had to solve: the build output. The Adapters API allows us to avoid reverse-engineering features, as the build output now follows a clear contract that every platform can follow. |
| 32 | + |
| 33 | +In Next.js 16 in October 2025, the Adapter API was released as an alpha. This was a major milestone, as it allowed us to start developing our new adapters in earnest. |
| 34 | + |
| 35 | +And now, in March 2026, **the Adapter API is stable in Next.js 16.2.** [Read more about this incredible milestone in the official Next.js announcement](https://nextjs.org/blog/nextjs-across-platforms). |
| 36 | + |
| 37 | +AWS and Cloudflare adapters are currently being built in a shared monorepo. The Netlify adapter is also in active development. We expect all three to be released by the end of 2026. |
| 38 | + |
| 39 | +<Callout> |
| 40 | + Don't worry, the current OpenNext adapters are not going anywhere. They will still be supported and |
| 41 | + maintained by the OpenNext community. In the case of Netlify, transition to the new adapter will be seamless |
| 42 | + for users. |
| 43 | +</Callout> |
| 44 | + |
| 45 | +## What's Next? |
| 46 | + |
| 47 | + |
| 48 | + |
| 49 | +Over the last three years, OpenNext has played a crucial role in pushing Next.js toward true portability. Now, the introduction of the Adapters API signals a new era. And [as announced today by the Next.js team](https://nextjs.org/blog/nextjs-across-platforms), OpenNext along with Netlify and Cloudflare are founding members of the new [Next.js Ecosystem Working Group](https://nextjs.org/ecosystem-working-group), along with Google, AWS Amplify, and others. This initiative and Vercel's associated commitments give us great confidence that Next.js will remain a flexible, open framework for years to come. For developers, this means more choices, fewer limitations, and a stronger, more inclusive web development community. |
| 50 | + |
| 51 | +The aims of OpenNext may evolve in the near future as we explore this new terrain together. Stay tuned. |
| 52 | + |
| 53 | +The future of Next.js is not just open, it's everywhere. |
| 54 | + |
| 55 | +## Read more |
| 56 | + |
| 57 | +Next.js, OpenNext, Netlify, and Google Firebase have published simultaneous companion posts: |
| 58 | + |
| 59 | +- Read about the stable Adapter API, verified adapters, and the new working group in the [Next.js blog post](https://nextjs.org/blog/nextjs-across-platforms) |
| 60 | +- Read about remaining architectural challenges in the [Netlify blog post](https://www.netlify.com/blog/the-next-js-adapter-api-just-shipped-here-s-what-comes-next) |
| 61 | +- Read about the Google Cloud perspective in the [Firebase blog post](https://firebase.blog/posts/2026/03/nextjs-adapters) |
0 commit comments