Skip to main content

​
Overview

You must select between multi-tenant or consumer data models when creating your Stytch project. This both defines who “owns” end user data and sets which SDKs and APIs your project has access to.

Multi-tenant auth

Common for B2B SaaS where users exist as to one or more .Uses B2B API & SDKs.

Consumer auth

Single-tenant model where users exist as individual without organizations.Uses Consumer API & SDKs.

​
Model diagram

Multi-tenant vs. single-tenant

​
Why this matters

Different application use cases have different auth needs. For example, the Consumer API is designed for simplicity and works well for apps that don’t require complex identity management features like SSO or SCIM—which are more commonly needed for B2B SaaS apps. Unique identifiers for end users are also slightly differentiated:
  • In multi-tenant auth, a member is identified by their email.
  • In consumer auth, a user is identified by either email or phone number.

​
Need a hybrid model?

If you have a mix of business customers and individual end users, we recommend using multi-tenant auth and creating an organization behind the scene for each individual user “tenant” in order to allow these single-player accounts to seamlessly upgrade and add potential collaborators in the future.