Why NestJS?

NestJS provides an opinionated structure: modules, controllers, services, guards. This predictability is critical when AI agents generate code — the Executor agent knows exactly where to place a new endpoint, how to wire dependencies, and where validation goes.

Express is flexible, but flexibility kills consistency when AI agents are writing code.

The Setup Problem

Setting up a production NestJS backend takes 4-6 hours:

• Initialize project with TypeScript configuration
• Configure module structure for scalability
• Wire Supabase JWT validation middleware
• Set up WebSocket gateway
• Configure background job processing
• Add health check endpoints
• Set up request logging and error handling

How AI App Factory Handles It

• Module structure follows a scalable pattern
• Auth guard validates Supabase JWTs automatically
• WebSocket gateway ready for real-time features
• Background jobs configured with Bull queue
• Health endpoint at /health for monitoring
• Request logging with structured output

Architecture Pattern

Request → Guard (JWT) → Controller → Service → Supabase/External API
                                        ↓
                                    Response

The AI agents follow this pattern. When you ask for a new feature, the Architect agent designs the module structure and the Executor agent implements it following this exact flow.

Related

• Supabase Auth — provides the JWTs that NestJS validates
• Oracle Cloud Hosting — where the backend runs
• React Native + NestJS + Supabase Starter — the full stack