Run SessionPBX on your servers
Approved partners can deploy SessionPBX into their own cloud account or onto a dedicated server. One server can host several customer tenants, each with separate users, domains, seats and billing. Your partner workspace manages those customer projects centrally.
Self-hosted customer tenants use annual licences. Hosting on your own hardware still requires an active SessionPBX licence for each customer.
Supported deployment options
| Deployment | Setup in the partner portal |
|---|---|
| AWS, Microsoft Azure, Google Cloud or DigitalOcean | Connect your cloud account, select an available region and server size, and provide your SSH public key. The deployment creates a dedicated server in your account. |
| Existing cloud server | Supply a supported server’s public IPv4 address, SSH user and SSH port, then authorise the installation key. |
| On-premises server | Choose On-premises server and provide the same supported server and access details. The server must be reachable through its public IPv4 address. |
Cloud-provider availability, permissions and quotas determine which regions and sizes you can select. Your provider bills infrastructure directly to you, including while an installation needs attention.
If self-hosted deployment is unavailable in your partner portal, contact SessionTalk to confirm installer availability before ordering infrastructure.
Requirements for an existing server
- A fresh, dedicated Debian 13 x86_64 server.
- At least 2 vCPUs, 4 GB RAM and 40 GB disk. These are installation minimums; size the server for the customers, calls and recordings you intend to support.
- A public IPv4 address and reachable SSH access using root or a user with passwordless sudo.
- Network and firewall access for installation, the customer workspace, SIP signalling and call media.
- Internet connectivity for SessionTalk provisioning and licence check-ins. This deployment is not an offline licensing option.
For an on-premises deployment, arrange public reachability and the necessary firewall or NAT configuration before installation. A private LAN address alone is not sufficient for the portal installer. Confirm network requirements with SessionTalk for your deployment.
Deploy the first customer
- In the partner workspace, select Create customer tenant.
- Choose Partner cloud or On-premises server, an annual plan and any logo branding option.
- Enter the customer reference, project name and customer administrator email. You can use your own email if you will administer the workspace for the customer.
- Under Server for this customer, choose Set up a new server.
- Enter the cloud-provider or existing-server details. Leave the custom hostname blank to use the project’s assigned
.pbx.sessiontalk.ioaddress, or supply your own hostname pointing to the server’s public IP. - Review the subscription and deployment details, then select Create project & start deployment.
For an existing server, the project shows a temporary installer SSH public key. Add it to the selected user’s ~/.ssh/authorized_keys, select Check server connection, and compare the returned SSH host fingerprint with your server console. Once verified, select Install PBX.
Follow Installation progress in the project. When complete, use Open workspace as admin to configure the customer’s PBX with your partner account. The customer administrator receives a password setup email; the partner administrator can also access the setup link in the project.
SessionTalk email supports administrator setup, team invitations and password resets. You can supply your own SMTP account for email and voicemail notifications and change it later in Workspace Settings → Email.
Add more customers to the same server
Open a completed self-hosted project and select Add another customer to this server under Server management. Alternatively, create a customer tenant with the same deployment type and select the completed server from Server for this customer.
Enter the new customer’s details and review its own annual subscription before selecting Add customer to server. Each customer receives a separate workspace and licence. Adding a tenant to a completed server uses the existing installation.
Operate and update your server
You manage the operating system, backups, firewall, capacity and infrastructure account. Monitor available storage, especially when using voicemail and call recording. Keep customer configuration and recovery procedures up to date.
Where portal updates are enabled, Your servers → Server software shows installed versions, release notes and available updates. Review the release and affected tenants before installing: an update applies to the shared server. Contact SessionTalk if the portal reports that an update agent or compatibility review is required.
Cancelling a customer’s subscription does not delete the server or stop infrastructure charges. Other customers on the server retain their own subscriptions. See partner billing.