System Architecture
Firebreak separates responsibilities across two independent client-facing servers and a shared domain engine operating over a pooled PostgreSQL database.
4 min read
•Production Verified
High-Level System Topology
The web console (apps/web) and MCP server (apps/mcp) are peer applications. Neither proxies through the other; both execute domain logic against @firebreak/core and synchronize state directly through Neon PostgreSQL.
System Architecture: Ingress, Gateways, Core Engine, Persistence, and Cloud Providers
Component Boundaries
| Component | Runtime / Framework | Target Host | Primary Role |
|---|---|---|---|
| apps/web | Next.js 16 / React 19 | Vercel Edge | Human web console, webhook ingestion gateway, Inngest durable job runner. |
| apps/mcp | NitroStack / Node.js | NitroCloud | Universal MCP server exposing 9 typed tools and 3 interactive React widgets. |
| packages/core | TypeScript (tsup) | Shared Package | Drizzle ORM schema, bisection engine, preflight checks, cloud adapters, AES crypto. |
| Database | Neon PostgreSQL | Neon Serverless | 17 relational tables tracking services, alerts, incidents, suspects, actions, and audit logs. |
Monorepo & Task Boundaries
Turborepo orchestrates builds in topological order (^build). The shared core package compiles to dist/index.js and dist/index.d.ts before dependent applications begin compiling.
Monorepo Workspace & Compilation Pipeline