Deployment Models
One platform. Three ways to deploy.
Same multi-tenant architecture, same admin tools, same APIs — packaged for the way you do business. Pick the deployment model that fits your operations, capital structure, and customer expectations.
Multi-Tenant Platform
For MSPs and UCaaS providers
License our software, run it on your infrastructure. Your brand, your billing, your operations.
- You operate the infrastructure and own the customer relationship end-to-end
- Per-tenant isolation, white-label branding, and per-tenant billing data
- Standard PBX licensing — annual subscription, sized to seats or concurrent calls
- Your data stays in your data center / cloud
Dedicated Deployment
For enterprise IT and organizations that need their own instance
A dedicated instance, on-prem or private cloud. For organizations with strict data-residency or integration requirements.
- Runs just your organization — full administrative control, room to grow into more tenants
- On-prem hardware, your private cloud, or a managed install by an integrator
- Best fit for regulated industries (healthcare, finance, government) or deep custom integrations
- Sold direct or through integrators / value-added resellers
Thirdlane Cloud
Early AccessFor MSPs who don’t want to operate infrastructure
We run the platform — you sell it. Channel-only Early Access partner program. Sold and supported under your brand. Not sold direct to end customers.
- Thirdlane operates the multi-tenant infrastructure — you focus on selling and supporting
- White-label: end customers see your brand, your billing, your support
- Channel-only — Thirdlane does not sell direct to end customers
- Currently in Early Access for design-partner MSPs
How to choose
Choose Multi-Tenant Platform if you’re an MSP or UCaaS provider with — or planning to build — your own operational stack and customer billing. You want full control of the environment, the upgrade cadence, and the margin structure.
Choose Dedicated Deployment if you’re an enterprise with regulatory, data-residency, or deep integration requirements that mandate a dedicated instance of your own. Or you’re an integrator delivering a turnkey system to a single customer.
Choose Thirdlane Cloud if you’re an MSP who wants the revenue motion of selling hosted UC without operating the infrastructure yourself. Currently Early Access — apply if you’d like to be a design partner.
Not sure which model fits? Contact our team and we’ll help you compare.
Deployment models — frequently asked questions
What is a multi-tenant PBX?
A multi-tenant PBX is a single phone-system platform that hosts many independent customer organizations (tenants) on one shared installation, with each tenant fully isolated — its own extensions, dial plan, users, branding, and billing data. One platform is patched and upgraded once, and capacity is added by scaling the platform rather than by deploying a separate system per customer. Thirdlane is a true multi-tenant PBX built on this model.
What is the difference between multi-tenant and multi-instance?
In a multi-tenant architecture, one platform serves many tenants from a shared core with per-tenant isolation, so there is one system to run and upgrade. In a multi-instance (or single-tenant-per-customer) architecture, the provider runs a separate PBX instance for every customer, so operational cost, patching, and upgrade effort grow linearly with customer count. Multiple single-tenant instances are not the same as multi-tenancy, even when a management layer sits on top.
What is UCaaS?
UCaaS (Unified Communications as a Service) is cloud-delivered business communications that combine voice/PBX, video meetings, chat and messaging, presence, and often contact center into one service. Thirdlane lets MSPs and service providers deliver UCaaS under their own brand — either self-hosted on a multi-tenant platform they operate, or on Thirdlane Cloud where Thirdlane runs the infrastructure.
What is a dedicated (single-organization) deployment?
A dedicated deployment runs the Thirdlane platform for one organization on its own infrastructure or private cloud, with full administrative control and no shared tenancy. It suits enterprises with strict data-residency, compliance, or deep-integration requirements, and it still uses the same multi-tenant-capable core, so it can grow into more tenants later.
Talk to our team
Walk through deployment options and pricing for your specific use case.