Architecture Overview

DevMatrix is built as a monorepo, keeping the frontend, backend, and shared packages versioned together.

Monorepo structure

monorepo structure

DevMatrix/
├─ apps/
│  ├─ web        # Next.js frontend
│  └─ api        # backend API
└─ packages/
   ├─ ui
   ├─ config
   └─ shared

Frontend

Next.js
TypeScript
TailwindCSS

Backend

Express or NestJS
TypeScript
MongoDB or PostgreSQL
JWT Authentication

How modules connect

The backend exposes one core API for auth and projects, and each module (Playground, Debugging, Analytics, Idea Validator) is its own set of routes and tables that all foreign-key back to projectId. The frontend renders each module as a route inside the dashboard shell, reading the active project from the same authenticated client.

Why a monorepoShipping the frontend, backend, and shared types from one repo keeps the API contract and the UI in sync as new modules are added — a change to a shared type surfaces immediately in both apps.

Why modules ship in this order

Core auth and the Project entity come first since every module depends on them. API Playground ships next because it needs no AI and no external integrations, making it the reference pattern for the modules that follow. See What is DevMatrix? for the full roadmap.

PreviousUsers & Auth Next StepAPI Playground