Deployment Options
Choose who operates the multi-tenant platform.
The core software remains the same. The main decision is whether your team operates the platform or Thirdlane operates it for your service. In either model, you retain the offer, pricing, billing, support model, and customer relationship.
Compare operating responsibility
Start with responsibility and capacity. Product modules and customer configuration can then be evaluated against the same technical foundation.
| Decision | Provider-operated platform You operate Thirdlane on your infrastructure. | Thirdlane-operated platform Thirdlane operates it for your service. |
|---|---|---|
| Platform operation | Your team operates the infrastructure and Thirdlane software. | Thirdlane operates the underlying multi-tenant platform. |
| Customer relationship | You define, sell, bill, and support the service. | You still define, sell, bill, and support the service. |
| Infrastructure location | Your selected data center, private cloud, public cloud, or on-premises environment. | Location and operating scope are specified in the quote and agreement. |
| Sizing inputs | Licensed extensions and expected concurrent calls, plus the infrastructure you select. | Extensions, concurrent calls, redundancy, location, retention, and support requirements. |
| Resilience | Choose a single server, replicated standby, or supported high-availability design. | Redundancy and service-level requirements are included in the hosted design and quote. |
| Best fit | Providers that want direct control of infrastructure, operations, and upgrade scheduling. | Providers that want to own the communications service without operating the platform. |
Customer Delivery Pattern
A dedicated environment can be delivered for one customer.
An MSP or systems integrator can deploy a separate Thirdlane environment when a customer requires its own infrastructure boundary, deployment location, integration work, or operating arrangement. Thirdlane provides the software platform; the provider delivers and owns the customer solution.
Size the deployment before choosing the operating model.
Share expected extensions, concurrent calls, locations, resilience, recording retention, and support requirements.