1. Scenario Overview
Multi-tenant management is how the platform runs as SaaS. One system serves many companies or brands. Each one is a tenant, and data and permissions stay fully separate. A data pool shares data across SIMs. White-label changes the brand. This capability is about tenant isolation, resource quotas, and usage billing. Each tenant has its own SIMs, plans, users, and orders. The platform operator manages tenants, quotas, and the bill.
A tenant can sign up, start a trial, and upgrade on its own. Plans, operators, and payment channels are configured per tenant and do not leak across. Usage is counted and billed by tenant, which is the commercial model for the platform operator.
2. Core capabilities
Tenant data isolation
SIMs, plans, users, orders, and agents stay inside the tenant. Tenant A cannot read anything that belongs to tenant B. Isolation is by tenant ID, so several customers can share the platform without sharing data.
Configuration that stays inside the tenant
Each tenant sets its own plan packaging, operator connections, payment channels, and white-label. The tenant admin can create sub-accounts and business rules for that tenant only. The platform operator manages the tenant tier, the quota, and the bill.
Self-serve signup and trial
A prospect registers online, enters company details, and picks a trial plan. The trial can open only part of the product, or cap usage — for example at 100 SIMs. When the trial ends, the tenant can upgrade itself to a paid account.
Quotas and usage billing
Set a ceiling on SIMs, data pools, and API calls. Past the ceiling, the platform warns or blocks. Counts of SIMs, data used, and API calls are kept per tenant. Billing can be pay as you go, monthly, or annual, and the invoice can go to payments so the charge is collected without a manual step.
3. From signup to the invoice
4. Tenants, white-label, and data pools
Each one answers a different question:
| Dimension | Multi-tenant | White-label | Data pool |
|---|---|---|---|
| What it covers | Isolation and billing | How the brand looks | SIMs sharing data |
| Core capabilities | Tenant isolation, quotas, usage billing | Logo, colors, and a custom domain | A shared data allowance inside the pool |
| Where it applies | Business-tenant administration | Branding at the tenant | Sharing data at the SIM |
| The question it answers | Whose data, and who pays | What the screen looks like | How several SIMs share one allowance |
They stack. Tenants hold the data boundary and the bill. White-label holds the brand. The data pool holds shared usage. Together that is a multi-brand SaaS operation.
5. Where teams use it
- A SaaS platform: One system, many companies, each a tenant. Data stays separate and the bill follows usage, which is how the platform operator charges.
- Several brands on one platform: Each brand keeps its own white-label, plans, and operators. A change in one brand does not show up in another.
- Trial, then a paid tenant: A prospect signs up for a trial and upgrades when it ends, so acquisition does not wait on a manual provisioning ticket.
6. What one system for many customers changes
Isolation is what makes it safe to put several customers on the same platform. Separate configuration is how their offers stay different. Usage billing is how SaaS pricing actually gets collected. Add white-label when each brand should look like its own product, and end-user management when the business tenant and the people who use the SIMs both need a place in the same system.
7. How to put it in place
Decide the tenant tiers and the quotas before the first signup. A trial can limit both features and usage. Write the usage-billing rules before you start charging. A quota can cap SIMs or API calls, and then warn or block. Each tenant still configures its own plans, operators, and white-label. SimtoLink can help design and stand up the tenant architecture.