> How is Wasp different from Next.js / Nuxt.js / Gatsby?
> TL;DR - These are frontend-first frameworks, with some limited backend capabilities.
> [...]
> Although some of them now offer an option to use serverless functions, you still have to bring your own database and you'll also need some kind of a server/backend if you'll need to run more complex operations.
That's a big understatement; Next is fully full stack. You get API endpoints and server-side rendering out of the box.
You can deploy the backend as serverless functions, yes, but you can also deploy it as a plain old Node app.
Does Wasp offer something on the backend that Next doesn't?
> you still have to bring your own database
Confused on this one - does Wasp abstract away the database? The docs show a database connection config and mention using Prisma as the ORM. It looks similar to what I'd do in Next.