Skip to content

Multi-Tenant Architecture Governance, by Workspace

Complete workspace isolation. Per-workspace identity, branding, AI configuration, and billing. Built for enterprises with distinct business units and for consultancies serving multiple clients on a single platform.

Isolation Is a Foundation, Not a Feature

Multi-tenancy is often retrofitted onto single-tenant applications, with subtle leaks lurking in queries that forgot to scope by tenant. For architecture data — strategy decisions, threat models, vendor evaluations — a single leaked query is a serious incident.

cajeX is multi-tenant by construction. Every record is keyed to the workspace it belongs to. Every query routes through workspace-aware middleware that enforces scoping before the database is touched. There is no code path where a query can return rows from a different workspace.

On top of the data layer, AI settings are isolated too. Each workspace has its own model choice and budget, and a workspace that brings its own provider key stores it encrypted at rest with a per-workspace AES-GCM-256 key.

Eight Tenancy Capabilities

Everything you need to run cajeX as a single workspace, or as dozens of isolated workspaces under one organisation.

Workspace Isolation

Complete data isolation: every record is keyed to its workspace and workspace-aware middleware scopes every query to a single workspace. AI provider API keys are encrypted at rest with per-workspace AES-GCM-256 keys.

Onboarding Wizard

Guided setup for new workspaces — organisation details, plan selection, initial team invitations, and first-run defaults.

Custom Branding

Upload your workspace logo and configure brand colours to match your organisation's identity across the app.

Identity Providers

Social Login (Google, GitHub, Apple) and Magic Link on all standard plans. Enterprise SSO with OIDC, SAML, SCIM provisioning, and Single Logout — Entra ID natively supported, plus any OIDC-compliant provider (Okta, Auth0, etc.) on Enterprise plans.

Member Management

Token-based invitations with accept/revoke flow, bulk invite capabilities, role assignment, and ownership transfer.

Billing & Subscriptions

Per-seat billing via Stripe across Free, Basic, Pro, Team, and Enterprise tiers, with automatic seat counting and per-workspace AI usage tracking.

Data Export

Export everything the workspace holds from Settings → Export (Pro and above): directives, findings, knowledge base, projects, applications, decisions, sessions and uploaded files, with a manifest.

Workspace Purge & Retention

Soft delete with a 30-day recovery window and scheduled purge. Restore your workspace anytime before permanent deletion.

Identity Provider Deep Dive

cajeX supports the identity stack you already use — from one-click social login on standard plans to full enterprise SSO with SCIM provisioning.

Standard plans

One-click social login on Free, Basic, Pro, and Team plans. No identity provider configuration required.

  • Google
  • Apple
  • GitHub
  • Magic Link

Enterprise SSO

Centralised identity for Enterprise workspaces. Automatic user lifecycle management via SCIM, group-based role mapping, and SLO so user offboarding propagates instantly.

  • Microsoft Entra ID (native)
  • Any OIDC provider (Okta, Auth0)
  • SAML 2.0
  • SCIM 2.0 provisioning
  • Single Logout

Single Workspace or Multiple?

Both models are first-class in cajeX. Choose based on whether you need shared standards across your organisation, or distinct governance per business unit.

Single workspace

You're one organisation with one architecture team applying one set of standards. Different teams or business units can share the workspace using role-based access and project tagging.

Typical examples

  • Mid-market companies
  • Single-tenant enterprises
  • Startup engineering teams

Multiple workspaces

You serve multiple clients with separate governance standards (consultancies), or you operate distinct business units with materially different architecture practices (large enterprises, holding companies).

Typical examples

  • Architecture consultancies (one workspace per client)
  • Holding companies with separate operating businesses
  • Enterprises running multiple acquisition entities
See the canonical use-case pages: Architecture Consultancies and Enterprise Architecture Teams.

Per-Workspace AI Configuration

Each workspace has its own AI settings. You choose the model and the budget independently — no shared quotas, and no path for one workspace's AI usage to touch another's.

  • Different model per workspace. Keep the default in your main workspace and run a different model in a client-facing or experimental one.
  • Per-workspace key encryption. Where a workspace brings its own provider key (Enterprise and Private Cloud), it is encrypted at rest with its own AES-GCM-256 key.
  • Per-workspace quotas. Set token budgets per workspace; the platform tracks usage by model, task, and day. Hit a quota and that workspace pauses AI features — others continue uninterrupted.
  • Disable AI per workspace. Regulated workspaces can turn off AI features entirely — every other governance module still works. See AI Co-Worker.

Frequently Asked Questions

What is workspace isolation in cajeX?
Every workspace has its own data partition. Every record is keyed to its workspace, and workspace-aware middleware scopes each query to one workspace, so no query can return data from another workspace. AI provider API keys are encrypted at rest with per-workspace AES-GCM-256 keys. There is no shared key, no cross-workspace data leakage path.
Does cajeX support SCIM for user provisioning?
Yes, on Enterprise plans. SCIM 2.0 provisioning automates user lifecycle — when your identity provider adds, updates, or deactivates a user, cajeX mirrors the change. Group-based role mapping lets you assign cajeX roles based on IdP group membership.
Can different workspaces use different AI models?
Yes. Each workspace picks its own model in Settings → AI, from GPT-5.6 Luna, MiniMax M3, Kimi K2.6, Gemini 3.7 Flash, Claude Haiku 4.5, Claude Sonnet 5 and Claude Opus 5, and has its own usage budget. On Enterprise and Private Cloud plans a workspace can also use its own provider key, encrypted per workspace.
How does per-seat billing work across multiple workspaces?
Each workspace is billed independently. Seats are counted automatically per workspace; adding a member mid-cycle is prorated. Workspaces can be on different plan tiers — a consultancy might run their internal workspace on Team and each client workspace on Basic.
What happens when a user belongs to multiple workspaces?
Each workspace membership is a separate billing seat. The user can switch between workspaces from the app; permissions are evaluated independently per workspace. Single Sign-On (on Enterprise) signs the user in across all workspaces they have access to.
Can I migrate from a single workspace to multiple later?
Yes. A second workspace can be created at any time and run beside the first. Workspace data exports in an open, documented format; setting the content up again in the new workspace is a manual step today, as there is no bulk import of an export.

Set Up Your First Workspace

Start free, no credit card required. Add more workspaces as your organisation or client roster grows.