Multi-Tenancy

Vektagraf treats multi-tenancy as a first-class primitive.

Design motivations:

• Multi-tenant SaaS requires strict isolation
• Application logic should not manually enforce tenant constraints
• Multi-tenancy must apply to data, files, vectors, logs, provenance, and sessions
• Tenants often require their own quotas, policies, and cryptographic boundaries
• Tenant leakage must be cryptographically impossible

Schema representation:

"settings": {
  "multitenancy": {
    "enabled": true,
    "tenant_field": "tenant_id",
    "isolation_level": "strict"
  }
}

All queries and storage operations automatically apply tenant constraints. No developer code is needed.