By workload
Your tenants deserve
their own sandbox.
Per-tenant WASM isolation. No shared memory, no side channels, no noisy neighbors. True hardware-level separation.
Explore the details
Every tenant gets a clear boundary.
Choose a sample identity and a storage owner, then attempt a read. The local evaluator allows matching scopes and denies cross-tenant access.
Acme
config.jsonevents.dbusage.logOrbit
config.jsonevents.dbusage.logNorth
config.jsonevents.dbusage.logExample rule: identity.tenant must equal resource.tenant. No actual files are read.
Isolation model
Three tenants. Zero overlap.
Security
Security that scales with your tenants.
Aes-256-gcm
All tenant data encrypted at rest with unique per-tenant keys. Keys rotated automatically.
Namespace isolation
Each tenant operates in its own network namespace. No cross-tenant DNS, no shared ports.
Per-tenant RBAC
Role-based access control scoped to each tenant. API keys, SSO, and service accounts isolated.
Tenant audit logs
Separate, immutable audit trails per tenant. Exportable, queryable, and retained per your SLA.
Resource quotas
CPU, memory, storage, and request rate limits enforced per tenant. No noisy neighbors.
Residency controls
Pin tenant data to specific regions. Enforce data residency at the platform level, not in code.
Every tenant. Their
own universe.
Ship multi-tenant SaaS with real isolation from day one.