A common Business OS core with separated identity, data, and integration layers.
Explore the public Workspace architecture: Next.js application routes, Clerk identity, company authorization, Supabase Postgres records, and Google integrations.
Application and identity layer
Next.js provides public marketing routes, authenticated panels, server actions, and API routes in one web application. Clerk initializes identity context for protected application requests.
Workspace then maps the signed-in identity to a company user and resolves modules, role permissions, and per-user overrides before sensitive operations.
Operational data layer
Supabase Postgres stores structured records that require relationships, company scope, workflow status, and database policies. Tenant-aware migrations and indexes support this operational model.
Google Drive and Sheets form a separate integration layer for workflows where the approved design calls for connected-account file ownership, including CRM lead storage.
Product expansion layer
The product direction separates common capabilities from context-specific configuration.
- The common core covers reusable CRM, people, project, finance, quotation, inventory, and portal concepts.
- Industry classification supports segmentation and reporting without changing permissions automatically.
- Industry packs can adapt terminology, fields, defaults, and workflows.
- Country packs remain a separate future layer for currency, tax, payroll, and legal rules.