B2B SaaS tenants
A SaaS product serves many customer companies from one application.
Kinde · Const
Multi-tenancy
Kinde models multi-tenancy with organizations: one Kinde business can serve multiple customers while separating their users, access, and tenant data. Use a flat organization set within a business; separate Kinde businesses are required for independent projects.
How it works
Kinde models multi-tenancy with organizations: each organization represents a tenant whose users, roles, permissions, and data are isolated from other tenants. Use one flat organization set within a Kinde business, or separate Kinde businesses for independent products or projects.
Key points
- Multi-tenancy lets one software instance and its infrastructure serve multiple customers.
- Kinde uses a shared database with a separate schema for each tenant.
- Tenant data is isolated so it is not visible to other tenants.
- Organizations provide the tenant boundary for grouping users and controlling their access separately.
- A user may participate in multiple organizations, so tenant membership is not necessarily exclusive.
- Keep a multi-tenant model flat within one Kinde business.
Common mistakes
- Do not create organizations inside other organizations to represent separate projects and their tenants.
- A single Kinde business cannot independently partition multiple multi-tenant products.
Example: Read the active organization
const org = await kindeClient.getOrganization();
console.log(org.code);Use the active organization returned by the Kinde SDK to scope tenant-aware application behavior.
When to use it
Separate user groups
A platform needs different user groups with distinct access rules.
Cross-organization membership
A user works with more than one customer organization.
Separate products
Several products need independent tenant partitions.
Interview questions
QHow does Kinde model multi-tenancy?
Kinde represents each tenant as an organization. Organizations separate user groups and let you manage organization-specific roles and permissions.
Follow-up: How would you support two independent products? Use separate Kinde businesses rather than nesting organizations or treating one organization set as multiple isolated projects.
QHow is tenant data isolated in Kinde’s model?
Kinde uses one database with a schema per tenant. Customers share the application and database, while each tenant’s data remains isolated and invisible to other tenants.
Follow-up: What is the application-level boundary? Use the organization context to scope users, access decisions, and tenant data consistently.
QCan one user belong to more than one tenant?
Users can belong to multiple organizations. Organization-level management controls access and assigns roles and permissions for each user in that organization.
Follow-up: What must authorization code avoid? It should not assume a user has only one organization; it must use the relevant organization context for the operation.
Related
OrganizationsUser management in organizationsRoles and permissionsAdd and manage organizationsOrganization handles