Current structure
Single-user shell
Dashboard, admin, and billing shells exist, but org and tenant domain models do not yet.
ENTERPRISE
A system that has to handle organizations, policy, region, and licensing together
The long-term product is larger than an individual-user SaaS. It eventually needs tenant, residency, licensing, and policy control planes.
Current public state
Current need
Enterprise framing first
The information architecture should prepare for the control plane before the model arrives.
Next stage
Tenant + policy plane
Organization, workspace, residency, and policy profiles belong to the next structural step.
Enterprise plane
Tenant / workspace
Organizations, seats, roles, and workspaces must eventually sit above the single-user shell.
Policy / licensing
Policy profiles, datasource licensing, and usage boundaries need a visible control surface.
Private deployment
Private network, BYO credentials, and region-aware deployment belong to the enterprise lane.
From user SaaS to control plane
TODAY
User shell
Individual-user and admin flows exist today.
NEXT
Org shell
Organization, workspace, role, and policy profile layers need to be added next.
LATER
Enterprise control
Residency, licensing, audit export, and private deployment later complete the control plane.
Enterprise readiness
| Enterprise lane | Public today | Next stage |
|---|---|---|
| Organization / seats | Not implemented | Org / workspace / role model |
| Residency / region | Document-only framing | Tenant profile + region control |
| Licensing / datasource | Trust-language only | Policy-linked licensing plane |
| Private deployment | Support handoff only | Private network / BYO credential lane |
Principles
- Enterprise should expand through control-plane readiness, not only through pricing.
- Without tenant, policy, and residency structures, enterprise claims should stay constrained.
- The public surface has to anticipate later control-plane features without pretending they are already live.