In brief: Multi-tenant UCaaS hosting — running multiple client phone systems from a single platform instance — is one of the most efficient operating models for SA telecoms MSPs. This guide covers the platforms that support multi-tenancy, the commercial model, and the technical requirements.
What Multi-Tenant UCaaS Means for MSPs
In a traditional deployment model, an MSP might deploy a separate 3CX or Yeastar P-Series instance for each client — a separate server, separate management console, and separate subscription for each business. This is manageable with a handful of clients but becomes operationally complex and expensive as the client base grows to 20, 50, or 100+ businesses.
Multi-tenant UCaaS allows an MSP to run multiple client “tenants” on a single platform instance, with each tenant isolated from the others in terms of extensions, call routing, and data. The MSP manages all tenants from a single administrator console — one place to see all clients, apply updates, and manage licences — while each tenant has its own independent phone system environment.
This model reduces infrastructure costs (one server serves many clients), simplifies operations (single update process, single security patch cycle), and enables more efficient scaling as new clients are onboarded as new tenants rather than new infrastructure deployments.
3CX Multi-Tenant: The SA MSP Standard
3CX V20 includes a mature multi-tenant hosting capability that has become the dominant model for SA MSPs serving small business clients. 3CX’s multi-tenant architecture allows a single 3CX installation to host dozens to hundreds of tenant instances, each with complete PBX independence.
Licensing requirements: 3CX multi-tenant requires a minimum of 16SC PRO licence. This is 3CX’s hosted service licence tier, designed for MSPs selling hosted PBX to clients. The 16SC PRO licence allows the MSP to host up to a defined number of tenants with a combined SC count within the licenced limit. As of April 2026, 3CX strictly enforces this — MSPs running multi-tenant setups without the appropriate hosted licence should correct this before the enforcement deadline.
Server sizing for multi-tenant: A 3CX multi-tenant server hosting 20–50 small business tenants (each with 4–16SC) needs appropriate server resources. General guideline: 8 vCPU, 16GB RAM, and 200GB SSD storage for a 20-30 tenant deployment. Scale resources as tenant count grows; underpowered multi-tenant servers produce poor call quality across all hosted clients.
Multi-tenant management: 3CX’s management console allows MSPs to create, configure, and manage individual tenant instances from a single login. Each tenant has its own admin console accessible via a unique URL, with tenant administrators able to manage their own users without accessing other tenants’ data. This enables a self-service model where each client’s IT administrator manages their own extensions while the MSP handles infrastructure and platform-level management.
Yeastar P-Series Multi-Tenant Option
Yeastar P-Series also supports a multi-tenant model through its Software Edition, allowing a single P-Series installation to serve multiple isolated tenant instances. Similar to 3CX’s model, each tenant is independent with its own configuration and call routing. The Yeastar Management Plane (YMP) provides centralised management of multiple P-Series instances or tenants from a single dashboard.
Yeastar’s multi-tenant implementation is well-suited for SA MSPs who prefer P-Series’s feature set or who serve clients that need the stronger built-in call centre module. The licensing model and resource requirements are comparable to 3CX.
The Commercial Model for Multi-Tenant UCaaS
The standard commercial model for SA MSPs running multi-tenant UCaaS:
Infrastructure costs (per month):
- Hosting server: R800–R2,500/month (Hetzner Cloud CX21/CX31 or equivalent)
- 3CX/Yeastar licence: R1,500–R4,000/month (depends on total SC)
- SIP trunking wholesale: Pass-through cost from provider
Revenue per tenant (per month):
- Hosted PBX subscription (4SC): R400–R800/month per client
- SIP trunk (retail): R500–R2,000/month depending on call volume
- Managed service fee: R200–R500/month per client
A well-run multi-tenant platform with 30 tenants at R1,200/month average generates R36,000/month recurring revenue against approximately R4,000–R8,000/month in infrastructure costs, yielding strong margin for the MSP.
Isolation and Security in Multi-Tenant Deployments
Multi-tenant hosting introduces responsibility: a security incident affecting one tenant could potentially affect others on the same platform if isolation is inadequate. Key security practices for SA multi-tenant MSPs:
- Each tenant must have unique, strong passwords — never reuse credentials between tenants
- Firewall rules should restrict each tenant’s SIP access to their specific trunk provider IPs
- Monitor call volumes per tenant for anomalies — a toll fraud attack on one tenant shouldn’t be able to generate costs that affect others
- Implement per-tenant call cost limits via the SIP trunk provider
- Regular backup of all tenant configurations to external storage
What This Means for SA Telecoms Resellers
Multi-tenant UCaaS hosting is one of the most scalable business models available to SA telecoms resellers. The ability to add new clients as tenants (rather than deploying new infrastructure) dramatically lowers the cost and complexity of onboarding small business customers.
For resellers who currently deploy a separate instance for each client and find the operational overhead increasing, transitioning to a multi-tenant model — with proper planning and testing — can improve both margins and service quality. The investment in a well-specified multi-tenant server and appropriate licencing pays back within 6–12 months at typical SA SME pricing.
About the Author
Mechelle Gindra
Mechelle Gindra is the managing editor and lead content strategist at Telecoms-Channel, South Africa's dedicated intelligence platform for telecoms resellers, ICT distributors, and channel partners. She oversees the editorial team's AI-assisted content production pipeline, ensuring vendor news, market analysis, and regulatory updates are accurate, timely, and actionable for the SA telecoms channel community. With deep expertise in the South African telecoms reseller ecosystem, Mechelle directs coverage of vendor partner programmes, ICASA regulatory developments, wholesale market dynamics, and channel business strategy. She is responsible for maintaining Telecoms-Channel's editorial standards, fact-checking processes, and corrections policy.
