Wasp is a full-stack web framework — define your app in a .wasp config file, get React frontend + Node backend + database + auth.
What You Get for Free
-
Declarative config — define routes, queries, actions in
.waspfile - Auth built-in — email, Google, GitHub login in 3 lines
- Full-stack type safety — shared types between client and server
- Database — Prisma ORM integrated
- Real-time — WebSocket support built-in
- Jobs — background and scheduled jobs
- Email sending — built-in email support
-
One-command deploy —
wasp deploy flydeploys to Fly.io - AI-generated apps — describe your app, get code
Quick Start
curl -sSL https://get.wasp-lang.dev/installer.sh | sh
wasp new my-app
// main.wasp
app MyApp {
title: "My SaaS",
auth: {
userEntity: User,
methods: { email: {}, google: {} }
}
}
route DashboardRoute { path: "/dashboard", to: DashboardPage }
page DashboardPage { authRequired: true, component: import { Dashboard } from "@src/pages/Dashboard" }
query getTasks { fn: import { getTasks } from "@src/queries", entities: [Task] }
Why Developers Switch from Next.js + Prisma + NextAuth
Building full-stack Next.js apps requires gluing 5+ libraries:
- Auth in 3 lines — not 200 lines of NextAuth config
-
One config — routes, queries, auth in
.waspfile - Background jobs — built-in, not a separate Bull/Redis setup
- Full-stack types — client knows server return types automatically
A developer spent 2 weeks setting up Next.js + Prisma + NextAuth + Tailwind for a SaaS boilerplate. With Wasp: same functionality in 3 days, 60% less code.
Need Custom Data Solutions?
I build production-grade scrapers and data pipelines for startups, agencies, and research teams.
Browse 88+ ready-made scrapers on Apify → — Reddit, HN, LinkedIn, Google, Amazon, and more.
Custom project? Email me: spinov001@gmail.com — fast turnaround, fair pricing.
Top comments (0)