Common
questions.

Anything Prisma supports — PostgreSQL is the default, but MySQL, MariaDB, SQLite, SQL Server, MongoDB, and CockroachDB all work. Switching is a single env var and a re-run of `prisma generate`.

Full-stack. The client is Next.js, the server is Express + Bun in a separate workspace, the queue layer runs as its own worker. They communicate over HTTP + a typed contract package.

The Next.js client deploys cleanly to Vercel. The Express server needs a long-running runtime — Fly.io, Render, Railway, or your own VPS. Step-by-step guides for each in the docs.

Stripe for global B2B, MercadoPago because LATAM customers can't always pay with international cards, Polar.sh for OSS-friendly billing with built-in license keys. They all live behind the same IPaymentProvider port.

Yes. The AI module is one bounded context; deleting its module folder + the related routes is a 10-minute job. Same for any other module — that's the point of bounded contexts.

Founder tier: 6 months of updates via private GitHub repo invite. Lifetime tier: forever. Updates are tagged releases with a migration guide for breaking changes.

Yes. Email [email protected] within 14 days of purchase for a full refund. No questions asked.

Yes. The license covers commercial use across as many projects as you ship — including agency / consultancy work for clients. You can't resell or redistribute the boilerplate itself.

The marketing site ships with English / Spanish / Portuguese already wired. The dashboard uses next-intl and is set up the same way — drop in a new dict file to add a locale.

Around 25k LOC across the monorepo, ~459 tests, ~24 docs pages, ~10 bounded contexts. Big enough to be useful, small enough to read end-to-end in a weekend.