Architecture

What Is Tenant Isolation?

The complete separation of resources, data, and credentials between different customers (tenants) on a shared platform.

In Plain English

Tenant isolation ensures that Customer A cannot access Customer B's data, credentials, agent configuration, or audit logs — even though they share the same infrastructure.

Clawctl achieves tenant isolation through per-tenant Docker environments, separate encrypted credential stores, isolated file systems, and independent network namespaces. Each tenant gets their own OpenClaw instance running in its own container.

This is not just logical separation (different database rows). It is physical separation at the container level. A compromised tenant cannot lateral-move to another tenant because there is no shared execution environment.

Why It Matters for OpenClaw

Multi-tenant platforms that lack proper isolation are one vulnerability away from a breach affecting all customers. Tenant isolation contains incidents to a single customer, protecting everyone else.

How Clawctl Helps

Clawctl provides per-tenant Docker isolation by default. Separate containers, credentials, file systems, and network namespaces. No shared resources between tenants.

Try Clawctl — 60 Second Deploy

Common Questions

Is it truly isolated or just logically separated?

Truly isolated. Each tenant gets their own Docker container with separate file system, network, and credentials.

Can tenants share resources?

No. Complete separation by default. Enterprise plans can configure controlled resource sharing for multi-agent setups within a single tenant.

What happens if one tenant is compromised?

The blast radius is limited to that tenant. Other tenants are unaffected due to container-level isolation.