01
Tenant-scoped access
Workspace record access is scoped to the authorized tenant. Review the access controls for the records and roles relevant to your deployment.
Multi-tenant Architecture
One platform. Clear tenant boundaries.
Every record carries an account_id. The control plane provisions and bills tenants but never sees their data. Cancellation deactivates access; physical deletion is a separate reviewed operation. The architecture matters when you're the customer and you're auditing it.
Read-only demo · no signup · realistic seeded records
How it works
Tenant isolation by row, enforced through scoped data access.
Azora's multi-tenant model isn't "folders with permissions" or "workspaces with shared infrastructure". Every customer-data table carries a NOT NULL account_id column with an index, and every query is scoped through a helper that adds WHERE account_id = $tenant. The Control Plane (vendor-only) provisions, bills, and suspends tenants — it has no SELECT access to tenant rows.
02
CP / Tenant separation
Control plane sits above; tenant DBs sit below. CP provisions + bills + suspends. Never reads tenant data.
03
Account cancellation
The account cancellation route changes status and disables access. It does not invoke a physical purge.
04
Per-tenant RBAC
Roles and permissions live within the tenant. CP has its own role hierarchy (vendor admin, billing, support).
05
Audit log per tenant
Every CRUD operation logged with actor + tenant. CP actions logged separately to admin_audit_log.
06
Self-host option
Run the same code on your own infrastructure, with the control plane optional. Deployment, updates and data access are defined in a separate services agreement.
Connected workflow
Multi-tenant Architecture works better when the context travels with it.
Azora brings project work, quality, people, suppliers, units and documents into one platform. Review the records and relationships your process needs.
- 01Tenant-scoped access
Workspace record access is scoped to the authorized tenant. Review the access controls for the records and roles relevant to your deployment.
- 02CP / Tenant separation
Control plane sits above; tenant DBs sit below. CP provisions + bills + suspends. Never reads tenant data.
- 03Account cancellation
The account cancellation route changes status and disables access. It does not invoke a physical purge.
- 04Per-tenant RBAC
Roles and permissions live within the tenant. CP has its own role hierarchy (vendor admin, billing, support).
“Before we built Azora's multi-tenant model, we evaluated three SaaS QMS vendors for our own use. Two said 'tenant-isolated' but couldn't show us the schema. That's why we ended up writing our own — and why Azora opens the column to anyone who asks.”
100%Records carry account_id
0Cross-tenant SELECTs in Control Plane
AccessCancellation deactivates users
One connected platformDiscuss the plan and rollout that fit your team.
Review the current platform offering and talk through your team size, configuration and onboarding needs. View platform pricing.
See it before you talk to sales
Audit the architecture, then talk to us.
Open the technical brief for the schema, the helpers, the audit-log structure, and the May 2026 internal security review findings. Then email us with whatever's missing.