Multi-Tenancy (Data per Tenant)

• Jun 23, 2025
• 3 minutes to read

XAF includes an out-of-the box capability to implement multi-tenant or SaaS-ready applications for straightforward CRUD usage scenarios.

View Example: XAF - How to Create a Multi-Tenant Application

Note

Please take a moment to complete a short survey about your multi-tenancy requirements: https://www.devexpress.com/products/net/application_framework/survey.xml.

Glossary

Before you start researching the multi-tenancy feature, we recommend that you take a moment to familiarize yourself with the following terms specific to multi-tenancy in XAF:

Multi-Tenant Application

An application in which a single instance serves multiple independent organizations (tenants) that use the same codebase and business logic but operate on separate data sets.

Tenant

A separate database as well as a group of users that have rights to operate on this database. Each tenant has its own individually stored data sets, access permissions, and application configuration.

Host User Interface

A multi-tenant application’s operation mode for tenant list management. This mode allows a user to create, delete, and edit tenants.

Tenant User Interface

A multi-tenant application’s operation mode where a tenant can specify available data sets, user access permissions, and application configuration.

Host Database

A database that is used in Host User Interface mode. This database stores all information about tenants, the global configuration of a multi-tenant application, and shared business objects.

Tenant Database

A database that a multi-tenant application uses in Tenant User Interface mode. This database stores an individual tenant’s business object data and configurations.

Super Administrator

A user account that is used to access the Host User Interface. This user has no access rights for Tenant User Interfaces.

Best Practices and Limitations

• The same database should not store data that belongs to several separate tenants. All connection strings for Tenant Databases must be unique.
• The same database should not store data from the Host Database and one or more Tenant Databases. None of the Tenant Database connection strings can ever match the Host Database connection string.
• Multi-tenant XAF Blazor apps have the same scalability as regular single-tenant XAF Blazor apps. This means that the number of concurrent users is determined by the sum of concurrent users of all tenants plus concurrent users of the Host User Interface. For more information, refer to Deployment Recommendations for XAF Blazor UI Applications.
• Modules that register their own persistent types do not work in Host User Interface mode. For more information, see Modules in a Multi-Tenant Application.
• Multi-tenant applications do not currently support persistent validation rules.
• Updating databases in a multi-tenant application has specific considerations. Refer to the following help topics for more information:
  • Use EF Core Migrations to Update the Database Schema in Multi-Tenant Applications
  • Update Database in Multi-Tenant Application