Enterprise · Multi-Tenant
Tenant → reservoir → agent → dataspace.
Four levels of containment, baked into the kernel. Deterministic 128-bit namespace IDs. Per-namespace encryption keys via HKDF-SHA256. Per-namespace audit chains. No shared state by accident.
At a glance
What's here.
The shape of this page in six lines.
Four-level hierarchy
tenant · reservoir · agent · dataspace — each with its own keys, audit, and policy.
Deterministic IDs
SHA-256 namespace IDs — reproducible, addressable, never colliding.
Per-namespace KEKs
HKDF-SHA256 derives a unique key for every namespace from the root.
Quotas
Per-namespace storage, throughput, and compute caps. Enforced at the kernel.
Audit isolation
Each namespace has its own Merkle audit chain. No cross-tenant leakage.
Hot attach
Mount external volumes (S3, KMS, NAS) at any level without restart.
Reference
Useful links.
referencebash
// Create a tenant and a reservoir within it.
const tenant = await minds.tenant.create({
name: "acme",
region: "us-east",
quotas: { storageGB: 500, opsPerSec: 50_000 },
});
const reservoir = await tenant.reservoir.create({ name: "research" });
const agent = await reservoir.agent.create({ name: "alpha" });
const space = await agent.dataspace.create({ name: "q3-analysis" });Specs
Details.
At a glance
- Levels
- 4 (tenant · reservoir · agent · dataspace)
- Namespace ID
- 128-bit SHA-256 deterministic
- Per-namespace KEK
- HKDF-SHA256
- Quota enforcement
- kernel-level
- Audit isolation
- per-namespace Merkle chain
Guarantees
- Durability
- fsync per WAL commit
- Isolation
- MVCC · snapshot
- Audit
- BLAKE3 Merkle chain
- Encryption
- AES-256-GCM per-namespace
- Concurrency
- 100K+ ops/sec
Get started in an afternoon.
Run anywhere — Akasha Cloud, on-prem, or air-gapped.