Multi-Tenancy Model

Wristband is an authentication platform purpose-built for multi-tenant SaaS applications. Before detailing Wristband’s approach to multi-tenancy, it's helpful to review some of the core design principles that underpin multi-tenant architectures.

A multi-tenant application is a single software instance that serves multiple, distinct groups of users, known as tenants. These tenants typically correspond to real-world entities such as companies, institutions, or other types of organizations.

Supporting multi-tenancy introduces unique architectural requirements. Two of the most critical are:

1. Tenant Isolation: The application must enforce strict boundaries between tenants to prevent data leakage and unintended cross-tenant side effects. From the end user's perspective, their tenant should behave as an entirely separate instance, even though multiple tenants share the same underlying infrastructure.
2. Tenant Configurability: Tenants often have unique business, security, and branding requirements. As such, a multi-tenant application must support per-tenant customization across various areas, including authentication policies, UI theming, and business logic.

With these architectural principles in mind, let's now explore Wristband’s multi-tenancy model. Use the links below to learn how Wristband provides support for tenant isolation and configurability.

• Tenant Isolation - Learn how Wristband enforces tenant isolation for both its entities and authentication flows.
• Tenant Configurability - Learn how Wristband's hierarchical configurations allow for each tenant to customize their authentication flows.