#111111th of 204 in Backends, databases and hosting

opennextjs-aws

Adapter that packages Next.js build output for AWS Lambda or Node servers

Stars
5.1k
License
MIT
Last commit
Nov 2026
Last release
Nov 2026
Language
TypeScript
Stars, last 29 weeks+92
25 Apr 2026: 4,959 stars2 May 2026: 4,963 stars9 May 2026: 4,968 stars16 May 2026: 4,969 stars23 May 2026: 4,974 stars30 May 2026: 4,977 stars6 Jun 2026: 4,982 stars13 Jun 2026: 4,984 stars20 Jun 2026: 4,987 stars27 Jun 2026: 4,989 stars4 Jul 2026: 4,993 stars11 Jul 2026: 4,996 stars18 Jul 2026: 4,997 stars25 Jul 2026: 4,998 stars1 Aug 2026: 4,999 stars8 Aug 2026: 5,004 stars15 Aug 2026: 5,006 stars22 Aug 2026: 5,010 stars29 Aug 2026: 5,014 stars5 Sept 2026: 5,019 stars12 Sept 2026: 5,020 stars19 Sept 2026: 5,022 stars26 Sept 2026: 5,025 stars3 Oct 2026: 5,029 stars10 Oct 2026: 5,032 stars17 Oct 2026: 5,036 stars24 Oct 2026: 5,041 stars31 Oct 2026: 5,043 stars7 Nov 2026: 5,048 stars14 Nov 2026: 5,051 stars

4,959 on 25 Apr 20265,051 on 14 Nov 2026

From GitHub's daily star counts.

Checked on GitHub.

Overview

OpenNext takes the Next.js build output and converts it into packages deployable on AWS Lambda or a classic Node.js server. It covers App and Pages Router, ISR, middleware, server actions and image optimization, and is configured through an optional open-next.config.ts. It also ships a warmer function to reduce Lambda cold starts.

Who it is for: Teams self-hosting Next.js apps on AWS Lambda or Node.js

Strengths

  • Supports App and Pages Router, ISR, middleware, server actions and image optimization
  • Runs without a config file; defaults apply when open-next.config.ts is absent
  • Includes a warmer function to reduce Lambda cold starts
  • Prerelease packages published on every push to main via pkg.pr.new

Weaknesses

  • Targets Next.js 15; some features are listed as work in progress
  • Native support limited to AWS Lambda and Node.js server
  • Warmer does not remove all cold starts, such as lazy-loaded routes
  • Debug mode can make output 2-3x larger

What it needs

  • no GPU
  • Needs Next.js, AWS Lambda, Node.js

What changed

From the release notes. No flag means the note does not say so, not that the upgrade is safe.

Known problems

Reported, then fixed by a linked change

Titles are the reporters' own words, taken from the project's GitHub issues and ranked by reactions. We have not tried to reproduce any of them.

Also in Backends, databases and hosting

See all 204
Also in Backends, databases and hosting
RankProjectScore
1bunJavaScript and TypeScript runtime with bundler, test runner and package manager96.7k starscustom license94 out of 100
2coolifySelf-hosted Heroku and Vercel alternative that deploys apps and databases over SSH66.2k starsApache-2.093 out of 100
3strapiHeadless CMS that generates REST and GraphQL APIs from content models Live demo ↗ (opens in a new tab)73.5k starscustom license92 out of 100
#4traefikHTTP reverse proxy and load balancer that auto-discovers routes from orchestrators65.6k starsMIT92 out of 100
#5appwriteBackend with auth, databases, storage, functions and an MCP server for agents Live demo ↗ (opens in a new tab)58.2k stars+653 (+1.1%) in 30 daysBSD-3-Clause92 out of 100