Next.js + Postgres + Prisma + Vercel
The default choice when you need SEO, server rendering, and typed database access in one codebase.
Sources verified Sep 2026
When to use it
- Public content must be indexable and fast on first paint
- You want API routes and UI in the same repo and the same deploy
- The schema is non-trivial and you want migrations under version control
How the pieces fit
Next.js renders on the server, so data fetching happens next to the database instead of over the public internet. Prisma turns the schema into TypeScript types, so a column rename becomes a compile error rather than a runtime 500. Vercel runs the framework it maintains, so routing, caching, and image optimization work without hand-tuning. The result is one mental model: write a server component, query Postgres, return HTML.
Tools and responsibilities
Architectural examples
Each example links to a public source — no claims about private internals.
Cal.com
Open-source scheduling platform whose public repo shows the full shape: Next.js app, Prisma schema and migrations, Postgres database.
sourceNotion's marketing site
Built with Next.js on Vercel and runs hundreds of experiments a year at the edge — the indexable site is kept separate from the Notion app itself.
sourceSkip if
Skip if your app is a purely internal dashboard behind a login — the server rendering cost buys you SEO you will never use.
Testing and shipping this stack
- Test the behavior users depend on
- Check keyboard access and automated accessibility
- Investigate flaky browser tests
- Verify the production build before release
- Keep secrets out of browser bundles
- Make CI validate the same release inputs
- Capture errors with useful context
- Change database schemas in compatible stages
- Prove a backup can restore
- Prepare rollback before publishing