Explanation
Multi-tenancy
Tenant isolation, key management, and routing.
codingassist.bot is multi-tenant from the kernel up. Every record carries a tenant_id; every key is scoped per tenant.
Isolation boundaries
| Boundary | Mechanism |
|---|---|
| Storage | Row-level tenant_id on every table; per-tenant DEK |
| Compute | Stage workers shard by tenant_id modulo |
| Network | Egress per tenant routed through a tenant-scoped proxy |
| Logs | Tenant-scoped streams; no cross-tenant reads |
Per-tenant Data Encryption Keys
Every tenant has its own DEK, wrapped by a Key Encryption Key (KEK) in your KMS. Token rotation re-wraps the DEK; data does not need to be re-encrypted.
Routing
Requests are routed by the X-Tenant-Id header, validated against the bearer token's claims. A token bound to tenant A can never read tenant B.
Related
Was this page helpful?