ADR 006 - Multi Tenant Architecture
- Date: 2026-01-24
- Status: Active
Problem Statement
HyperPath must meet security and compliance requirements in a multi-tenant architecture.
Decision
Tenant compliance is achieved through environment and tenant isolation rules.
Multiple Environments
- Each environment deploys a separate application stack.
- Each environment gets its own AWS VPC.
- Each environment gets its own RDS cluster.
- Resources should be tagged with environment identifiers where possible.
Shared and Employee Resources
- Shared infrastructure is defined in
infrastructure/shared. - Shared data lives in the
AppDbContextschema. HyperPath.EmployeeWebis employee-only.
Tenant Resources
- Tenant infrastructure is defined in
infrastructure/tenantandHyperPath.InfrastructureDeploy. HyperPath.Webis deployed per tenant.- Tenant data lives in tenant-specific database schemas and uses separate credentials.
- Resources should be tagged with tenant identifiers where possible.
Rationale
Security, compliance, and noisy-neighbor isolation all require strong separation between tenants.