What is Wasp?
Wasp is a full-stack framework: you describe routes, pages, queries, auth, jobs and email in a main.wasp.ts spec, write the React and Node.js logic yourself, and the compiler generates the rest. One CLI command deploys to Fly.io or Railway.
Its pitch to AI users is that the spec is a compact description of the whole app, which keeps agent edits inside a known structure. Official agent plugins add version-matched docs, conventions and setup skills to Claude Code, Cursor, Codex, Gemini CLI, Copilot and OpenCode.
The framework is MIT-licensed and still in beta. After raising over $5M, the team retired its custom DSL in favour of the TypeScript spec from version 0.24, and v0.26.1 shipped on 23 October 2026.
Is Wasp worth it?
Wasp's best idea survives the team's own admission of error. In a May 2026 post titled "5 Years and $5M Later", the founders wrote that inventing a configuration language was a mistake; the DSL was retired in 0.24 for a plain TypeScript file. The compiler behind it is unchanged, and the spec still declares auth, routes, operations and jobs in one place. That is what an agent benefits from: it reads one file to learn the app's shape and adds a feature by declaring it rather than wiring five layers by hand.
The agent plugins are thin but practical. In Claude Code they install from a marketplace in two commands, write Wasp conventions into CLAUDE.md or AGENTS.md, and point the agent at docs matching your Wasp version. The older Mage generator, which built apps from a prompt, was archived in July 2026 and only produces the retired DSL, so ignore tutorials that recommend it.
Stability is the real cost. Version 0.26 lists 12 breaking changes, including compile-time type-checking of app code, a compulsory PORT variable and a health check moved to /up. The project calls itself beta. The CLI also sends telemetry, which 0.26 extended to CPU architecture. Next.js or a plain Vite and Express stack ask more of an agent but carry far less upgrade risk.
Where it earns its place
A solo founder with a weekend
Ship a paid SaaS prototype with login and billing
Start from the Open SaaS template (wasp new -t saas), install the Wasp plugin in Claude Code and have the agent add features by editing main.wasp.ts and the React and Node.js files it references. The framework costs nothing; hosting is billed by Fly.io or Railway.
A two-person agency
Build client portals that the next developer can read
Use Wasp's built-in auth and jobs instead of assembling libraries, so an agent or a new hire reads one spec to see every route and operation. Budget time for breaking changes on each minor upgrade.
A team on Wasp 0.23 or earlier
Move off the retired DSL
Follow the legacy migration guide, which says the conversion is mechanical and ships a prompt to hand the job to an LLM, then work through the shared migration steps.
Before you commit
- Setup
- npm i -g @wasp/cli@latest, then wasp new; for agents, claude plugin marketplace add wasp-lang/wasp-agent-plugins and claude plugin install wasp@wasp-agent-plugins, or npx skills add wasp-lang/wasp-agent-plugins for other tools.
- Integrations
- React, Node.js and Prisma; PostgreSQL; wasp deploy for Fly.io and Railway; agent plugins for Claude Code, Cursor, Codex, Gemini CLI, Copilot and OpenCode.
- Data and privacy
- Apps run wherever you deploy them; the CLI collects usage telemetry, which 0.26 extended to report CPU architecture.
- Cost at scale
- No licence cost at any size; production cost is your host and database, plus whatever your coding agent subscription bills.
- Limits
- Beta status with frequent breaking changes; wasp deploy fly needs Fly CLI 0.4.82 or newer and Railway CLI 5.28.0 or newer; the generated stack cannot swap out React, Node.js or Prisma.
What’s good
- One TypeScript spec describes auth, routes, operations and jobs
- Official plugins for Claude Code, Cursor, Codex and others
- Auth, email and background jobs built in
- One-command deploys to Fly.io and Railway
What’s not
- Still beta, with 12 breaking changes in 0.26
- Locked to React, Node.js and Prisma
- Archived Mage generator still turns up in tutorials
- CLI telemetry is on by default
Best for
Solo founders and small teams building React and Node.js SaaS apps with a coding agent who accept pre-1.0 upgrade churn.
Wasp alternatives
Wasp: common questions
- Is Wasp worth it?
- Wasp gives coding agents an unusually clear map of a full-stack app, at the cost of betting on a pre-1.0 framework that still breaks things between releases. We rate it 3.7 out of 5.
- How much does Wasp cost?
- Free and open source (MIT); no paid tier. You pay for hosting and any model provider you use.
- What are the downsides of Wasp?
- Still beta, with 12 breaking changes in 0.26; locked to React, Node.js and Prisma; archived Mage generator still turns up in tutorials; cLI telemetry is on by default.
- Who is Wasp best for?
- Solo founders and small teams building React and Node.js SaaS apps with a coding agent who accept pre-1.0 upgrade churn.
- How much does Wasp cost for a team or in production?
- No licence cost at any size; production cost is your host and database, plus whatever your coding agent subscription bills.
- Is Wasp safe for company data?
- Apps run wherever you deploy them; the CLI collects usage telemetry, which 0.26 extended to report CPU architecture.
- What are the best Wasp alternatives?
- The closest alternatives we have reviewed are InsForge and NocoBase.
Answers checked Nov 16, 2026.