Multi-tenant loyalty runs multiple separate programs on one shared platform instance, with each program isolated as a tenant that has its own data, rules, branding, and configuration. The tenants share underlying infrastructure and software but never see each other's members or activity. It is the same architecture that lets one system efficiently serve many independent clients.
A provider uses multi-tenancy to host many brands' programs cost-effectively on common infrastructure. An enterprise with a portfolio of brands uses it internally to run each brand's program from one platform, keeping members and data partitioned per brand while sharing the engine, the upgrades, and the operational team.
For an operator, multi-tenancy shapes both economics and governance. Shared infrastructure lowers the cost of running additional programs, and one platform to maintain is simpler than many. The critical requirement is isolation: each tenant's data and configuration must stay strictly separated, so a change or an incident in one program cannot affect another. Enterprises evaluate how cleanly a platform enforces that boundary, because a portfolio program depends on it.
