stacks / pick

Stack picker

What would a dev do?

A few questions about what you're building, then the playbook a developer would reach for — and when to skip it.

An API or backend serviceSeveral clientsNo Python work Start over

A dev would reach for

TypeScript API service: NestJS + Postgres + Prisma

A standalone TypeScript API that several clients depend on — mobile apps, partners, other services — with a validated contract and generated docs.

Why this fits

  • Several clients depend on one contract, so request validation and generated OpenAPI docs are part of the product.
  • Modules and dependency injection keep domains separate as the API grows.
  • Guards put authentication, authorization, and rate limiting in one place.

Common trap

Changing response shapes in place once partners depend on them. Version the API from the first external client.

Check this before you commit

Skip if the API is small or has a single client — a lighter framework such as Fastify or Hono, or route handlers next to your web app, costs far less ceremony.

Read the playbook

WWADD — Choose the tool. Make the move. Build the stack.

FREE REFERENCE · NO LOGINCONTACTPRIVACYTERMS