Enterprise
Governed tenancy, not a flat shared board.
Atlas Program contains Platform, Payments, and Documentation. Each project has its own people and capability grants. The Nest backend owns sessions and RBAC. Next.js never opens the database.
Structure
Organization, department, then project.
Slugs are derived from names unless an admin edits them. Projects carry lists, members, and the permission matrix. This is the tenancy model the product enforces — not a marketing diagram invented for this page.
Access
Board, roadmap, reports, knowledge, workflow, people.
Built-in roles are admin, member, limited member, and guest. Guests do not open the board. Members edit tasks. Workflow rules, people, and most settings stay with admin. Custom role profiles can refine the matrix in the product.
Volume
One task model, virtualized lists.
Large backlogs stay on the same records across views. The product virtualizes long lists and patches local state after mutations instead of reloading the workspace. Workload bars make Sprint 18 allocation visible before hours slip.
Ownership
Presentation in Next. Authority in Nest.
The marketing site and the product UI are Next.js. Login, logout, session cookies, RBAC, Git credentials, and the audit log are NestJS talking to PostgreSQL. That split is how Flagship Tracker is built, not a future plan.
Accountability
Comments and audit events sit with the task.
Priority changes, Git links, and mentions are visible on the item. Platform actions write an audit trail the backend stores — the browser is not the system of record.
Talk through tenancy and roles for your organization.
Contact sales to request a workspace, or sign in if you already have one.