Wasp

Wasp is the open-source full-stack framework that lets a single .wasp config file describe a complete React + Node.js + Prisma application — authentication, background jobs, email, RPC, end-to-end types and a one-command deploy all generated for you. We rate it 84/100 — for solo founders and small teams who want "Rails for JavaScript" and the most AI-friendly stack on the market in 2026, Wasp is the strongest pick at v0.23.

What is Wasp?

Wasp was started in January 2020 by Croatian brothers Martin and Matija Šošić and went through Y Combinator's W21 batch. The project is MIT-licensed, lives at github.com/wasp-lang/wasp and has crossed 18,290 GitHub stars. The latest release, v0.23.0, shipped on April 15, 2026, and the team is publicly building toward a 1.0.

The pitch is unusual: instead of stitching together Next.js, NextAuth, Prisma, BullMQ, Resend and a deploy script yourself, you write a small declarative main.wasp file describing pages, routes, queries, actions, jobs, auth providers and email senders. The Wasp compiler reads that file and generates a real React + Node.js + Prisma project around your handwritten code. The framework is not a black box — you can wasp build at any point and get a plain Node.js app you could deploy without Wasp installed.

Key Features of Wasp

• Declarative DSL: a 30-line main.wasp file describes routes, pages, server queries, mutations, jobs, websockets, auth providers and email senders. Add auth: { methods: { email: {}, google: {} } } and you have email + Google sign-in plus password reset.
• End-to-end type safety: Wasp generates types from the DSL plus your Prisma schema, so client-side useQuery(getTask) auto-typed against the server function — no tRPC client or OpenAPI generator step.
• Batteries included: auth (email, social, Keycloak, magic link), background jobs (PgBoss, optional cron), email sending (SendGrid, Mailgun, SMTP), websockets and a built-in deploy command for Fly.io and Railway.
• AI-codegen efficiency: a Wasp benchmark in March 2026 showed building the same SaaS used ~40% fewer tokens than the Next.js equivalent — the smaller surface area lets Cursor, Claude Code and Codex iterate cheaper and more reliably.
• Open SaaS starter: the OpenSaaS template (also MIT) ships Wasp + Stripe + Plausible + Astro blog + admin dashboard, and has become one of the most popular AI-first SaaS starters of 2026.
• Cadence: 0.21 → 0.23 over March–April 2026, plus weekly RC drops on the way to v1.0.

What Users Say About Wasp

Sentiment is genuinely warm but realistic. The Show HN and Launch HN threads from 2021 onwards are still the best primary source: founders highlight the time saved on boilerplate, and contrarians push back that "yet another DSL" is a gamble in a JS ecosystem that already has Next.js, Remix and TanStack Start. The recent Ask HN thread ("Thoughts on wasp-JS") in 2025 shows the same split, sharper: indie hackers running production SaaS on Wasp are openly happy, while skeptics worry about lock-in to a non-standard config language. On Reddit's r/webdev and r/SaaS, OpenSaaS-built side projects ship in a weekend and the cited pain points are predictable — TypeScript-only client-side templates, fewer first-party hosting targets than Vercel, and the documentation occasionally trailing the latest 0.x release. The brand-defining sentiment, captured in the team's own "From 'you will fail' to 15,000 stars" post, is that early advice told the founders the project would never work; six years of compounding shipping has done the rebuttal.

Wasp Pricing

The framework itself is free under the MIT license — no per-app fee, no tracked deploy, no telemetry-locked tier. Hosting and managed services are whatever you choose: Fly.io, Railway, Render, AWS or your own server.

Tier	Price	What's Included
Open Source (MIT)	$0	Full framework, CLI, all generators, all auth providers, jobs, email, deploy command
OpenSaaS starter	$0	MIT-licensed SaaS boilerplate built on Wasp — Stripe, admin, blog, analytics
Hosting (Fly.io / Railway / etc.)	varies	Standard cloud pricing — Wasp ships wasp deploy fly and wasp deploy railway wrappers but the bill comes from your provider

Who Should Use Wasp?

Best for: indie hackers, solo founders and small teams who want a Laravel/Rails-class "happy path" in JavaScript, anyone building production SaaS with Cursor or Claude Code who values token efficiency, and developers who like Prisma + React but resent piecing together auth, jobs and email by hand.

Not ideal for: teams that need server components and edge rendering as a hard requirement (use Next.js or TanStack Start), backends that aren't TypeScript on Node.js, or shops that have policies against domain-specific languages and prefer plain TypeScript config.

Pros and Cons

Pros:

• Genuinely batteries-included — auth, jobs, email, RPC, deploy and types all live in one declarative config.
• The most token-efficient stack for AI coding in 2026 — measurably ~40% fewer tokens vs. Next.js for the same SaaS app.
• OpenSaaS is one of the strongest free SaaS boilerplates available; you can ship a paying app over a weekend.
• YC-backed, six-year-old project with consistent shipping and an active core team.
• Output is a real React + Node + Prisma app — no runtime lock-in, you can wasp build and walk away.

Cons:

• Still pre-1.0 — DSL changes have shipped in 0.x minors and you should pin versions.
• Smaller ecosystem than Next.js — fewer first-party integrations and community plugins.
• Mobile/native is out of scope — Wasp targets web full-stack only.
• Documentation occasionally trails the latest release; expect to read source on the bleeding edge.

Alternatives to Wasp

The closest alternatives are Encore (best if you want a similar declarative full-stack story but with Go or TypeScript and managed cloud), Next.js (the default React full-stack — better for edge rendering, much heavier on boilerplate), and tRPC + Prisma + NextAuth (the DIY equivalent of what Wasp generates, only without a compiler hiding the wiring). For pure batteries-included alternatives outside JS, Laravel and Rails remain the gold standard.

Verdict: Is Wasp Worth It?

Wasp is the best answer in 2026 to the "why is shipping a full-stack JS app still this much wiring?" question. The declarative DSL, the OpenSaaS starter, the AI-codegen token efficiency and the founder velocity all point at a framework that is finally fulfilling its Laravel-for-JS promise — six years in. Subtract a few points for pre-1.0 DSL churn and a smaller ecosystem than Next.js and you land at a confident 84/100 — Very Good. We would happily ship a paid SaaS on Wasp + OpenSaaS this week and not look back.

Frequently Asked Questions

Is Wasp free?

Yes. Wasp is MIT-licensed, free for any use including commercial, with no per-app or per-user fee. You only pay your hosting provider (Fly.io, Railway, AWS, etc.).

Is Wasp open source?

Yes — the entire framework lives at github.com/wasp-lang/wasp under the MIT license, with 18,290+ stars and an active core team funded by Y Combinator (W21).

What stack does Wasp generate?

React on the client, Node.js (Express) on the server and Prisma on the database. The same project can deploy to Fly.io, Railway or any Node host via wasp build.

How does Wasp compare to Next.js?

Next.js is a React meta-framework with edge rendering and server components but no built-in auth, jobs or email — you assemble those yourself. Wasp ships all of them as declarative config and compiles to a React + Node app, which a 2026 benchmark found uses about 40% fewer tokens for the same SaaS when generated by AI agents.

Is Wasp production-ready?

The team describes Wasp as "approaching 1.0" but it is already used in production by indie SaaS, YC startups and internal tools at Fortune 500 companies. v0.23 is stable in practice; pin your version and read release notes for DSL changes.

What is OpenSaaS?

OpenSaaS is the official, MIT-licensed SaaS starter from the Wasp team — Stripe billing, email auth, admin dashboard, blog and Plausible analytics on top of Wasp. It pairs especially well with Cursor and Claude Code for AI-assisted development.