<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>Wasp Blog</title>
        <link>https://wasp.sh/resources</link>
        <description>Wasp Blog</description>
        <lastBuildDate>Wed, 09 Sep 2026 00:00:00 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <item>
            <title><![CDATA[Is There a Laravel for JavaScript? AdonisJS, Next.js, and Wasp Compared (2026)]]></title>
            <link>https://wasp.sh/resources/2026/09/09/laravel-for-javascript-2026</link>
            <guid>https://wasp.sh/resources/2026/09/09/laravel-for-javascript-2026</guid>
            <pubDate>Wed, 09 Sep 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Is there a Laravel for JavaScript? AdonisJS ports Laravel idioms to TypeScript, Next.js leaves the backend to you, and Wasp owns the boilerplate.]]></description>
            <content:encoded><![CDATA[
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="tldr">TL;DR<a href="https://wasp.sh/resources/2026/09/09/laravel-for-javascript-2026#tldr" class="hash-link" aria-label="Direct link to TL;DR" title="Direct link to TL;DR" translate="no">​</a></h2>
<ul>
<li class="">
<p>"Laravel for JS" is really two questions: <em>Laravel idioms in TypeScript</em> (where <a href="https://adonisjs.com/" target="_blank" rel="noopener noreferrer" class=""><strong>AdonisJS</strong></a> wins) or <em>Laravel's batteries-included DX</em> (where <a class="" href="https://wasp.sh/"><strong>Wasp</strong></a> is built around the same goal).</p>
</li>
<li class="">
<p><strong>AdonisJS</strong> is the closest 1:1 lineage: service container, providers, Lucid (ActiveRecord), Edge templates, and Ally for social auth. If you want Laravel muscle memory in TypeScript, this should be your pick.</p>
</li>
<li class="">
<p><strong>Wasp</strong> treats client, server, and database as peers in one declarative <code>.wasp.ts</code> config file, reducing boilerplate for both humans and AI. AdonisJS and Laravel are backend-first frameworks where the frontend is a transport target you wire up per page.</p>
</li>
<li class="">
<p>On the same SaaS feature, Wasp used <strong>38% fewer tokens</strong> and cost <strong>44% less</strong> than Next.js when built with Claude Code (<a class="" href="https://wasp.sh/blog/2026/03/26/nextjs-vs-wasp-40-percent-less-tokens-same-app">benchmark</a>).</p>
</li>
<li class="">
<p>We benchmarked the same small feature (auth + Google OAuth + dashboard + a CRUD model + two operations + a daily job) across all three: roughly <strong>7 files / ~85 lines of glue in Wasp</strong> vs <strong>17–18 files / ~300 lines in AdonisJS or Next.js</strong>.</p>
</li>
<li class="">
<p>One-line decision: <em>want Laravel idioms in TS</em> → AdonisJS. <em>Want Laravel's productivity feeling on a modern, AI-coding-friendly stack</em> → Wasp.</p>
</li>
</ul>
<!-- -->
<hr>
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="why-laravel-for-javascript-keeps-coming-up">Why "Laravel for JavaScript" Keeps Coming Up<a href="https://wasp.sh/resources/2026/09/09/laravel-for-javascript-2026#why-laravel-for-javascript-keeps-coming-up" class="hash-link" aria-label="Direct link to Why &quot;Laravel for JavaScript&quot; Keeps Coming Up" title="Direct link to Why &quot;Laravel for JavaScript&quot; Keeps Coming Up" translate="no">​</a></h2>
<p>It's a recurring search query, and not just from one camp. Laravel developers considering TypeScript want to know if there's a framework that won't make them give up the productivity they're used to. JavaScript developers who've watched Laravel from the outside want some of the same magic on their own stack. Founders comparing stacks for a new app just want to know what "the obvious choice" is in the JS world. We first wrote about this question in 2024, after Theo's video: <a class="" href="https://wasp.sh/blog/2024/05/29/why-we-dont-have-laravel-for-javascript-yet">why we don't have a Laravel for JavaScript yet</a>.</p>
<p>What people are actually asking for, when you read between the lines, is the same: opinionated full-stack DX, batteries included, low boilerplate, <em>the framework owns the boring parts</em>. They want a framework that takes care of auth, jobs, scaffolding, deployments, etc. and doesn't lock them into unwanted or expensive service providers.</p>
<p>They're <em>not</em> asking for "another Express" or "another Next.js" where you're responsible for picking and wiring together dozens of libraries before even writing a feature.</p>
<p>This is what makes Laravel so genuinely strong. It's got Eloquent, a service container, a great ecosystem, and an especially good deployment story (Forge, Cloud, Vapor). The JS frameworks in this post don't win on every axis, and we'll be specific about where they don't. There's no single "JS Laravel" but there are three real candidates depending on which part(s) of Laravel you actually wanted.</p>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="your-three-real-options">Your Three Real Options<a href="https://wasp.sh/resources/2026/09/09/laravel-for-javascript-2026#your-three-real-options" class="hash-link" aria-label="Direct link to Your Three Real Options" title="Direct link to Your Three Real Options" translate="no">​</a></h2>
<p>The three serious candidates are AdonisJS, Next.js, and Wasp, and they're aimed at developers asking slightly different versions of the question.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="adonisjs">AdonisJS<a href="https://wasp.sh/resources/2026/09/09/laravel-for-javascript-2026#adonisjs" class="hash-link" aria-label="Direct link to AdonisJS" title="Direct link to AdonisJS" translate="no">​</a></h3>
<p><a href="https://adonisjs.com/" target="_blank" rel="noopener noreferrer" class=""><strong>AdonisJS</strong></a> is the closest direct port of Laravel's architecture to TypeScript. The service container, providers, and IoC pattern come straight from the Laravel playbook. <a href="https://docs.adonisjs.com/guides/database/introduction" target="_blank" rel="noopener noreferrer" class="">Lucid</a> is an ActiveRecord-style ORM in the Eloquent tradition, <a href="https://docs.adonisjs.com/guides/auth/social-authentication" target="_blank" rel="noopener noreferrer" class="">Ally</a> handles social auth, <a href="https://docs.adonisjs.com/guides/views-and-templates/introduction" target="_blank" rel="noopener noreferrer" class="">Edge</a> is a server-rendered template engine, and the <code>node ace</code> CLI is the spiritual cousin of <code>php artisan</code>. If you're a Laravel developer who wants TypeScript without giving up your reflexes, AdonisJS is the framework most likely to feel like home.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="nextjs">Next.js<a href="https://wasp.sh/resources/2026/09/09/laravel-for-javascript-2026#nextjs" class="hash-link" aria-label="Direct link to Next.js" title="Direct link to Next.js" translate="no">​</a></h3>
<p><a href="https://nextjs.org/" target="_blank" rel="noopener noreferrer" class=""><strong>Next.js</strong></a> isn't actually Laravel-like; it's a React meta-framework with no opinions about your backend, your auth, your database, or your jobs. But it's where many "Laravel for JavaScript" searches end up, partly because it's the loudest framework in the JS world and partly because people assume "full-stack JavaScript" means Next.js by default. We're including it in the comparison for completeness, and because many readers are comparing against it.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="wasp">Wasp<a href="https://wasp.sh/resources/2026/09/09/laravel-for-javascript-2026#wasp" class="hash-link" aria-label="Direct link to Wasp" title="Direct link to Wasp" translate="no">​</a></h3>
<p><a class="" href="https://wasp.sh/"><strong>Wasp</strong></a> takes a different angle. Instead of porting Laravel's runtime patterns, it re-imagines the productivity story around a compiler. Features are defined in a <code>.wasp.ts</code> config file by declaring your routes, pages, auth methods, backend operations, and background jobs at a high level, and the Wasp compiler generates a typed React + Node.js + Prisma app from it.</p>
<p>(disclaimer: this is us!) We didn't build Wasp as a Laravel port, we built it because we thought the Laravel-style productivity feeling deserved a fresh attempt on a modern JS stack. AdonisJS lands closer to Laravel-the-architecture, whereas Wasp aims at Laravel-the-feeling.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="head-to-head-comparison">Head-to-Head Comparison<a href="https://wasp.sh/resources/2026/09/09/laravel-for-javascript-2026#head-to-head-comparison" class="hash-link" aria-label="Direct link to Head-to-Head Comparison" title="Direct link to Head-to-Head Comparison" translate="no">​</a></h3>
<table><thead><tr><th>Feature</th><th>AdonisJS</th><th>Next.js</th><th>Wasp</th></tr></thead><tbody><tr><td><strong>Pitch</strong></td><td>"Laravel for Node" (literal)</td><td>React meta-framework</td><td>Truly full-stack, AI-native framework</td></tr><tr><td><strong>Architectural model</strong></td><td>Runtime framework, IoC + providers</td><td>Runtime + file-based routing</td><td>Compiler; <code>.wasp.ts</code> config file is the spec</td></tr><tr><td><strong>High-level app map?</strong></td><td>No. Spread across <code>start/</code>, <code>config/</code>, <code>app/</code></td><td>No. File system + route handlers</td><td>Yes. Features defined in <code>.wasp.ts</code> config file(s)</td></tr><tr><td><strong>Frontend</strong></td><td>Inertia (React/Vue) or Edge templates</td><td>React (native)</td><td>React (framework-owned)</td></tr><tr><td><strong>ORM</strong></td><td>Lucid (ActiveRecord)</td><td>BYO (Prisma/Drizzle)</td><td>Prisma (integrated)</td></tr><tr><td><strong>Auth</strong></td><td><code>@adonisjs/auth</code> • Ally for social</td><td>BYO (NextAuth/Clerk)</td><td>Declarative in config</td></tr><tr><td><strong>Background jobs</strong></td><td><code>@adonisjs/queue</code> (first-party, experimental)</td><td>BYO (Inngest, <a href="https://trigger.dev/" target="_blank" rel="noopener noreferrer" class="">Trigger.dev</a>, Vercel Cron)</td><td>Built-in (pg-boss)</td></tr><tr><td><strong>Type safety, DB → UI</strong></td><td>Lucid types + Inertia (manual plumbing per page)</td><td>Partial (Server Actions infer; NextAuth Session needs augmenting)</td><td>Automatic, generated</td></tr><tr><td><strong>Files to ship the canonical feature</strong></td><td>~18</td><td>~17</td><td><strong>~7</strong></td></tr><tr><td><strong>Glue/wiring LOC</strong></td><td>280–340</td><td>~310</td><td><strong>~80–95</strong></td></tr><tr><td><strong>Deploy</strong></td><td>BYO (Docker is happy path)</td><td>Vercel-first</td><td><code>wasp deploy</code> (Fly/Railway), Docker for self-host</td></tr><tr><td><strong>AI-coding fit</strong></td><td>Multi-file mental model</td><td>Mixed (custom stack to map)</td><td>Single-file architecture map</td></tr><tr><td><strong>Maturity</strong></td><td>10+ years, v7.x</td><td>Industry standard</td><td>Beta, approaching 1.0</td></tr></tbody></table>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="why-wasp-lands-closest-to-the-second-question">Why Wasp Lands Closest to the Second Question<a href="https://wasp.sh/resources/2026/09/09/laravel-for-javascript-2026#why-wasp-lands-closest-to-the-second-question" class="hash-link" aria-label="Direct link to Why Wasp Lands Closest to the Second Question" title="Direct link to Why Wasp Lands Closest to the Second Question" translate="no">​</a></h2>
<p>The honest concession first: if you want Laravel idioms in TypeScript (service container, providers, Eloquent-style models, a Tinker-equivalent REPL), AdonisJS will feel more like home than Wasp. But "Laravel for JS" is two questions, and Wasp is built around the second one: <em>give me Laravel's batteries-included DX, where the framework, not me, owns the boilerplate.</em></p>
<p>The concrete differentiators:</p>
<ul>
<li class=""><strong>The config file gives one mental model.</strong> Wasp's config-driven approach (e.g. <code>main.wasp.ts</code>) aggregates routes, pages, auth, jobs, operations, and APIs making it easier to read and write features. AdonisJS spreads the equivalent across <code>start/routes.ts</code>, <code>start/kernel.ts</code>, <code>config/auth.ts</code>, <code>config/ally.ts</code>, <code>app/models/</code>, and <code>adonisrc.ts</code>. Both produce running apps; only one of them produces a single architectural map.</li>
<li class=""><strong>Client as a peer, not a transport target.</strong> Inertia is a real, well-built bridge. But the architectural posture is different. In AdonisJS, the React app sits at the other end of a per-page Inertia contract you author. In Wasp, the React app is a first-class layer in the same spec that declares your routes, auth, and operations. One mental model spans the boundary instead of two. Scope of this claim: client + server + DB cohesion. We're not making the bigger claim about deploy, where Laravel's Forge/Cloud/Vapor are genuinely strong and Wasp is younger.</li>
<li class=""><strong>End-to-end type safety, automatic.</strong> Prisma → operations → React, with no manual plumbing. AdonisJS has Lucid types, but the Inertia client/server boundary is something you type per page.</li>
<li class=""><strong>Less code to ship the same feature.</strong> AdonisJS landed at roughly 18 files and 280–340 lines of glue/wiring; Next.js at 17 files and ~310 lines; <strong>Wasp at 7 files and ~80–95 lines</strong>. The savings come from not writing what the framework can derive.</li>
<li class=""><strong>Boilerplate isn't just a developer cost, it's an AI cost.</strong> Wasp used <strong>38% fewer tokens</strong> and cost <strong>44% less</strong> ($2.87 vs $5.17) than Next.js on the same SaaS-feature build with Claude Code, with roughly 70% higher token efficiency. (<a class="" href="https://wasp.sh/blog/2026/03/26/nextjs-vs-wasp-40-percent-less-tokens-same-app">Full benchmark.</a>) The reason is structural: AI tools re-read the codebase on every turn, so a smaller codebase compounds.</li>
<li class=""><strong>No cloud lock-in deploy.</strong> <code>wasp deploy</code> ships to Fly or Railway in one command, and you can self-host on any VPS via Docker. AdonisJS deployment is BYO (Docker is the happy path); Next.js works best on Vercel, with caveats elsewhere.</li>
<li class=""><strong>PostgreSQL-backed jobs by default.</strong> No Redis required, and the scheduler runs in the same process as the server. AdonisJS's queue package needs a separate <code>node ace queue:work</code> process and is currently labeled experimental.</li>
</ul>
<p>Concretely, here's what the single architectural map looks like (abridged from the <a class="" href="https://wasp.sh/docs/features/spec">Wasp Spec reference</a>):</p>
<div class="language-typescript codeBlockContainer_Q34C theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_ZoZC"><pre tabindex="0" class="prism-code language-typescript codeBlock_aRLL thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__LR8"><div class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> app</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> action</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> job</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> page</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> query</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> route </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'@wasp/spec'</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> Dashboard </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'./src/pages/Dashboard'</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">with</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> type</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'ref'</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> getConfig</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> userSignupFields </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'./src/auth/google'</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">with</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> type</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'ref'</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> getTasks</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> createTask </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'./src/server/tasks'</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">with</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> type</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'ref'</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> sendDailyDigest </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'./src/server/jobs/digest'</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">with</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> type</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'ref'</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">export</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">default</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">app</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  name</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'todoApp'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  title</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'ToDo App'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  wasp</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> version</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'^0.25.0'</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  auth</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    userEntity</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'User'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    methods</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      google</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> configFn</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> getConfig</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> userSignupFields </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    onAuthFailedRedirectTo</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'/login'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    onAuthSucceededRedirectTo</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'/dashboard'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  spec</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">route</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">'DashboardRoute'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'/dashboard'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">page</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">Dashboard</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> authRequired</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token boolean" style="color:#36acaa">true</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">query</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">getTasks</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> entities</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token string" style="color:#e3116c">'Task'</span><span class="token punctuation" style="color:#393A34">]</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">action</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">createTask</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> entities</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token string" style="color:#e3116c">'Task'</span><span class="token punctuation" style="color:#393A34">]</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">job</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">sendDailyDigest</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      executor</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'PgBoss'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      entities</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token string" style="color:#e3116c">'User'</span><span class="token punctuation" style="color:#393A34">]</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      schedule</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> cron</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'0 9 * * *'</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">]</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><br></div></code></pre></div></div>
<p>Routes, auth, queries, actions, scheduled jobs all exist in the config file. That's also what AI tools see when you point them at your project, so it acts like a spec or map of your entire app that AI can easily read, keep in context, and build upon.</p>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="build-it-three-ways-a-side-by-side-snapshot">"Build It Three Ways": A Side-by-Side Snapshot<a href="https://wasp.sh/resources/2026/09/09/laravel-for-javascript-2026#build-it-three-ways-a-side-by-side-snapshot" class="hash-link" aria-label="Direct link to &quot;Build It Three Ways&quot;: A Side-by-Side Snapshot" title="Direct link to &quot;Build It Three Ways&quot;: A Side-by-Side Snapshot" translate="no">​</a></h2>
<p>We quickly tested the same feature in all three frameworks: signup/login + Google OAuth, a dashboard behind auth, a <code>Task</code> model, two operations (<code>getTasks</code>, <code>createTask</code>), and a daily digest job at 9am. This is what it took to achieve that feature in each framework:</p>
<div class="language-text codeBlockContainer_Q34C theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_ZoZC"><pre tabindex="0" class="prism-code language-text codeBlock_aRLL thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__LR8"><div class="token-line" style="color:#393A34"><span class="token plain">AdonisJS (~18 files, ~310 LOC of wiring):</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  config/auth.ts • config/ally.ts • config/queue.ts • adonisrc.ts</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  start/routes.ts • start/kernel.ts • start/scheduler.ts</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  app/middleware/auth_middleware.ts • app/models/{user,task}.ts</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  app/controllers/{session,social,tasks,dashboard}_controller.ts</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  app/jobs/send_daily_digest.ts</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  database/migrations/*.ts</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  inertia/pages/{login,dashboard}.tsx</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">Next.js (~17 files, ~310 LOC of wiring):</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  auth.config.ts • auth.ts • app/api/auth/[...nextauth]/route.ts</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  middleware.ts • lib/db.ts • prisma/schema.prisma</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  app/(auth)/{login,register}/page.tsx</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  app/dashboard/{layout,page}.tsx • app/actions/tasks.ts</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  inngest/{client,functions}.ts • app/api/inngest/route.ts</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  next-auth.d.ts (Session type augment)</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">Wasp (~7 files, ~85 LOC of wiring):</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  main.wasp.ts • schema.prisma</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  src/auth/google.ts • src/pages/{Dashboard,auth}.tsx</span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  src/server/tasks.ts • src/server/jobs/digest.ts</span><br></div></code></pre></div></div>
<p>The difference here, and why it takes significantly less code in Wasp to achieve the same result, is that Wasp takes care of the boilerplate and glue code based on the simple definitions in the config file. The higher-level abstractions mean less boilerplate, which is a win for both humans and AI.</p>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="why-this-matters-more-in-2026">Why This Matters More in 2026<a href="https://wasp.sh/resources/2026/09/09/laravel-for-javascript-2026#why-this-matters-more-in-2026" class="hash-link" aria-label="Direct link to Why This Matters More in 2026" title="Direct link to Why This Matters More in 2026" translate="no">​</a></h2>
<p>The "less boilerplate" pitch isn't new, and a few years ago you could honestly argue it was a matter of taste. In 2026 it isn't, because the second consumer of your codebase is now AI.</p>
<p>AI tools have finite context windows, and performance degrades long before they fill up. They also re-read the codebase on every turn, so codebase size compounds across a project's lifetime. Every time you ask Cursor or Claude Code to make a change, it pays again for every file that exists. Less framework code in your repo means more room in the working memory for your business logic, which is the only code that's actually unique to your app.</p>
<p>Quoting <a class="" href="https://wasp.sh/blog/2026/03/26/nextjs-vs-wasp-40-percent-less-tokens-same-app">our Wasp vs Next.js benchmark post</a>: <em>"tools that make coding easier for humans make it easier for AI, too."</em> The takeaway: when you're picking a stack today, "context efficiency" is a new evaluation metric to add alongside DX, performance, and ecosystem. A framework that lets you describe a feature in 10 lines instead of 100 isn't just nicer to type, it's cheaper and faster to evolve.</p>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="adonisjs-is-the-better-fit-if">AdonisJS Is the Better Fit If...<a href="https://wasp.sh/resources/2026/09/09/laravel-for-javascript-2026#adonisjs-is-the-better-fit-if" class="hash-link" aria-label="Direct link to AdonisJS Is the Better Fit If..." title="Direct link to AdonisJS Is the Better Fit If..." translate="no">​</a></h2>
<p>We genuinely like AdonisJS, and there are real cases where we'd recommend it over Wasp without hesitation.</p>
<ul>
<li class=""><strong>You're a Laravel developer migrating to TypeScript and you want muscle-memory parity.</strong> Service container, providers, Lucid, ace commands, Tinker-equivalent REPL: AdonisJS is the closest 1:1 mapping of Laravel idioms in TypeScript. Wasp is not trying to be that.</li>
<li class=""><strong>You need Vue (or server-rendered templates) on the frontend.</strong> AdonisJS officially supports both via Inertia and first-party Edge templates. Wasp is React-only.</li>
<li class=""><strong>You prefer ActiveRecord-style models with logic on the model.</strong> This is a real philosophical fork, not a Wasp gap. Lucid (and Eloquent) encourages logic on the model; Prisma takes the opposite stance, treating the model as data-access only with business logic living in services. Both philosophies have credible defenders. If your instinct is logic-on-the-model, Lucid will feel right and Prisma will feel restrictive; pick AdonisJS.</li>
</ul>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="frequently-asked-questions">Frequently Asked Questions<a href="https://wasp.sh/resources/2026/09/09/laravel-for-javascript-2026#frequently-asked-questions" class="hash-link" aria-label="Direct link to Frequently Asked Questions" title="Direct link to Frequently Asked Questions" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="is-there-really-a-laravel-for-javascript">Is there really a "Laravel for JavaScript"?<a href="https://wasp.sh/resources/2026/09/09/laravel-for-javascript-2026#is-there-really-a-laravel-for-javascript" class="hash-link" aria-label="Direct link to Is there really a &quot;Laravel for JavaScript&quot;?" title="Direct link to Is there really a &quot;Laravel for JavaScript&quot;?" translate="no">​</a></h3>
<p>Not as a single framework, because "Laravel for JS" is really two questions. If you mean <em>Laravel idioms in TypeScript</em> (service container, providers, ActiveRecord-style models, ace commands), <strong>AdonisJS</strong> is the closest 1:1 port. If you mean <em>Laravel's batteries-included DX</em>, where the framework owns the boilerplate, <strong>Wasp</strong> is built around that same goal on a modern React + Node.js + Prisma stack. Pick based on which half of the question you were actually asking.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="is-adonisjs-really-laravel-for-node">Is AdonisJS really "Laravel for Node"?<a href="https://wasp.sh/resources/2026/09/09/laravel-for-javascript-2026#is-adonisjs-really-laravel-for-node" class="hash-link" aria-label="Direct link to Is AdonisJS really &quot;Laravel for Node&quot;?" title="Direct link to Is AdonisJS really &quot;Laravel for Node&quot;?" translate="no">​</a></h3>
<p>Yes, more directly than any other JS framework. AdonisJS ports the core Laravel idioms to TypeScript: a service container with providers, an ActiveRecord-style ORM (Lucid), social auth via Ally, ace commands, and Edge templates. If you want muscle-memory parity with Laravel in TypeScript, AdonisJS is the closest 1:1 mapping.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="whats-the-difference-between-adonisjs-and-wasp">What's the difference between AdonisJS and Wasp?<a href="https://wasp.sh/resources/2026/09/09/laravel-for-javascript-2026#whats-the-difference-between-adonisjs-and-wasp" class="hash-link" aria-label="Direct link to What's the difference between AdonisJS and Wasp?" title="Direct link to What's the difference between AdonisJS and Wasp?" translate="no">​</a></h3>
<p><strong>AdonisJS</strong> is a runtime framework that ports Laravel idioms (service container, providers, Lucid ORM) into TypeScript. <strong>Wasp</strong> is a compiler-driven framework where a single <code>main.wasp.ts</code> file declares your routes, pages, auth, database entities, and jobs, and the compiler generates a typed React + Node.js + Prisma app from it. AdonisJS is backend-first with the frontend wired up per page; Wasp treats client, server, and database as peers in one spec.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="does-wasp-use-activerecord-like-lucid">Does Wasp use ActiveRecord like Lucid?<a href="https://wasp.sh/resources/2026/09/09/laravel-for-javascript-2026#does-wasp-use-activerecord-like-lucid" class="hash-link" aria-label="Direct link to Does Wasp use ActiveRecord like Lucid?" title="Direct link to Does Wasp use ActiveRecord like Lucid?" translate="no">​</a></h3>
<p>No. Wasp uses Prisma, which is a data-mapper / data-access ORM, not ActiveRecord. Lucid (and Eloquent in Laravel) put query and relationship logic on the model itself; Prisma keeps the model dumb and pushes business logic into services or operations. Both philosophies have serious defenders. If your instinct is logic-on-the-model, Lucid will feel right.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="what-about-nestjs-isnt-that-the-js-laravel">What about NestJS, isn't that the JS Laravel?<a href="https://wasp.sh/resources/2026/09/09/laravel-for-javascript-2026#what-about-nestjs-isnt-that-the-js-laravel" class="hash-link" aria-label="Direct link to What about NestJS, isn't that the JS Laravel?" title="Direct link to What about NestJS, isn't that the JS Laravel?" translate="no">​</a></h3>
<p>NestJS is closer to Spring Boot than Laravel. It optimizes for enterprise-style dependency injection, decorators, and modular architecture. Laravel and Wasp optimize for productivity and batteries-included DX. Different goals, which is why we left NestJS out of the main three-way comparison.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="what-about-the-t3-stack">What about the t3-stack?<a href="https://wasp.sh/resources/2026/09/09/laravel-for-javascript-2026#what-about-the-t3-stack" class="hash-link" aria-label="Direct link to What about the t3-stack?" title="Direct link to What about the t3-stack?" translate="no">​</a></h3>
<p>The t3-stack isn't a framework, it's a scaffolder (<code>create-t3-app</code>) that wires together Next.js, tRPC, Prisma, NextAuth, Tailwind, and TypeScript into a starting project. After it generates the app, you own and maintain every piece independently; nothing keeps the integration coherent over time. That's the opposite of what Laravel and Wasp do, and it's why t3 isn't a fourth lane in this post: it answers the "give me curated defaults" question, not the "give me a framework that owns the boring parts" question. Honest credit: it's a great starting point if assembly is what you want.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="does-using-wasp-actually-save-money-on-ai-coding-tools">Does using Wasp actually save money on AI coding tools?<a href="https://wasp.sh/resources/2026/09/09/laravel-for-javascript-2026#does-using-wasp-actually-save-money-on-ai-coding-tools" class="hash-link" aria-label="Direct link to Does using Wasp actually save money on AI coding tools?" title="Direct link to Does using Wasp actually save money on AI coding tools?" translate="no">​</a></h3>
<p>Yes, measurably. We ran the same SaaS-feature prompt through Claude Code on identical Wasp and Next.js apps. Wasp used <strong>38% fewer tokens</strong> and cost <strong>44% less</strong> ($2.87 vs $5.17), with roughly 70% higher token efficiency. The reason is structural: AI tools re-read the codebase on every turn, so a smaller codebase compounds across a project's lifetime. (<a class="" href="https://wasp.sh/blog/2026/03/26/nextjs-vs-wasp-40-percent-less-tokens-same-app">Full benchmark.</a>)</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="im-coming-from-laravel-which-framework-should-i-try-first">I'm coming from Laravel, which framework should I try first?<a href="https://wasp.sh/resources/2026/09/09/laravel-for-javascript-2026#im-coming-from-laravel-which-framework-should-i-try-first" class="hash-link" aria-label="Direct link to I'm coming from Laravel, which framework should I try first?" title="Direct link to I'm coming from Laravel, which framework should I try first?" translate="no">​</a></h3>
<p>Try <strong>AdonisJS</strong> first if you want your Laravel muscle memory to transfer (service container, Eloquent-style models, ace commands, Edge or Inertia for views). Try <strong>Wasp</strong> first if what you loved about Laravel was the productivity feeling (the framework owning the boilerplate) and you're open to a different mental model (a declarative config file, Prisma instead of ActiveRecord, React on the front).</p>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="bottom-line">Bottom Line<a href="https://wasp.sh/resources/2026/09/09/laravel-for-javascript-2026#bottom-line" class="hash-link" aria-label="Direct link to Bottom Line" title="Direct link to Bottom Line" translate="no">​</a></h2>
<p>There's no single "Laravel for JavaScript"; the right answer depends on which part of Laravel you were actually asking about.</p>
<table><thead><tr><th>If you...</th><th>Choose</th><th>Why</th></tr></thead><tbody><tr><td>Want Laravel idioms ported to TypeScript</td><td><strong>AdonisJS</strong></td><td>Direct lineage: service container, Lucid, Ally</td></tr><tr><td>Need maximum frontend flexibility (Vue, Edge templates)</td><td><strong>AdonisJS</strong></td><td>First-class Vue support via Inertia + server-rendered templates</td></tr><tr><td>Want Laravel's productivity feeling on a modern, AI-coding-friendly stack</td><td><strong>Wasp</strong></td><td>Declarative config file drastically improves AI context efficiency, framework-owned client, automatic type safety, measurably less boilerplate</td></tr><tr><td>Have a heavily React-focused team and don't mind assembling</td><td><strong>Next.js</strong></td><td>Largest ecosystem, no opinions, hire pool unmatched</td></tr></tbody></table>
<p>Picking AdonisJS makes a lot of sense if you want the literal Laravel feel. Pick Wasp if you want to bet on DX and where full-stack frameworks are heading.</p>
<p>If you do decide to try Wasp, a great path is the <a href="https://opensaas.sh/" target="_blank" rel="noopener noreferrer" class="">Open SaaS</a> template: a free, open-source SaaS starter (14k+ GitHub stars) built on Wasp with auth, payments, admin, and analytics already wired up. Or jump straight into the <a class="" href="https://wasp.sh/docs">Wasp docs</a> to start a fresh project.</p>
<p>Coming from Laravel and want to compare notes with people who've made the jump? Come hang out in the <a href="https://discord.gg/rzdnErX" target="_blank" rel="noopener noreferrer" class="">Wasp Discord</a>; we'd love to hear what you're building.</p>]]></content:encoded>
            <author>vince@wasp-lang.dev (Vince Canger)</author>
            <category>wasp</category>
            <category>laravel</category>
            <category>adonisjs</category>
            <category>nextjs</category>
            <category>comparison</category>
        </item>
        <item>
            <title><![CDATA[RedwoodJS Alternatives in 2026: CedarJS, RedwoodSDK, or Wasp?]]></title>
            <link>https://wasp.sh/resources/2026/09/09/redwoodjs-alternatives-2026</link>
            <guid>https://wasp.sh/resources/2026/09/09/redwoodjs-alternatives-2026</guid>
            <pubDate>Wed, 09 Sep 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[RedwoodJS is winding down. We compare your three real alternatives (CedarJS, RedwoodSDK, and Wasp) and which one preserves the original philosophy.]]></description>
            <content:encoded><![CDATA[
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="tldr">TL;DR<a href="https://wasp.sh/resources/2026/09/09/redwoodjs-alternatives-2026#tldr" class="hash-link" aria-label="Direct link to TL;DR" title="Direct link to TL;DR" translate="no">​</a></h2>
<ul>
<li class="">
<p>The original <a href="https://docs.redwoodjs.com/" target="_blank" rel="noopener noreferrer" class="">RedwoodJS</a> framework is being wound down (now branded <strong>RedwoodGraphQL</strong>), and developers are looking for somewhere to migrate.</p>
</li>
<li class="">
<p><a href="https://cedarjs.com/" target="_blank" rel="noopener noreferrer" class=""><strong>CedarJS</strong></a> is the community fork that continues the original codebase. <a href="https://rwsdk.com/" target="_blank" rel="noopener noreferrer" class=""><strong>RedwoodSDK</strong></a> is a different framework from the same team: Cloudflare-only and built on React Server Components.</p>
</li>
<li class="">
<p><a class="" href="https://wasp.sh/"><strong>Wasp</strong></a> is the closest spiritual successor to original RedwoodJS for the JS/TS ecosystem: opinionated, batteries-included, React + Node.js + Prisma, deploy-anywhere.</p>
</li>
</ul>
<p>If you want <strong>minimum disruption</strong> to an existing RedwoodJS app, go with CedarJS.
If you want the <strong>original RedwoodJS philosophy on a modern, AI-friendly stack</strong>, go with Wasp.</p>
<!-- -->
<hr>
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="what-happened-to-redwoodjs">What Happened to RedwoodJS?<a href="https://wasp.sh/resources/2026/09/09/redwoodjs-alternatives-2026#what-happened-to-redwoodjs" class="hash-link" aria-label="Direct link to What Happened to RedwoodJS?" title="Direct link to What Happened to RedwoodJS?" translate="no">​</a></h2>
<p>The framework that pitched itself as "the full-stack framework for startups" has been wound down by its core team (<a href="https://community.redwoodjs.com/t/the-future-of-redwood-launches-today/7938" target="_blank" rel="noopener noreferrer" class="">announcement on the Redwood community forum, April 2025</a>), and the JavaScript framework landscape has shifted around it.</p>
<p>Here's the short version:</p>
<ol>
<li class="">The original RedwoodJS framework (React, GraphQL, Prisma, all wired together) was renamed to <strong>RedwoodGraphQL</strong> and put into maintenance mode. If you visit <a href="https://docs.redwoodjs.com/" target="_blank" rel="noopener noreferrer" class="">docs.redwoodjs.com</a> today, the docs site asks you to choose between RedwoodGraphQL and RedwoodSDK; that split is the official framing from the team.</li>
<li class="">The community then forked RedwoodGraphQL and continued active development under a new name: <a href="https://github.com/cedarjs/cedar" target="_blank" rel="noopener noreferrer" class=""><strong>CedarJS</strong></a>. It preserves the original APIs and conventions, with a documented <a href="https://github.com/cedarjs/cedar/blob/main/docs/docs/upgrade-guides/redwood-to-cedar.md" target="_blank" rel="noopener noreferrer" class="">Redwood-to-Cedar upgrade path</a>.</li>
<li class="">The original Redwood team's new direction is <a href="https://rwsdk.com/" target="_blank" rel="noopener noreferrer" class=""><strong>RedwoodSDK</strong></a>: a React Server Components framework <a href="https://developers.cloudflare.com/workers/framework-guides/web-apps/redwoodsdk/" target="_blank" rel="noopener noreferrer" class="">built specifically for Cloudflare Workers</a>. It shares the brand, but it's a different framework, not a continuation of the original.</li>
</ol>
<p>The result: if you Google "RedwoodJS" today, you'll find three different things wearing similar names, plus a lot of confused Reddit threads. This post is the cheat sheet we wish existed: what the three options actually are, how they compare, and which one preserves the spirit of original RedwoodJS for your next project.</p>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="your-three-migration-paths">Your Three Migration Paths<a href="https://wasp.sh/resources/2026/09/09/redwoodjs-alternatives-2026#your-three-migration-paths" class="hash-link" aria-label="Direct link to Your Three Migration Paths" title="Direct link to Your Three Migration Paths" translate="no">​</a></h2>
<p>There's no single "RedwoodJS replacement." There are three real options, and they're aimed at different developers.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="cedarjs">CedarJS<a href="https://wasp.sh/resources/2026/09/09/redwoodjs-alternatives-2026#cedarjs" class="hash-link" aria-label="Direct link to CedarJS" title="Direct link to CedarJS" translate="no">​</a></h3>
<p><a href="https://cedarjs.com/" target="_blank" rel="noopener noreferrer" class=""><strong>CedarJS</strong></a> is the community-maintained fork of RedwoodGraphQL (i.e., the original RedwoodJS codebase). Cells, Services, the GraphQL layer, and dbAuth all work the same way; the config file and CLI have been rebranded (<code>redwood.toml</code> → <code>cedar.toml</code>, <code>yarn rw</code> → <code>yarn cedar</code>), but the mental model is identical. Getting onto Cedar is a search-and-replace from <code>@redwoodjs</code> imports to <code>@cedarjs</code>, which lands you on the release line Cedar's own <a href="https://github.com/cedarjs/cedar/blob/main/docs/docs/upgrade-guides/redwood-to-cedar.md" target="_blank" rel="noopener noreferrer" class="">upgrade guide</a> describes as "the latest version of Cedar that's fully compatible with RedwoodJS": CedarJS v1.x.</p>
<p>That detail matters more than it first looks, because v1.x is the entry point, not the destination. Cedar has shipped steadily since forking in April 2025 and is on <strong>v6.x as of September 2026</strong>, so getting to the current release means climbing the version ladder (v1 → v2 → … → v6), each hop with its own upgrade guide and its own breaking changes. Cedar v6 alone asks you to move to flat ESLint config, Vitest 4, and MSW 2, and to swap custom Babel plugins for Vite plugin options. None of that is exotic, and this is still the least disruptive of the three paths, but "search-and-replace" describes the first hop rather than the whole trip.</p>
<p>The honest tradeoff: long-term resourcing is uncertain. Community continuations of large frameworks have a mixed track record: some thrive, some stall. CedarJS has momentum right now, but you're betting on a community to do what a funded core team previously did.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="redwoodsdk">RedwoodSDK<a href="https://wasp.sh/resources/2026/09/09/redwoodjs-alternatives-2026#redwoodsdk" class="hash-link" aria-label="Direct link to RedwoodSDK" title="Direct link to RedwoodSDK" translate="no">​</a></h3>
<p><a href="https://rwsdk.com/" target="_blank" rel="noopener noreferrer" class=""><strong>RedwoodSDK</strong></a> is a different framework from the original Redwood team. It's <a href="https://docs.rwsdk.com/core/react-server-components/" target="_blank" rel="noopener noreferrer" class="">built on React Server Components</a>, runs on Cloudflare Workers, and ships <a href="https://docs.rwsdk.com/core/queues/" target="_blank" rel="noopener noreferrer" class="">Cloudflare Queues for background jobs</a> plus a <a href="https://github.com/redwoodjs/passkey-addon" target="_blank" rel="noopener noreferrer" class="">first-party passkey auth addon</a>. It's actively developed and the team behind it is serious.</p>
<p>The catch: it's a new framework with a new mental model. If you liked RedwoodJS because of Cells, Services, and Prisma-as-the-source-of-truth, RedwoodSDK won't feel familiar. It's also Cloudflare-only; your hosting choice is made for you.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="wasp">Wasp<a href="https://wasp.sh/resources/2026/09/09/redwoodjs-alternatives-2026#wasp" class="hash-link" aria-label="Direct link to Wasp" title="Direct link to Wasp" translate="no">​</a></h3>
<p><a class="" href="https://wasp.sh/"><strong>Wasp</strong></a> is the closest spiritual successor to original RedwoodJS for the JS/TS ecosystem. It's a batteries-included full-stack framework built on React, Node.js, and Prisma, with a declarative config file that describes your entire app (routes, pages, auth, database, jobs) at a high level.</p>
<p>(Disclaimer: this is us!) We didn't build Wasp as a Redwood replacement, but if you valued the opinionated "framework, not library" philosophy that made original RedwoodJS distinct, Wasp lands closer to it than anything else in the JavaScript ecosystem right now. Same opinionated, generated-app model, but with type-safe RPC instead of GraphQL, and the added benefit of being able to deploy anywhere.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="head-to-head-comparison">Head-to-Head Comparison<a href="https://wasp.sh/resources/2026/09/09/redwoodjs-alternatives-2026#head-to-head-comparison" class="hash-link" aria-label="Direct link to Head-to-Head Comparison" title="Direct link to Head-to-Head Comparison" translate="no">​</a></h3>
<table><thead><tr><th>Feature</th><th>CedarJS</th><th>RedwoodSDK</th><th>Wasp</th></tr></thead><tbody><tr><td><strong>Status</strong></td><td>Community fork</td><td>Active, v1.x</td><td>Active beta, approaching 1.0</td></tr><tr><td><strong>Stack</strong></td><td>React + Node + Prisma + GraphQL</td><td>RSC + Cloudflare Workers</td><td>React + Node + Prisma</td></tr><tr><td><strong>Hosting</strong></td><td>Anywhere</td><td>Cloudflare only</td><td>Anywhere (one-command deploy to Railway, <a href="https://fly.io/" target="_blank" rel="noopener noreferrer" class="">Fly.io</a>)</td></tr><tr><td><strong>Auth</strong></td><td>dbAuth (inherited)</td><td>First-party passkey addon</td><td>Built-in declarative</td></tr><tr><td><strong>Background jobs</strong></td><td>Inherited from Redwood</td><td>Cloudflare Queues</td><td>Built-in (pg-boss)</td></tr><tr><td><strong>Type safety</strong></td><td>GraphQL-mediated</td><td>RSC-native</td><td>End-to-end automatic</td></tr><tr><td><strong>Mental model</strong></td><td>Original Redwood</td><td>Brand new</td><td>Config + generated app</td></tr><tr><td><strong>AI-coding fit</strong></td><td>Good (strong conventions)</td><td>Too new to assess</td><td>Excellent (config as map)</td></tr><tr><td><strong>Migration effort from RedwoodJS</strong></td><td>Lowest, but staged (v1.x → v6.x)</td><td>High</td><td>Moderate</td></tr></tbody></table>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="why-wasp-lands-closest-to-original-redwoodjs">Why Wasp Lands Closest to Original RedwoodJS<a href="https://wasp.sh/resources/2026/09/09/redwoodjs-alternatives-2026#why-wasp-lands-closest-to-original-redwoodjs" class="hash-link" aria-label="Direct link to Why Wasp Lands Closest to Original RedwoodJS" title="Direct link to Why Wasp Lands Closest to Original RedwoodJS" translate="no">​</a></h2>
<p>Here's the part where we make our case. RedwoodJS was distinctive because it took strong, opinionated bets when the rest of the JS ecosystem was still telling you to "pick your stack." Wasp makes a lot of the same bets, just without the GraphQL layer and with a much smaller surface area.</p>
<p>The concrete parallels:</p>
<ul>
<li class=""><strong>Prisma → Prisma.</strong> Both frameworks use Prisma as the database layer. Your <code>schema.prisma</code> is portable as-is. No rewrite, no translation.</li>
<li class=""><strong>Cells &amp; Services → Operations + type-safe RPC.</strong> The mental model is the same: declare server logic, call it from React. Wasp drops the GraphQL middle layer in favor of typed RPC, so you get end-to-end types without writing a single SDL file.</li>
<li class=""><strong>dbAuth → declarative auth.</strong> RedwoodJS made auth scaffolding feel like a first-class feature. Wasp does the same with even fewer lines: declare your auth methods in <code>main.wasp.ts</code> and the providers (email/password, Google, GitHub, etc.) wire themselves up.</li>
<li class=""><strong><code>redwood.toml</code> → <code>main.wasp.ts</code>.</strong> This is the philosophical core. Both frameworks treat config-as-architecture: a high-level file that describes your app, and the framework generates the plumbing. If this idea is what drew you to RedwoodJS, Wasp is the only other framework currently doubling down on it.</li>
<li class=""><strong>Built-in deploy.</strong> <code>wasp deploy</code> ships your app to <a href="https://fly.io/" target="_blank" rel="noopener noreferrer" class="">Fly.io</a>, Railway, or any VPS. No cloud lock-in, no platform-specific rewrites.</li>
<li class=""><strong>No GraphQL required.</strong> A lot of RedwoodJS users loved the framework but never loved maintaining the GraphQL layer for an app that didn't need it. Wasp uses type-safe RPC (with Postgres + Prisma underneath) instead of a GraphQL layer, so you skip the SDL files, resolvers, and Apollo wiring entirely.</li>
<li class=""><strong>AI-coding compatibility.</strong> This is where Wasp goes beyond what RedwoodJS offered. The <code>.wasp.ts</code> file gives Cursor, Claude Code, and other AI tools a single source of truth for your app's architecture: routes, pages, auth, and operations all declared together. RedwoodJS spreads the equivalent information across <code>Routes.tsx</code>, <code>redwood.toml</code>, <code>web/src/auth.ts</code>, the GraphQL handler, and the Prisma schema, so AI tools have to stitch the map together themselves.</li>
</ul>
<p>Concretely, here's what that single source of truth looks like (abridged from the <a class="" href="https://wasp.sh/docs/features/spec">Wasp Spec reference</a>):</p>
<div class="language-typescript codeBlockContainer_Q34C theme-code-block" style="--prism-color:#393A34;--prism-background-color:var(--wasp-code-bg)"><div class="codeBlockContent_ZoZC"><pre tabindex="0" class="prism-code language-typescript codeBlock_aRLL thin-scrollbar" style="color:#393A34;background-color:var(--wasp-code-bg)"><code class="codeBlockLines__LR8"><div class="token-line" style="color:#393A34"><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> app</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> action</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> job</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> page</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> query</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> route </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'@wasp/spec'</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> Dashboard </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'./src/pages/Dashboard'</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">with</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> type</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'ref'</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> getTasks </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'./src/queries'</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">with</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> type</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'ref'</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> createTask </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'./src/actions'</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">with</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> type</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'ref'</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">import</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> sendDailyDigest </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">from</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'./src/jobs/digest'</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">with</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> type</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'ref'</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain" style="display:inline-block"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token keyword" style="color:#00009f">export</span><span class="token plain"> </span><span class="token keyword" style="color:#00009f">default</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">app</span><span class="token punctuation" style="color:#393A34">(</span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  name</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'todoApp'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  title</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'ToDo App'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  wasp</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> version</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'^0.25.0'</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  auth</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    userEntity</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'User'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    methods</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      google</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      </span><span class="token comment" style="color:#999988;font-style:italic">// gitHub, email/password, etc...</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    onAuthFailedRedirectTo</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'/login'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    onAuthSucceededRedirectTo</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'/dashboard'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  spec</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">route</span><span class="token punctuation" style="color:#393A34">(</span><span class="token string" style="color:#e3116c">'DashboardRoute'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'/dashboard'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token function" style="color:#d73a49">page</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">Dashboard</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> authRequired</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token boolean" style="color:#36acaa">true</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">query</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">getTasks</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> entities</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token string" style="color:#e3116c">'Task'</span><span class="token punctuation" style="color:#393A34">]</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">action</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">createTask</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> entities</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token string" style="color:#e3116c">'Task'</span><span class="token punctuation" style="color:#393A34">]</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token function" style="color:#d73a49">job</span><span class="token punctuation" style="color:#393A34">(</span><span class="token plain">sendDailyDigest</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      executor</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'PgBoss'</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      schedule</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">{</span><span class="token plain"> cron</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token string" style="color:#e3116c">'0 7 * * *'</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">      entities</span><span class="token operator" style="color:#393A34">:</span><span class="token plain"> </span><span class="token punctuation" style="color:#393A34">[</span><span class="token string" style="color:#e3116c">'User'</span><span class="token punctuation" style="color:#393A34">]</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">    </span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain">  </span><span class="token punctuation" style="color:#393A34">]</span><span class="token punctuation" style="color:#393A34">,</span><span class="token plain"></span><br></div><div class="token-line" style="color:#393A34"><span class="token plain"></span><span class="token punctuation" style="color:#393A34">}</span><span class="token punctuation" style="color:#393A34">)</span><br></div></code></pre></div></div>
<p>Routes, auth, queries, actions, scheduled jobs: one file. That's what AI tools see when you point them at your project.</p>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="migration-what-transfers-what-doesnt">Migration: What Transfers, What Doesn't<a href="https://wasp.sh/resources/2026/09/09/redwoodjs-alternatives-2026#migration-what-transfers-what-doesnt" class="hash-link" aria-label="Direct link to Migration: What Transfers, What Doesn't" title="Direct link to Migration: What Transfers, What Doesn't" translate="no">​</a></h2>
<p>If you're considering moving from RedwoodJS to Wasp, here's the practical breakdown. We'll keep this short; a full migration guide is its own post.</p>
<table><thead><tr><th>Transfers cleanly</th><th>Needs rewriting</th></tr></thead><tbody><tr><td><code>schema.prisma</code></td><td>Cells → Operations + React Query</td></tr><tr><td>React components</td><td>Services → Operations</td></tr><tr><td>Auth providers (most)</td><td>GraphQL SDL → typed RPC functions</td></tr><tr><td>Business logic in services</td><td><code>redwood.toml</code> → <code>main.wasp.ts</code></td></tr><tr><td>TypeScript types</td><td>Generators / scaffolds</td></tr></tbody></table>
<p>The net effect: less boilerplate, simpler deploys, and a stack that AI coding tools handle dramatically better. Most teams report that the rewrite is smaller than they expected, because the GraphQL layer was where a lot of the maintenance burden lived.</p>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="frequently-asked-questions">Frequently Asked Questions<a href="https://wasp.sh/resources/2026/09/09/redwoodjs-alternatives-2026#frequently-asked-questions" class="hash-link" aria-label="Direct link to Frequently Asked Questions" title="Direct link to Frequently Asked Questions" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="is-redwoodjs-dead">Is RedwoodJS dead?<a href="https://wasp.sh/resources/2026/09/09/redwoodjs-alternatives-2026#is-redwoodjs-dead" class="hash-link" aria-label="Direct link to Is RedwoodJS dead?" title="Direct link to Is RedwoodJS dead?" translate="no">​</a></h3>
<p>The original RedwoodJS framework has been wound down by its core team. The codebase still exists and apps built on it still run, but active development has moved elsewhere. The community has continued the original project as CedarJS, while the original team has launched a new framework called RedwoodSDK that targets Cloudflare and React Server Components.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="whats-the-difference-between-redwoodjs-redwoodsdk-and-cedarjs">What's the difference between RedwoodJS, RedwoodSDK, and CedarJS?<a href="https://wasp.sh/resources/2026/09/09/redwoodjs-alternatives-2026#whats-the-difference-between-redwoodjs-redwoodsdk-and-cedarjs" class="hash-link" aria-label="Direct link to What's the difference between RedwoodJS, RedwoodSDK, and CedarJS?" title="Direct link to What's the difference between RedwoodJS, RedwoodSDK, and CedarJS?" translate="no">​</a></h3>
<p><strong>RedwoodJS</strong> is the original framework that has been wound down (now referred to as <strong>RedwoodGraphQL</strong>). <strong>CedarJS</strong> is a community fork that continues the original codebase with the same APIs, conventions, and philosophy. <strong>RedwoodSDK</strong> is a new framework from the original Redwood team; it shares the brand but is built on React Server Components and is Cloudflare-only, making it a different mental model entirely.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="should-i-migrate-to-cedarjs-or-switch-frameworks-entirely">Should I migrate to CedarJS or switch frameworks entirely?<a href="https://wasp.sh/resources/2026/09/09/redwoodjs-alternatives-2026#should-i-migrate-to-cedarjs-or-switch-frameworks-entirely" class="hash-link" aria-label="Direct link to Should I migrate to CedarJS or switch frameworks entirely?" title="Direct link to Should I migrate to CedarJS or switch frameworks entirely?" translate="no">​</a></h3>
<p>If your existing RedwoodJS app is in production and you want minimum disruption, <strong>CedarJS</strong> is the lowest-effort path. Getting on is mostly a search-and-replace from <code>@redwoodjs</code> imports to <code>@cedarjs</code>, which lands you on Cedar v1.x, the line Cedar documents as fully RedwoodJS-compatible. Reaching the current release (v6.x as of September 2026) then means working up through Cedar's per-major upgrade guides, each with its own breaking changes. It's still the least disruptive of the three options, just staged rather than a single hop. If you're starting a new project, or you want a more modern stack with better AI-coding compatibility and no GraphQL layer to maintain, switching to <strong>Wasp</strong> gives you the original RedwoodJS philosophy on a more modern foundation.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="can-i-reuse-my-prisma-schema-when-migrating-from-redwoodjs-to-wasp">Can I reuse my Prisma schema when migrating from RedwoodJS to Wasp?<a href="https://wasp.sh/resources/2026/09/09/redwoodjs-alternatives-2026#can-i-reuse-my-prisma-schema-when-migrating-from-redwoodjs-to-wasp" class="hash-link" aria-label="Direct link to Can I reuse my Prisma schema when migrating from RedwoodJS to Wasp?" title="Direct link to Can I reuse my Prisma schema when migrating from RedwoodJS to Wasp?" translate="no">​</a></h3>
<p>Yes. Both RedwoodJS and Wasp use Prisma for the database layer, so your <code>schema.prisma</code> file is portable. You'll need to rewrite Cells and Services as Wasp Operations and adjust your auth setup, but the database layer transfers cleanly with no rewrite required.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="does-wasp-support-graphql">Does Wasp support GraphQL?<a href="https://wasp.sh/resources/2026/09/09/redwoodjs-alternatives-2026#does-wasp-support-graphql" class="hash-link" aria-label="Direct link to Does Wasp support GraphQL?" title="Direct link to Does Wasp support GraphQL?" translate="no">​</a></h3>
<p>Wasp doesn't ship a GraphQL layer by default. Instead, it gives you type-safe RPC: you call server functions directly from your React components, and types flow end-to-end automatically. If you need GraphQL specifically, you can still add Apollo or another GraphQL server inside your Wasp app, but most teams find they don't need it.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="is-wasp-production-ready">Is Wasp production-ready?<a href="https://wasp.sh/resources/2026/09/09/redwoodjs-alternatives-2026#is-wasp-production-ready" class="hash-link" aria-label="Direct link to Is Wasp production-ready?" title="Direct link to Is Wasp production-ready?" translate="no">​</a></h3>
<p>Yes, with caveats. Wasp is currently in beta and approaching a 1.0 release, so API changes can occur between versions. That said, real companies and indie hackers are running production apps on Wasp today, and the underlying stack (React, Node.js, Prisma) is fully battle-tested. For SaaS products, MVPs, and internal tools, Wasp is production-viable.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="whats-the-closest-equivalent-to-redwood-cells-in-wasp">What's the closest equivalent to Redwood Cells in Wasp?<a href="https://wasp.sh/resources/2026/09/09/redwoodjs-alternatives-2026#whats-the-closest-equivalent-to-redwood-cells-in-wasp" class="hash-link" aria-label="Direct link to What's the closest equivalent to Redwood Cells in Wasp?" title="Direct link to What's the closest equivalent to Redwood Cells in Wasp?" translate="no">​</a></h3>
<p>Wasp Operations + React Query. RedwoodJS Cells bundle a GraphQL query, loading state, error state, and success render into one component. Wasp Operations are server functions you call directly from React with type-safe RPC, and React Query (used under the hood) handles the loading and error states. Same mental model, fewer layers.</p>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="bottom-line">Bottom Line<a href="https://wasp.sh/resources/2026/09/09/redwoodjs-alternatives-2026#bottom-line" class="hash-link" aria-label="Direct link to Bottom Line" title="Direct link to Bottom Line" translate="no">​</a></h2>
<p>There's no single "right" RedwoodJS replacement; the right choice depends on what you valued about RedwoodJS in the first place.</p>
<table><thead><tr><th>If you...</th><th>Choose</th><th>Why</th></tr></thead><tbody><tr><td>Want minimum disruption to your existing RedwoodJS app</td><td><strong>CedarJS</strong></td><td>Same APIs and conventions; staged upgrade path to current</td></tr><tr><td>Are starting fresh and committing to Cloudflare + RSC</td><td><strong>RedwoodSDK</strong></td><td>Modern RSC stack, tight Cloudflare integration</td></tr><tr><td>Want the original RedwoodJS philosophy on a modern, deploy-anywhere stack</td><td><strong>Wasp</strong></td><td>Opinionated, batteries-included, AI-coding-friendly</td></tr><tr><td>Want maximum flexibility and don't mind assembling</td><td><strong>Next.js + your stack</strong></td><td>Largest ecosystem, no opinions</td></tr></tbody></table>
<p>If RedwoodJS taught the JavaScript ecosystem anything, it was that strong opinions and a generated-app model can produce a developer experience that "pick your own stack" frameworks can't match. That idea didn't die with RedwoodJS; it just needs a new home.</p>
<p>If you want to try Wasp, the fastest path is the <a href="https://opensaas.sh/" target="_blank" rel="noopener noreferrer" class="">Open SaaS</a> template: a free, open-source SaaS starter (14k+ GitHub stars) built on Wasp with auth, payments, admin, and analytics already wired up. Or jump straight into the <a class="" href="https://wasp.sh/docs">Wasp docs</a> to start a fresh project.</p>
<p>Questions, war stories from your own RedwoodJS migration, or just want to compare notes? Come hang out in the <a href="https://discord.gg/rzdnErX" target="_blank" rel="noopener noreferrer" class="">Wasp Discord</a>; we'd love to hear what you're building.</p>]]></content:encoded>
            <author>vince@wasp-lang.dev (Vince Canger)</author>
            <category>wasp</category>
            <category>redwoodjs</category>
            <category>cedarjs</category>
            <category>frameworks</category>
            <category>comparison</category>
        </item>
        <item>
            <title><![CDATA[What Are the Best Full-stack Web App Frameworks in 2026?]]></title>
            <link>https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026</link>
            <guid>https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026</guid>
            <pubDate>Tue, 24 Feb 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[We compare the most popular full-stack frameworks in 2026 — Laravel, Ruby on Rails, Django, Next.js, and Wasp — across developer experience, ecosystem, AI-friendliness, deployment, and full-stack coverage.]]></description>
            <content:encoded><![CDATA[
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="tldr">TL;DR<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#tldr" class="hash-link" aria-label="Direct link to TL;DR" title="Direct link to TL;DR" translate="no">​</a></h2>
<ul>
<li class="">
<p><a href="https://laravel.com/" target="_blank" rel="noopener noreferrer" class="">Laravel</a>, <a href="https://rubyonrails.org/" target="_blank" rel="noopener noreferrer" class="">Rails</a>, and <a href="https://www.djangoproject.com/" target="_blank" rel="noopener noreferrer" class="">Django</a> remain the most battle-tested full-stack frameworks in 2026.</p>
</li>
<li class="">
<p><a href="https://nextjs.org/" target="_blank" rel="noopener noreferrer" class="">Next.js</a> dominates for React-first apps but requires significant assembly.</p>
</li>
<li class="">
<p><a href="https://wasp.sh/" target="_blank" rel="noopener noreferrer" class="">Wasp</a> brings the batteries-included experience of Laravel/Rails to the JS/TS ecosystem, with the strongest AI-coding compatibility of the five.</p>
</li>
</ul>
<p>If you want <strong>proven maturity</strong>, go Laravel for PHP or Django for Python.
If you want to <strong>ship fast in JavaScript with minimal boilerplate</strong>, go with Wasp.</p>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="what-were-comparing">What We're Comparing<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#what-were-comparing" class="hash-link" aria-label="Direct link to What We're Comparing" title="Direct link to What We're Comparing" translate="no">​</a></h2>
<p>In this guide, we compare the most popular full-stack frameworks in 2026: <strong>Laravel</strong>, <strong>Ruby on Rails</strong>, <strong>Django</strong>, and <strong>Next.js</strong>. We also include <strong>Wasp</strong>, the framework we're building. We think it's a compelling option in this space, and we wanted to put it side by side with the established players so you can judge for yourself.</p>
<p>We look at what each does well, where each falls short, and which one fits your use case, whether you're a solo indie hacker, a startup team, or an enterprise engineering org.</p>
<p>Beyond the usual criteria like developer experience and ecosystem size, we also evaluate how well each framework plays with AI coding tools like Cursor, Claude Code, Codex, Copilot, and OpenCode — because in 2026, that matters more than ever.</p>
<!-- -->
<hr>
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="what-makes-a-great-full-stack-framework-in-2026">What Makes a Great Full-Stack Framework in 2026?<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#what-makes-a-great-full-stack-framework-in-2026" class="hash-link" aria-label="Direct link to What Makes a Great Full-Stack Framework in 2026?" title="Direct link to What Makes a Great Full-Stack Framework in 2026?" translate="no">​</a></h2>
<p>We focused on five criteria when evaluating full-stack frameworks:</p>
<ol>
<li class=""><strong>Developer Experience (DX):</strong> How fast can you go from <code>init</code> to a deployed app? How much configuration and boilerplate do you (not) have to deal with?</li>
<li class=""><strong>Ecosystem &amp; Community:</strong> Are there libraries, plugins, and guides for when you get stuck? Is it being actively maintained?</li>
<li class=""><strong>AI-Friendliness:</strong> How well does the framework work with AI coding assistants? Can an LLM understand your project structure and generate correct code?</li>
<li class=""><strong>Deployment Ease:</strong> Can you deploy with a single command, or do you need to configure infrastructure manually?</li>
<li class=""><strong>Full-Stack Coverage:</strong> Does the framework cover the client, server, <em>and</em> database layer, and how much assembly is required?</li>
</ol>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="different-flavors-of-full-stack">Different Flavors of Full-Stack<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#different-flavors-of-full-stack" class="hash-link" aria-label="Direct link to Different Flavors of Full-Stack" title="Direct link to Different Flavors of Full-Stack" translate="no">​</a></h2>
<p>All five frameworks in this guide can be used for full-stack development, but they take different approaches:</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="backend-first-full-stack-laravel-rails-django">Backend-first full-stack (Laravel, Rails, Django)<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#backend-first-full-stack-laravel-rails-django" class="hash-link" aria-label="Direct link to Backend-first full-stack (Laravel, Rails, Django)" title="Direct link to Backend-first full-stack (Laravel, Rails, Django)" translate="no">​</a></h3>
<p>These are the original full-stack frameworks. They own the server and database layer with built-in ORMs, migrations, auth, background jobs, and more. Their frontend story varies, e.g. Laravel pairs with Inertia.js or Livewire, Rails has Hotwire/Turbo, and Django uses templates or a separate SPA. These are mature, battle-tested, and genuinely full-stack. If your definition of full-stack is "handles everything from HTTP request to database and back," these frameworks nailed it years ago.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="frontend-first-full-stack-nextjs">Frontend-first full-stack (Next.js)<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#frontend-first-full-stack-nextjs" class="hash-link" aria-label="Direct link to Frontend-first full-stack (Next.js)" title="Direct link to Frontend-first full-stack (Next.js)" translate="no">​</a></h3>
<p>Covers client-side rendering and server-side logic (API routes, server components), but the database layer is entirely Bring Your Own (BYO). You choose your ORM, your auth solution, your email provider, and you wire them together yourself.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="all-in-one-full-stack-wasp">All-in-one full-stack (Wasp)<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#all-in-one-full-stack-wasp" class="hash-link" aria-label="Direct link to All-in-one full-stack (Wasp)" title="Direct link to All-in-one full-stack (Wasp)" translate="no">​</a></h3>
<p>Wasp takes a different approach within the JavaScript ecosystem specifically. It uses a declarative configuration file that describes your routes, authentication, database models, server operations, and more in one place. The compiler then generates a React + Node.js + Prisma application. Unlike Laravel or Rails, Wasp removes the need to pick and assemble frontend solutions, and bundles everything within a single mental model. Wasp also brings the batteries-included philosophy of Laravel and Rails to the JS/TS ecosystem, where developers otherwise need to assemble everything from scratch.</p>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="laravel-php">Laravel (PHP)<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#laravel-php" class="hash-link" aria-label="Direct link to Laravel (PHP)" title="Direct link to Laravel (PHP)" translate="no">​</a></h2>
<p><strong>The battle-tested PHP powerhouse that keeps reinventing itself.</strong></p>
<p>Laravel has been the dominant PHP framework for over a decade, and it shows no signs of slowing down. Laravel has a long tradition of incremental, developer-friendly improvements. With over <a href="https://github.com/laravel/laravel" target="_blank" rel="noopener noreferrer" class=""><strong>80,000 GitHub stars</strong></a> and <a href="https://blog.jetbrains.com/phpstorm/2024/09/laravel-trends-2024-the-latest-market-insights/" target="_blank" rel="noopener noreferrer" class="">used by 61% of PHP developers</a>, Laravel's community is massive and active.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="key-features">Key Features<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#key-features" class="hash-link" aria-label="Direct link to Key Features" title="Direct link to Key Features" translate="no">​</a></h3>
<ul>
<li class=""><strong>Eloquent ORM</strong> — expressive, ActiveRecord-style database layer</li>
<li class=""><strong>New Starter Kits (React, Vue, Livewire)</strong> — built-in auth scaffolding for email with optional WorkOS AuthKit for social auth, passkeys, and SSO</li>
<li class=""><strong>Laravel Cloud, or Forge</strong> — fully-managed deployments with Laravel Cloud, or VPS server management with Forge</li>
<li class=""><strong>Inertia.js integration</strong> — use React or Vue as your frontend with server-driven routing</li>
<li class=""><strong>Queues, events, broadcasting</strong> — built-in job processing and real-time features</li>
<li class=""><strong>Laravel Herd</strong> — zero-config local development environment</li>
</ul>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="pros">Pros<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#pros" class="hash-link" aria-label="Direct link to Pros" title="Direct link to Pros" translate="no">​</a></h3>
<ul>
<li class="">Incredibly mature ecosystem with solutions for nearly every problem</li>
<li class="">Excellent documentation — often cited as the gold standard</li>
<li class="">Huge job market, especially for agencies and SaaS companies</li>
<li class="">First-party tools for deployment, billing (Cashier), search (Scout), and more</li>
<li class="">Active release cycle with yearly major versions</li>
</ul>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="cons">Cons<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#cons" class="hash-link" aria-label="Direct link to Cons" title="Direct link to Cons" translate="no">​</a></h3>
<ul>
<li class="">PHP — love it or hate it, many JS/Python developers won't consider it</li>
<li class="">Frontend story requires extra setup (Inertia.js, Livewire, or a separate SPA)</li>
<li class="">Performance requires tuning for high-concurrency applications</li>
</ul>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="best-for">Best For<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#best-for" class="hash-link" aria-label="Direct link to Best For" title="Direct link to Best For" translate="no">​</a></h3>
<p>Enterprise applications, SaaS products, agencies, and teams already invested in PHP. Laravel is the safest bet if you need a proven framework with an answer for everything.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="aivibe-coding-compatibility">AI/Vibe Coding Compatibility<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#aivibe-coding-compatibility" class="hash-link" aria-label="Direct link to AI/Vibe Coding Compatibility" title="Direct link to AI/Vibe Coding Compatibility" translate="no">​</a></h3>
<p><strong>Good.</strong> Laravel's consistent conventions and excellent documentation mean AI tools can generate reasonably accurate code. However, the PHP + JS split (if using Inertia or a React SPA) means the AI needs to understand two separate codebases. AI-coding tools work well with Laravel, but the full-stack context is split across languages.</p>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="ruby-on-rails">Ruby on Rails<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#ruby-on-rails" class="hash-link" aria-label="Direct link to Ruby on Rails" title="Direct link to Ruby on Rails" translate="no">​</a></h2>
<p><strong>The original "convention over configuration" framework, still going strong.</strong></p>
<p>Ruby on Rails practically invented modern web development conventions. <a href="https://rubyonrails.org/2024/12/13/Rails-Version-8-0-1-has-been-released" target="_blank" rel="noopener noreferrer" class="">Rails 8.0</a> (released late 2024) doubled down on simplicity with Kamal 2 for deployment, Thruster for HTTP/2, and the Solid trifecta (Solid Cable, Solid Cache, Solid Queue) — replacing Redis dependencies with database-backed alternatives. Rails has approximately <a href="https://github.com/rails/rails" target="_blank" rel="noopener noreferrer" class=""><strong>56,000+ GitHub stars</strong></a> and a loyal, experienced community.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="key-features-1">Key Features<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#key-features-1" class="hash-link" aria-label="Direct link to Key Features" title="Direct link to Key Features" translate="no">​</a></h3>
<ul>
<li class=""><strong>Active Record</strong> — the ORM that inspired every other ORM</li>
<li class=""><strong>Kamal 2</strong> — deploy anywhere with zero-downtime Docker deployments</li>
<li class=""><strong>Hotwire (Turbo + Stimulus)</strong> — modern frontend interactivity without heavy JS</li>
<li class=""><strong>Solid Cable/Cache/Queue</strong> — database-backed infrastructure, no Redis needed</li>
<li class=""><strong>Built-in authentication generator</strong> (new in Rails 8)</li>
<li class=""><strong>Action Mailer, Active Job, Active Storage</strong> — batteries included for email, jobs, and file uploads</li>
</ul>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="pros-1">Pros<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#pros-1" class="hash-link" aria-label="Direct link to Pros" title="Direct link to Pros" translate="no">​</a></h3>
<ul>
<li class="">Convention over configuration means less decision fatigue</li>
<li class="">Extremely productive for CRUD applications and MVPs</li>
<li class="">Mature ecosystem with gems for nearly everything</li>
<li class="">Rails 8's "no PaaS" philosophy makes self-hosting straightforward</li>
<li class="">Strong opinions lead to consistent, maintainable codebases</li>
</ul>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="cons-1">Cons<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#cons-1" class="hash-link" aria-label="Direct link to Cons" title="Direct link to Cons" translate="no">​</a></h3>
<ul>
<li class="">Ruby's job market has shrunk compared to JS, Python, and PHP. <a href="https://blog.jetbrains.com/research/2025/10/state-of-developer-ecosystem-2025/" target="_blank" rel="noopener noreferrer" class="">JetBrains' 2025 survey</a> classifies Ruby as a language in "long-term decline"</li>
<li class="">Ruby has no opt-in type system akin to TypeScript — that's freeing for some developers and frustrating for others</li>
<li class="">Performance can lag behind Node.js and Go for I/O-heavy workloads</li>
<li class="">Frontend story (Hotwire) is polarizing — great for some, frustrating for React/Vue developers</li>
<li class="">Smaller pool of new developers entering the ecosystem</li>
</ul>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="best-for-1">Best For<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#best-for-1" class="hash-link" aria-label="Direct link to Best For" title="Direct link to Best For" translate="no">​</a></h3>
<p>Startups that value speed-to-market, CRUD-heavy applications, and teams that appreciate strong conventions. Rails remains one of the fastest ways to go from idea to working product if you're comfortable with Ruby.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="aivibe-coding-compatibility-1">AI/Vibe Coding Compatibility<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#aivibe-coding-compatibility-1" class="hash-link" aria-label="Direct link to AI/Vibe Coding Compatibility" title="Direct link to AI/Vibe Coding Compatibility" translate="no">​</a></h3>
<p><strong>Good.</strong> Rails' strong conventions make it relatively predictable for AI tools. The "Rails way" means there's usually one correct approach, which helps LLMs generate accurate code. However, like Laravel, the backend (Ruby) and any modern frontend (React via Inertia or API mode) are separate contexts the AI must juggle.</p>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="django-python">Django (Python)<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#django-python" class="hash-link" aria-label="Direct link to Django (Python)" title="Direct link to Django (Python)" translate="no">​</a></h2>
<p><strong>Python's full-stack framework, now supercharged by the AI/ML ecosystem.</strong></p>
<p><a href="https://docs.djangoproject.com/en/5.2/releases/5.2/" target="_blank" rel="noopener noreferrer" class="">Django 5.2 LTS</a> (released April 2025) is the latest long-term support release, with security fixes guaranteed through April 2028. With roughly <a href="https://github.com/django/django" target="_blank" rel="noopener noreferrer" class=""><strong>82,000+ GitHub stars</strong></a>, Django has one of the largest open-source communities of any web framework. Its killer advantage in 2026? Python is the language of AI and data science, making Django a natural choice for teams that need web applications tightly integrated with ML pipelines.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="key-features-2">Key Features<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#key-features-2" class="hash-link" aria-label="Direct link to Key Features" title="Direct link to Key Features" translate="no">​</a></h3>
<ul>
<li class=""><strong>Django ORM</strong> — powerful, Pythonic database layer with migrations</li>
<li class=""><strong>Django Admin</strong> — automatic admin interface from your models</li>
<li class=""><strong>Django REST Framework (DRF)</strong> — the de facto standard for building APIs</li>
<li class=""><strong>Built-in auth, sessions, CSRF protection</strong> — security-first by default</li>
<li class=""><strong>Excellent integration with Python ML/AI libraries</strong> — NumPy, pandas, scikit-learn, PyTorch</li>
</ul>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="pros-2">Pros<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#pros-2" class="hash-link" aria-label="Direct link to Pros" title="Direct link to Pros" translate="no">​</a></h3>
<ul>
<li class="">Python, <a href="https://www.tiobe.com/tiobe-index/" target="_blank" rel="noopener noreferrer" class="">the most popular programming language according to the TIOBE Index</a></li>
<li class="">Unmatched for applications that combine web + data science/ML</li>
<li class="">Django Admin alone saves weeks of development time</li>
<li class=""><a href="https://www.djangoproject.com/start/overview/" target="_blank" rel="noopener noreferrer" class="">Battle-tested at scale</a> (Instagram, Pinterest, Mozilla)</li>
<li class=""><a href="https://docs.djangoproject.com/en/dev/internals/release-process/" target="_blank" rel="noopener noreferrer" class="">LTS releases</a> provide long-term stability — 3 years of security fixes per LTS version, the longest of any framework in this list</li>
<li class="">Massive community with extensive third-party packages</li>
</ul>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="cons-2">Cons<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#cons-2" class="hash-link" aria-label="Direct link to Cons" title="Direct link to Cons" translate="no">​</a></h3>
<ul>
<li class="">Frontend story is the weakest of the five. Django templates are server-rendered, and pairing with React requires a separate SPA + DRF API</li>
<li class="">Async support is improving but still not as natural as Node.js</li>
<li class="">"Monolithic" architecture can feel heavy for small projects</li>
<li class="">Deployment requires more setup than modern deployment platforms</li>
</ul>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="best-for-2">Best For<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#best-for-2" class="hash-link" aria-label="Direct link to Best For" title="Direct link to Best For" translate="no">​</a></h3>
<p>Data-driven applications, ML-integrated products, and teams already writing Python. If your backend does heavy data processing or integrates with AI models, Django is a natural fit. Also excellent for government, education, and enterprise contexts where Python is standard.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="aivibe-coding-compatibility-2">AI/Vibe Coding Compatibility<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#aivibe-coding-compatibility-2" class="hash-link" aria-label="Direct link to AI/Vibe Coding Compatibility" title="Direct link to AI/Vibe Coding Compatibility" translate="no">​</a></h3>
<p><strong>Very good for backend, weaker for full-stack.</strong> Python is the language AI tools understand best, so Django backend code gets excellent AI assistance. But the disconnect between Django's backend and a modern JS frontend means AI tools struggle with the full-stack picture. If you're building a Django + React app, the AI has to work across two very different codebases.</p>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="nextjs-react">Next.js (React)<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#nextjs-react" class="hash-link" aria-label="Direct link to Next.js (React)" title="Direct link to Next.js (React)" translate="no">​</a></h2>
<p><strong>The React meta-framework that dominates the JavaScript ecosystem.</strong></p>
<p>Next.js pioneered server-side rendering in the React ecosystem and continues to push boundaries with React Server Components, Server Actions, and a serverless-first deployment model via Vercel. <a href="https://nextjs.org/showcase" target="_blank" rel="noopener noreferrer" class="">Used by companies like Netflix, TikTok, and Notion</a>, it has over <a href="https://github.com/vercel/next.js" target="_blank" rel="noopener noreferrer" class=""><strong>130,000+ GitHub stars</strong></a>, making it one of the most popular open-source frameworks.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="key-features-3">Key Features<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#key-features-3" class="hash-link" aria-label="Direct link to Key Features" title="Direct link to Key Features" translate="no">​</a></h3>
<ul>
<li class=""><strong>App Router</strong> — React Server Components, layouts, and streaming</li>
<li class=""><strong>Server Actions</strong> — call server functions directly from client components</li>
<li class=""><strong>Turbopack</strong> — Rust-based bundler for faster builds</li>
<li class=""><strong>API Routes</strong> — build backend endpoints alongside your frontend</li>
<li class=""><strong>Vercel deployment</strong> — git push to production in seconds</li>
<li class=""><strong>Image optimization, fonts, metadata</strong> — built-in performance features</li>
</ul>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="pros-3">Pros<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#pros-3" class="hash-link" aria-label="Direct link to Pros" title="Direct link to Pros" translate="no">​</a></h3>
<ul>
<li class="">Largest ecosystem and community in the JavaScript full-stack space</li>
<li class="">Vercel provides best-in-class deployment experience</li>
<li class="">React skills are the most in-demand frontend skills in the job market</li>
<li class="">Server Components and Server Actions blur the client/server boundary</li>
<li class="">Excellent TypeScript support</li>
<li class=""><a href="https://nextjs.org/support-policy" target="_blank" rel="noopener noreferrer" class="">Formal LTS support policy</a> — each major version gets up to 2 years of maintenance</li>
<li class="">Massive library of examples, templates, and tutorials</li>
</ul>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="cons-3">Cons<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#cons-3" class="hash-link" aria-label="Direct link to Cons" title="Direct link to Cons" translate="no">​</a></h3>
<ul>
<li class="">No built-in ORM, database layer, or auth — you need Prisma/Drizzle for DB, NextAuth/Clerk for auth, Resend for email, etc.</li>
<li class="">Complexity has grown significantly — App Router, Server Components, caching strategies can be overwhelming</li>
<li class=""><a href="https://eduardoboucas.com/posts/2025-03-25-you-should-know-this-before-choosing-nextjs/" target="_blank" rel="noopener noreferrer" class="">Vercel platform coupling</a> — key features like ISR, image optimization, and serverless deployment work best (or only) on Vercel, with no official adapter system for other hosts</li>
<li class="">Serverless-first billing model can lead to unpredictable costs at scale</li>
<li class="">"Glue framework" problem — you spend significant time choosing and wiring together third-party solutions</li>
<li class="">Frequent breaking changes like the migration from Pages to App Router, which effectively required rewriting large portions of existing apps</li>
</ul>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="best-for-3">Best For<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#best-for-3" class="hash-link" aria-label="Direct link to Best For" title="Direct link to Best For" translate="no">​</a></h3>
<p>Teams building React-first applications who want maximum flexibility. Next.js is the right choice when you need a highly customized frontend with complex UI, and you're comfortable assembling or connecting your own backend stack. It's the only framework in this list that works equally well as a pure frontend layer.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="aivibe-coding-compatibility-3">AI/Vibe Coding Compatibility<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#aivibe-coding-compatibility-3" class="hash-link" aria-label="Direct link to AI/Vibe Coding Compatibility" title="Direct link to AI/Vibe Coding Compatibility" translate="no">​</a></h3>
<p><strong>Mixed.</strong> AI tools are excellent at generating React components and Next.js page structures. But because Next.js doesn't prescribe a database, auth, or backend architecture, the AI has to understand whatever custom stack you've assembled and spend a lot more time writing boilerplate and glue code. The complexity of the App Router, Server Components, and caching — plus breaking changes like the Pages to App Router migration — can also make it harder for AI to get things right.</p>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="wasp-react--nodejs--prisma">Wasp (React + Node.js + Prisma)<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#wasp-react--nodejs--prisma" class="hash-link" aria-label="Direct link to Wasp (React + Node.js + Prisma)" title="Direct link to Wasp (React + Node.js + Prisma)" translate="no">​</a></h2>
<p><strong>A declarative full-stack JS framework that gives React + Node.js + Prisma the batteries-included treatment.</strong></p>
<p>Wasp (Web Application Specification) takes a different approach within the JavaScript ecosystem. Instead of giving you building blocks and telling you to assemble them, Wasp uses a declarative configuration file that describes your entire application: routes, pages, authentication, database models, server operations, and background jobs. The Wasp compiler then generates a complete React + Node.js + Prisma application. With <a href="https://github.com/wasp-lang/wasp" target="_blank" rel="noopener noreferrer" class=""><strong>18,000+ GitHub stars</strong></a> and a growing community, Wasp is earning attention as the opinionated alternative to the "assemble it yourself" JS ecosystem.</p>
<p>This is our framework. We built Wasp because we felt the JS/TS ecosystem was missing the kind of batteries-included experience that Laravel, Rails, and Django developers have had for years. We think that earns it a spot in this comparison, but we'll let you be the judge.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="key-features-4">Key Features<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#key-features-4" class="hash-link" aria-label="Direct link to Key Features" title="Direct link to Key Features" translate="no">​</a></h3>
<ul>
<li class=""><strong>Declarative <code>.wasp</code> or <code>.wasp.ts</code> config</strong> — define your entire app — routes, auth, database, jobs — from a high level</li>
<li class=""><strong>Full-stack type safety</strong> — types flow from database to UI automatically</li>
<li class=""><strong>Type-safe RPC</strong> — call server functions from the client with automatic serialization and type checking, no API layer to write</li>
<li class=""><strong>Built-in auth</strong> — email/password, Google, GitHub, etc. with minimal config</li>
<li class=""><strong>Background jobs</strong> — declare async jobs in config, implement in Node.js</li>
<li class=""><strong>One-command deployment</strong> — <code>wasp deploy</code> to Railway, <a href="http://fly.io/" target="_blank" rel="noopener noreferrer" class="">Fly.io</a> or other providers</li>
<li class=""><strong><a href="https://opensaas.sh/" target="_blank" rel="noopener noreferrer" class="">Open SaaS</a></strong> — production-ready SaaS starter with <a href="https://github.com/wasp-lang/open-saas" target="_blank" rel="noopener noreferrer" class="">13,000+ GitHub stars</a></li>
</ul>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="pros-4">Pros<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#pros-4" class="hash-link" aria-label="Direct link to Pros" title="Direct link to Pros" translate="no">​</a></h3>
<ul>
<li class="">Dramatically less boilerplate than assembling Next.js + Prisma + NextAuth + etc. — which means a faster start and less maintenance later</li>
<li class="">Wasp's config acts as a high-level map of your app that both you and AI coding tools can read to quickly understand the full picture</li>
<li class="">Full-stack type safety without manual setup</li>
<li class="">Built on React, Node.js, and Prisma — widely adopted, marketable technologies</li>
<li class="">Simple by default, powerful when needed — common features work out of the box, but you can always drop into the underlying React, Node.js, and Prisma code for full flexibility</li>
<li class="">No deployment lock-in — build artifacts are standard Node.js and React, deployable anywhere</li>
<li class="">Helpful community with very active maintainers (according to the feedback of our users!)</li>
</ul>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="cons-4">Cons<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#cons-4" class="hash-link" aria-label="Direct link to Cons" title="Direct link to Cons" translate="no">​</a></h3>
<ul>
<li class="">Newer technology, which means faster changes and a still-growing ecosystem</li>
<li class="">Not yet battle-tested at enterprise scale</li>
<li class="">Currently only focused on the React + Node.js + Prisma stack</li>
<li class="">No serverless deployment support (yet)</li>
</ul>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="best-for-4">Best For<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#best-for-4" class="hash-link" aria-label="Direct link to Best For" title="Direct link to Best For" translate="no">​</a></h3>
<p>Solo developers, indie hackers, and startup teams who want a batteries-included full-stack experience in JavaScript/TypeScript. Also a strong fit for small-to-medium teams building SaaS products and enterprises building internal tools — anywhere speed-to-ship and low boilerplate matter more than maximum customization.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="aivibe-coding-compatibility-4">AI/Vibe Coding Compatibility<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#aivibe-coding-compatibility-4" class="hash-link" aria-label="Direct link to AI/Vibe Coding Compatibility" title="Direct link to AI/Vibe Coding Compatibility" translate="no">​</a></h3>
<p><strong>Excellent.</strong> The Wasp spec gives AI an instant, high-level understanding of your entire application, including its routes, authentication methods, server operations, and more. The well-defined stack and clear structure allow AI to focus on your app's business logic while Wasp handles the glue and boilerplate. And because complexity is hidden until you need it, there's simply less for AI to get wrong, making it easier to generate coherent code across the entire stack.</p>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="built-in-features-what-you-get-out-of-the-box">Built-in Features: What You Get Out of the Box<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#built-in-features-what-you-get-out-of-the-box" class="hash-link" aria-label="Direct link to Built-in Features: What You Get Out of the Box" title="Direct link to Built-in Features: What You Get Out of the Box" translate="no">​</a></h2>
<p>One of the biggest differences between frameworks is how much they give you versus how much you assemble yourself. Here's a detailed comparison of key features across all five frameworks.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="authentication">Authentication<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#authentication" class="hash-link" aria-label="Direct link to Authentication" title="Direct link to Authentication" translate="no">​</a></h3>
<table><thead><tr><th>Framework</th><th>Built-in Solution</th><th>Setup Effort</th></tr></thead><tbody><tr><td><strong>Wasp</strong></td><td>Declarative auth in config — ~10 lines for email + social auth</td><td>Minimal — declare it, done</td></tr><tr><td><strong>Laravel</strong></td><td>New starter kits with email auth and optional WorkOS AuthKit for social auth, passkeys, SSO</td><td>Low — one CLI command scaffolds views, controllers, routes</td></tr><tr><td><strong>Rails</strong></td><td>Built-in auth generator (Rails 8+). <code>rails generate authentication</code></td><td>Low — generates migration, model, controller, views</td></tr><tr><td><strong>Django</strong></td><td><code>django.contrib.auth</code> built into every project. Login/logout views, permissions, groups</td><td>Low — included by default, add URLs and templates</td></tr><tr><td><strong>Next.js</strong></td><td>None built-in. Use NextAuth.js/Auth.js (~50-100 lines config + route handler + middleware + provider setup) or Clerk (hosted, paid)</td><td>Moderate-High — install package, configure providers, add middleware, handle sessions</td></tr></tbody></table>
<p><strong>Where the established frameworks win:</strong> Laravel, Rails, and Django have had over a decade to refine their auth systems. They handle edge cases (password resets, email verification, rate limiting, 2FA) that newer solutions are still maturing on. Django's permission system and Laravel's team management are particularly sophisticated. That said, Wasp stands out for how little code is needed to get auth working: a few lines of config vs. generated scaffolding in the other frameworks.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="background-jobs--async-tasks">Background Jobs / Async Tasks<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#background-jobs--async-tasks" class="hash-link" aria-label="Direct link to Background Jobs / Async Tasks" title="Direct link to Background Jobs / Async Tasks" translate="no">​</a></h3>
<table><thead><tr><th>Framework</th><th>Built-in Solution</th><th>External Dependencies</th></tr></thead><tbody><tr><td><strong>Laravel</strong></td><td>Laravel Queues — first-party, supports Redis, SQS, database drivers. Horizon for monitoring</td><td>None required (database driver works out of the box)</td></tr><tr><td><strong>Rails</strong></td><td>Active Job — built-in abstraction. Solid Queue (Rails 8) eliminates Redis. Sidekiq for heavy workloads</td><td>None with Solid Queue; Sidekiq needs Redis</td></tr><tr><td><strong>Django</strong></td><td>None built-in. Celery is the de facto standard (~50-100 lines setup, needs broker like Redis/RabbitMQ)</td><td>Celery + message broker</td></tr><tr><td><strong>Wasp</strong></td><td>Declare <code>job</code> in <code>.wasp</code> config (~5 lines), implement handler in Node.js</td><td>None — uses pg-boss under-the-hood (PostgreSQL-backed)</td></tr><tr><td><strong>Next.js</strong></td><td>None built-in. Need Inngest, Trigger.dev, or BullMQ + separate worker process</td><td>Third-party service or self-hosted worker</td></tr></tbody></table>
<p><strong>Where Laravel, Rails, and Wasp dominate:</strong> Laravel Queues and Rails' Active Job / Solid Queue are the gold standard for background processing. They support job chaining, rate limiting, retry logic, priority queues, and monitoring dashboards (Horizon, Solid Queue's admin). Wasp's job system is simpler to declare but less feature-rich for complex workflows.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="routing">Routing<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#routing" class="hash-link" aria-label="Direct link to Routing" title="Direct link to Routing" translate="no">​</a></h3>
<table><thead><tr><th>Framework</th><th>Approach</th></tr></thead><tbody><tr><td><strong>Next.js</strong></td><td>File-based routing — create a file at <code>app/dashboard/page.tsx</code> and the route exists. Intuitive but can get messy with complex layouts</td></tr><tr><td><strong>Laravel</strong></td><td><code>routes/web.php</code> — expressive, resourceful routing. <code>Route::resource('photos', PhotoController::class)</code> gives you 7 CRUD routes in one line</td></tr><tr><td><strong>Rails</strong></td><td><code>config/routes.rb</code> — similar to Laravel. <code>resources :photos</code> generates RESTful routes. Mature, powerful DSL</td></tr><tr><td><strong>Django</strong></td><td><code>urlpatterns</code> in <code>urls.py</code> — explicit URL-to-view mapping. Flexible but more verbose than Rails/Laravel</td></tr><tr><td><strong>Wasp</strong></td><td>Declare <code>route</code> + <code>page</code> in <code>.wasp</code> config — routes are paired with pages and get type-safe linking. Simpler but less flexible than Rails/Laravel</td></tr></tbody></table>
<p><strong>Honest take:</strong> Routing is largely a solved problem. Rails and Laravel have the most powerful routing DSLs. Next.js file-based routing is the most intuitive for simple apps. Wasp's routing is the most concise but also the least flexible for complex URL patterns.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="full-stack-type-safety">Full-Stack Type Safety<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#full-stack-type-safety" class="hash-link" aria-label="Direct link to Full-Stack Type Safety" title="Direct link to Full-Stack Type Safety" translate="no">​</a></h3>
<table><thead><tr><th>Framework</th><th>Type Safety Story</th></tr></thead><tbody><tr><td><strong>Wasp</strong></td><td>Automatic — types flow from Prisma schema through server operations to React components. No manual setup needed</td></tr><tr><td><strong>Next.js</strong></td><td>Possible with tRPC or Server Actions, but requires manual configuration. Server Actions provide some type flow but aren't end-to-end</td></tr><tr><td><strong>Laravel</strong></td><td>Limited — PHP has types, but no automatic flow to JS frontend. Inertia.js provides some type sharing with TypeScript</td></tr><tr><td><strong>Rails</strong></td><td>Minimal — Ruby is dynamically typed. Sorbet exists but isn't standard</td></tr><tr><td><strong>Django</strong></td><td>Limited — Python has type hints, but no automatic flow to JS frontend</td></tr></tbody></table>
<p><strong>Wasp's genuine advantage:</strong> This is one area where Wasp clearly leads. Having types flow automatically from your database schema to your UI components, with zero configuration, eliminates an entire class of bugs. In other frameworks, achieving this requires significant setup (tRPC in Next.js) or isn't practically possible (Rails, Django).</p>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="head-to-head-comparison">Head-to-Head Comparison<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#head-to-head-comparison" class="hash-link" aria-label="Direct link to Head-to-Head Comparison" title="Direct link to Head-to-Head Comparison" translate="no">​</a></h2>
<table><thead><tr><th>Feature</th><th>Laravel</th><th>Ruby on Rails</th><th>Django</th><th>Next.js</th><th>Wasp</th></tr></thead><tbody><tr><td><strong>Language</strong></td><td>PHP</td><td>Ruby</td><td>Python</td><td>JavaScript/TypeScript</td><td>JavaScript/TypeScript</td></tr><tr><td><strong>GitHub Stars</strong></td><td>83K+</td><td>56K+</td><td>82K+</td><td>130K+</td><td>18K+</td></tr><tr><td><strong>ORM</strong></td><td>Eloquent</td><td>Active Record</td><td>Django ORM</td><td>BYO (Prisma/Drizzle)</td><td>Prisma (integrated)</td></tr><tr><td><strong>Auth</strong></td><td>Starter kits + WorkOS AuthKit integration</td><td>Generator (Rails 8)</td><td>django.contrib.auth</td><td>BYO (NextAuth/Clerk)</td><td>Declarative config</td></tr><tr><td><strong>Background Jobs</strong></td><td>Queues + Horizon</td><td>Active Job + Solid Queue</td><td>(Celery)</td><td>BYO (Inngest/Trigger.dev)</td><td>Declarative config</td></tr><tr><td><strong>Modern React Frontend</strong></td><td>Via Inertia.js</td><td>Via Hotwire/API</td><td>Via separate SPA</td><td>Native React</td><td>Native React</td></tr><tr><td><strong>Full-Stack Type Safety</strong></td><td>Limited</td><td>Minimal</td><td>Limited</td><td>Manual (tRPC)</td><td>Automatic</td></tr><tr><td><strong>Easy Deployment</strong></td><td>Forge/Vapor</td><td>Kamal 2</td><td>Manual/PaaS</td><td>Vercel (one-click)</td><td>CLI deploy to Railway, Fly.io, or any VPS</td></tr><tr><td><strong>AI-Friendliness</strong></td><td>⭐⭐⭐⭐</td><td>⭐⭐⭐⭐</td><td>⭐⭐⭐⭐</td><td>⭐⭐⭐</td><td>⭐⭐⭐⭐⭐</td></tr><tr><td><strong>Learning Curve</strong></td><td>Moderate</td><td>Moderate</td><td>Moderate</td><td>Steep (App Router)</td><td>Low-Moderate</td></tr><tr><td><strong>Job Market</strong></td><td>Large (PHP)</td><td>Shrinking</td><td>Large (Python)</td><td>Very Large (React)</td><td>Indirectly Very Large (Wasp is React/Node.js/Prisma)</td></tr><tr><td><strong>Maturity / Enterprise Readiness</strong></td><td>⭐⭐⭐⭐⭐</td><td>⭐⭐⭐⭐⭐</td><td>⭐⭐⭐⭐⭐</td><td>⭐⭐⭐⭐</td><td>⭐⭐⭐</td></tr></tbody></table>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="frequently-asked-questions">Frequently Asked Questions<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#frequently-asked-questions" class="hash-link" aria-label="Direct link to Frequently Asked Questions" title="Direct link to Frequently Asked Questions" translate="no">​</a></h2>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="when-should-i-choose-laravel-vs-nextjs-vs-wasp">When should I choose Laravel vs Next.js vs Wasp?<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#when-should-i-choose-laravel-vs-nextjs-vs-wasp" class="hash-link" aria-label="Direct link to When should I choose Laravel vs Next.js vs Wasp?" title="Direct link to When should I choose Laravel vs Next.js vs Wasp?" translate="no">​</a></h3>
<p><strong>Choose Laravel</strong> if you or your team knows PHP, you need a battle-tested solution for a complex business application, and you want a massive ecosystem with answers for every problem. <strong>Choose Next.js</strong> if you're designing a marketing page and SEO is very important, or if you need a highly custom React frontend with maximum flexibility and you're comfortable assembling your own backend stack. <strong>Choose Wasp</strong> if you want a batteries-included JS/TS full-stack experience without the assembly tax for building and shipping fast.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="whats-the-best-framework-for-solo-developers">What's the best framework for solo developers?<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#whats-the-best-framework-for-solo-developers" class="hash-link" aria-label="Direct link to What's the best framework for solo developers?" title="Direct link to What's the best framework for solo developers?" translate="no">​</a></h3>
<p>It depends on your language. <strong>Wasp</strong> is excellent for JS/TS solo developers. The declarative config eliminates decision fatigue and AI tools work particularly well with it. <strong>Rails</strong> has been the solo developer's best friend for two decades and is still incredibly productive. <strong>Laravel</strong> is similarly productive if you know PHP. The common thread: pick a framework with strong opinions so you spend time building, not configuring.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="which-framework-is-best-for-vibe-coding--ai-assisted-development">Which framework is best for vibe coding / AI-assisted development?<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#which-framework-is-best-for-vibe-coding--ai-assisted-development" class="hash-link" aria-label="Direct link to Which framework is best for vibe coding / AI-assisted development?" title="Direct link to Which framework is best for vibe coding / AI-assisted development?" translate="no">​</a></h3>
<p><strong>Wasp's</strong> configuration makes it the best choice as it gives AI a boilerplate-free, high-level understanding of the entire app, and allows it to focus on building your app's business logic while Wasp handles the glue. But Django also performs well because Python is the language AI tools understand most deeply, and Laravel/Rails benefit from their strong conventions that reduce ambiguity.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="is-wasp-production-ready">Is Wasp production-ready?<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#is-wasp-production-ready" class="hash-link" aria-label="Direct link to Is Wasp production-ready?" title="Direct link to Is Wasp production-ready?" translate="no">​</a></h3>
<p>Yes, with caveats. Wasp is rapidly approaching a 1.0 release (currently in beta), which means API changes can occur between versions. However, real companies and indie hackers are running production applications built with Wasp. For enterprise-scale applications with complex requirements, you may want to wait for 1.0 or choose a more established framework. For startups, MVPs, and SaaS products, Wasp is production-viable.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="whats-the-best-framework-for-a-startup-mvp">What's the best framework for a startup MVP?<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#whats-the-best-framework-for-a-startup-mvp" class="hash-link" aria-label="Direct link to What's the best framework for a startup MVP?" title="Direct link to What's the best framework for a startup MVP?" translate="no">​</a></h3>
<p>For a <strong>JavaScript/TypeScript</strong> startup: <strong>Wasp</strong> gets you to a deployed MVP fast, especially with the Open SaaS template. For a <strong>Python</strong> team: <strong>Django</strong> with Django REST Framework. For a <strong>PHP</strong> team: <strong>Laravel</strong>. For speed-to-market in Ruby: <strong>Rails</strong>. The common thread is choosing a framework that makes decisions for you so you can focus on your product.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="which-framework-has-the-best-job-market">Which framework has the best job market?<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#which-framework-has-the-best-job-market" class="hash-link" aria-label="Direct link to Which framework has the best job market?" title="Direct link to Which framework has the best job market?" translate="no">​</a></h3>
<p><strong>Next.js / React</strong> dominates the JavaScript job market. <strong>Django / Python</strong> leads in data science, AI/ML, and many enterprise contexts. <strong>Laravel / PHP</strong> remains strong for agencies, e-commerce, and WordPress-adjacent work. <strong>Rails</strong> has a loyal but shrinking job market. <strong>Wasp</strong> is too new for a meaningful job market of its own, but Wasp skills are really React + Node.js + Prisma skills — all highly marketable individually.</p>
<h3 class="anchor anchorTargetStickyNavbar_TPLw" id="can-i-use-nextjs-as-a-true-full-stack-framework">Can I use Next.js as a true full-stack framework?<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#can-i-use-nextjs-as-a-true-full-stack-framework" class="hash-link" aria-label="Direct link to Can I use Next.js as a true full-stack framework?" title="Direct link to Can I use Next.js as a true full-stack framework?" translate="no">​</a></h3>
<p>You can, but it requires significant assembly. Next.js provides the client and server layers, but you'll need to add your own ORM, authentication, email service, background jobs, and more. This gives you maximum flexibility but also maximum setup time. If you want a batteries-included JavaScript full-stack experience, Wasp is a better fit. If you want a customizable React-first framework and don't mind the assembly, Next.js remains the industry standard.</p>
<hr>
<h2 class="anchor anchorTargetStickyNavbar_TPLw" id="conclusion-which-framework-should-you-choose">Conclusion: Which Framework Should You Choose?<a href="https://wasp.sh/resources/2026/02/24/best-frameworks-web-dev-2026#conclusion-which-framework-should-you-choose" class="hash-link" aria-label="Direct link to Conclusion: Which Framework Should You Choose?" title="Direct link to Conclusion: Which Framework Should You Choose?" translate="no">​</a></h2>
<p>There's no single "best" framework but there is a best framework <em>for you</em>:</p>
<table><thead><tr><th>If you are...</th><th>Choose...</th><th>Why</th></tr></thead><tbody><tr><td>An enterprise team with complex requirements</td><td><strong>Laravel</strong> or <strong>Django</strong></td><td>Battle-tested, massive ecosystems, proven at scale</td></tr><tr><td>A startup prioritizing speed-to-market</td><td><strong>Rails</strong> or <strong>Wasp</strong></td><td>Maximum productivity, minimum boilerplate</td></tr><tr><td>Building a data/ML-heavy product</td><td><strong>Django</strong></td><td>Python ecosystem integration is unmatched</td></tr><tr><td>A JS/TS developer who wants batteries included</td><td><strong>Wasp</strong></td><td>The Laravel/Rails experience for the JavaScript ecosystem</td></tr><tr><td>Need maximum frontend flexibility</td><td><strong>Next.js</strong></td><td>React ecosystem, Vercel deployment, custom everything</td></tr><tr><td>Optimizing for job market value</td><td><strong>Next.js</strong> or <strong>Django</strong></td><td>Largest demand for React and Python skills</td></tr><tr><td>Prioritizing AI-assisted development (vibe coding)</td><td><strong>Wasp</strong></td><td>Config-as-architecture, low boilerplate, batteries-included</td></tr></tbody></table>]]></content:encoded>
            <author>vince@wasp-lang.dev (Vince Canger)</author>
            <category>wasp</category>
            <category>fullstack</category>
            <category>frameworks</category>
            <category>web-development</category>
        </item>
    </channel>
</rss>