Separate every customer
Users, extensions, routes, recordings, reports and configuration stay scoped to a tenant.
MULTI-TENANT PBX · SERVICE PROVIDER
Run customer PBX environments without multiplying separate control panels.
Move an existing FusionPBX or VitalPBX fleet, or onboard new customers, into one service-provider control plane. Keep every tenant, domain, entitlement and SIP carrier explicit while superadministrators retain fleet-wide visibility.
Keep your SIP carriersPer-tenant limitsDry-run migration
WHY MULTI-TENANT
Give MSP operations one control plane without losing tenant boundaries.
Start with a migration assessment or a new tenant. The provider keeps central visibility while every customer sees only its authorised environment.
Delegate routine administration
Give customer administrators the roles they need without exposing provider-level controls.
Operate the whole fleet
Use a superadministrator view, tenant filter and explicit context switch for support and configuration.
PROVIDER CAPABILITIES
The controls required to migrate and run PBX as a service.
Migration evidence
Assess FusionPBX or VitalPBX, run a dry import and review conflicts before anything touches production.
Domains and certificates
Map verified customer hostnames and automate TLS where DNS and policy allow it.
Tenant limits
Enforce extension, concurrent-call, edition and module entitlements per customer.
Central supervision
Review health and activity across tenants with the originating tenant shown in fleet-wide views.
White-label boundaries
Provider branding and delegated customer access remain separate from RelayPBX Cloud tenancy.
PROVIDER WORKFLOW
Assess the fleet, provision a tenant and hand over controlled access.
A tenant is more than a label: it carries its own domain, entitlements, carrier relationship and operational context.
- Run an anonymized assessment and dry migration, or define the first new customer tenant.
- Assign edition, modules, extension and concurrent-call limits before activation.
- Delegate customer roles and validate that provider-only data stays hidden.
- Monitor the fleet centrally and switch tenant context explicitly for support work.
In the shared cloud model RelayPBX is the service provider. The Service Provider edition is designed for Dedicated Cloud or Self-hosted deployments where the customer operates their own tenant fleet.
EXPLORE
Build the surrounding provider operation.
READY FOR A TENANT FLEET