Multi-Tenancy Architecture

Every Udala workspace is a completely isolated tenant. Your data is never shared with or accessible to any other organisation.

Schema-per-tenant isolation

Each workspace gets its own dedicated PostgreSQL schema (e.g. tenant_nexus_group). This means:

• No shared tables between tenants - no accidental data leakage is possible at the database level
• A bug in another tenant's code cannot expose your data
• Each schema can be backed up, restored or migrated independently
• Tenant schemas can be on different database servers for performance isolation (Enterprise)

Subdomain routing

Each workspace is accessed via its own subdomain: your-company.udala.africa. The app server identifies the tenant from the subdomain and connects to the correct schema before any query runs. Requests to an invalid subdomain return a 404.

Cross-workspace access

An Owner account can belong to multiple workspaces. The workspace switcher in the navigation lets you move between your companies instantly. However, data never crosses workspace boundaries - a query in workspace A cannot read data from workspace B, even if the same user has access to both.

Consolidated reporting

For accounts with multiple workspaces, the Cross-Entity Dashboard (Growth and Enterprise) aggregates data from all your workspaces into a single consolidated view - revenue, headcount, pipeline - without ever merging the underlying data.