Mosaic is a single, unified platform for identity, authentication, verification, and fraud prevention, built with an API-first approach. Before you write any code, it helps to understand how Mosaic tenants, environments, and apps fit together.
Three concepts define the boundaries you work within:
- Tenant: The top-level administrative and identity boundary. Mosaic maintains one unified record per real person at the tenant level, and everything else—apps, roles, journeys, and promotion—operates inside a tenant. Identity and fraud signals are centralized per tenant, which is what makes detection accurate and integrations simple.
- Environment: Where a tenant runs. Mosaic offers production environments (in several regions) for live traffic, and a sandbox environment for development and testing.
- App: A configuration boundary inside a tenant. You model your organization—subsidiaries, lines of business, markets, and channels—using apps, each with its own isolated user pool and set of journeys. In B2B scenarios, you also model the business entities that access an app as organizations, with their own members and roles.
The platform is designed to model complexity inside a tenant, not by creating many tenants. Keep this in mind as you plan your setup: reach for apps, organizations, and roles before you reach for additional tenants.
Note
Ready to build? Start by creating an application. To plan how you develop, test, and promote your integration across environments, see Development lifecycle.