An agency runs two businesses at once: winning and servicing clients, and actually delivering the work. Those usually live in different tools, so nobody can answer simple questions — what is blocked, what is invoiced, what the client can see. AgencyOS puts both halves in one multi-tenant platform: clients and their onboarding checklist, projects and milestones, a Kanban board with dependency rules, support tickets, documents, invoices, notifications and reporting — plus a client portal that shows a client only their own work.
It is a modular monolith with two deployables and one database: Next.js 15 (App Router) for the web, NestJS 11 for the REST API, PostgreSQL 17 with Prisma for persistence. The browser never learns the API host — it calls the same-origin path /api/v1 and Next.js rewrites to API_INTERNAL_URL, so cookies stay first-party and there is no CORS preflight in the happy path.
The project's discipline is separating what is proven from what is merely possible. Builds, lint, 11 unit tests, 15 integration tests against a real PostgreSQL and 4 Playwright end-to-end specs pass; the docs state plainly that Docker images, GitHub Actions runs and every third-party provider call (Stripe, OpenAI, Resend, S3) were not executed in the build sandbox, and those paths are implemented to report themselves unavailable rather than fake success.