Web backends have a named stack

Team standards now names a stack for web backends, the non-trading HTTP services behind our clients and partner integrations.

• Web backends run NestJS on Fastify, with @nestjs/swagger generating the OpenAPI document that architecture requires.
• Data access uses Prisma against PostgreSQL on Cloud SQL, at the latest version Cloud SQL supports.
• Services deploy to GKE with Kustomize and Flux.
• A product client and its backend ship from one repository under pnpm workspaces, as apps/api, apps/web, and apps/worker, with kustomize/ and cloudflare/ beside them. Each app deploys on its own and carries its own CODEOWNERS entry.
• Express needs an exception.

The stack records what the services already run, drawn from market-info-api, trader-dashboard-api, preference-api, remote-storage-api, user-context-api, and nt-follow. Repository manifests and lockfiles set exact versions.

FCM clearing and back-office services stay on Python. This page states the default for new work; an existing service that differs is not, by itself, a reason to migrate.