// the take
OpenNext takes a standard Next.js build and repackages it to run on AWS Lambda (or a plain Node server), covering SSR, ISR, middleware, and server actions rather than just static export. It's for teams who want to self-host Next.js on their own AWS account instead of using Vercel, typically via SST or raw CDK/Terraform.
It solves a genuinely hard problem: Next.js's server runtime (ISR revalidation, middleware, server actions, image optimization) wasn't designed with Lambda's execution model in mind, and OpenNext does the actual work of translating that instead of punting to static export. It's proven in production at scale (Gymshark, NHS England, Udacity are named users, not just logos on a page), and the team ships prerelease builds on every push to main via pkg.pr.new, so fixes land fast instead of waiting on a tagged release.
Cold start is Lambda's problem, not something a warmer function actually fixes — the README's own "(*)" next to "almost no coldstart" is the tell, and route-level lazy loading means even a warm instance can cold-start a specific path. This project is chasing Next.js's internal build output format, which isn't a stable public API, so every major Next.js release carries real risk of OpenNext lagging or breaking until it catches up. And debug mode's warning that it can triple your bundle size and disables minification suggests people have shipped it to prod by accident. If Next.js changes undocumented internals, you're dependent on this project's turnaround, not AWS's or Vercel's.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →