Multi-tenant AI Architecture

Multi-tenant AI architecture is how a SaaS AI platform serves many organizations from one control plane without mixing their data, tools, or conversations. In Qefro the top boundary is the organization (tenant); inside it, AI Workspaces isolate teams and use cases.

Short definition (citation-ready)

Multi-tenant AI architecture enforces hard isolation between customer organizations — and usually softer isolation between workspaces inside an organization — across knowledge indexes, tool credentials, conversations, and administrative APIs.

Why it matters

Without tenancy:

• Customer A’s documents could appear in Customer B’s answers
• Tool credentials could be invoked across orgs
• Analytics and billing would be unreliable
• Enterprise buyers cannot pass security review

Tenancy is therefore both a security and a product requirement for AI Workspace platforms.

Layered model

Layer	Qefro unit	Isolates
Platform	Qefro cloud (api.qefro.com, app.qefro.com)	Shared infra, per-tenant logical isolation
Tenant	Organization	Users, billing, branding, widget token
Workspace	AI Workspace	Knowledge, tools, conversations
Access	Teams + RBAC	Which members see which Employee AI workspaces
Channel	Widget / WhatsApp / Portal	How external or internal users attach

Control plane

Admin Console

Configure workspaces, knowledge, tools, RBAC per tenant.

Data plane

Runtime

Chat, RAG, and Business Actions resolve tenant + workspace first.

Experience

Channels

Widget, WhatsApp, and Internal Portal inherit those scopes.

Request path (conceptual)

1. Authenticate (user JWT, widget token, or channel webhook).
2. Resolve tenant from the credential / host.
3. Resolve workspace from channel binding or portal selection.
4. Retrieve only from that workspace’s knowledge index.
5. Allow only that workspace’s Business Tools.
6. Emit logs attributed to tenant + workspace (+ actor when known).

Security deep dive: Tenant Isolation.

Single-tenant / enterprise variants

Some enterprises require private deployment. Conceptually the isolation model stays the same; the difference is where the control/data planes run. See Deployment and Production Deployment.

Design workflow

Design tenancy for your AI rollout

1. One org per customer — Never share an Admin Console org across legal entities that must be isolated.
2. Workspaces per audience — Customer vs employee corpora stay split.
3. Bind channels carefully — Widget workspace IDs and portal grants are security boundaries.
4. Review custom domains — Portal hostnames still map to one tenant.
5. Audit — Use execution and admin audit logs in security reviews.

FAQ

Is a workspace a tenant?

No. The organization is the tenant. Workspaces are sub-scopes for knowledge and tools inside that tenant.

Can two organizations share knowledge?

Not by default. Each org’s indexes and tools are isolated. Sharing requires deliberate export/import of content.

How does this relate to Hybrid RAG?

Hybrid RAG runs inside a workspace index. Tenancy ensures retrieval never searches another org’s index.

Note

Product entry points: Organizations, AI Workspaces, Security Overview.

Related topics