
# 3CX Self-Hosted

Commercial business communications and PBX platform installed into the customer's public-cloud account.

Canonical page: https://launchinyourcloud.com/directory/3cx-self-hosted/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## 3CX Self-Hosted

Commercial business communications and PBX platform installed into the customer's public-cloud account.

- Listing: https://launchinyourcloud.com/directory/3cx-self-hosted/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp, digitalocean
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Proprietary annual 3CX system license; edition and simultaneous-call entitlements vary.
- Licensing model: commercial-only
- Installation: 3CX deployment wizard or provider Marketplace path for AWS, Azure, Google Cloud or DigitalOcean
- Architecture: Customer-operated PBX/application VM with web client, SIP/RTP media, certificates, firewall rules and external trunk or carrier dependencies.
- Operations: Customer manages the cloud instance, networking and firewall, DNS/FQDN, backups, upgrades, monitoring, trunks, endpoints and licensing.
- Product website: https://www.3cx.com/
- Source review: 2026-11-19; cloud review: 2026-11-18; licensing review: 2026-11-18; infrastructure review: 2026-11-18

### Scope and qualifications

This entry excludes the Hosted by 3CX service. External SIP trunks, carriers, calling charges and endpoint hardware remain separate. Review provider sizing and media-network requirements before deployment. The AWS AMI is vendor-published package 20.0.10.1785 on Debian 12, with its 3CX licence billed outside AWS Marketplace. 3CX's November 2026 security-hotfix log updates V20 SP9/SP10 Linux packages including nginx, the kernel, PostgreSQL, BIND, SASL and rsync. Apply the latest update through the Admin Console, restart as directed and verify the deployed package set; do not treat the application build number alone as proof that OS hotfixes are current.

3CX is proprietary commercial software licensed by edition and capacity; cloud hosting and telecom services are separate.

3CX runs as a persistent PBX and communications application on a customer-managed cloud VM.


### Category fit

- collaboration: Provides business voice, video, chat, web meetings and PBX collaboration in a customer-operated deployment.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.3cx.com/docs/hosted-pbx-aws/ (checked 2026-11-18). Source: https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm (checked 2026-11-18). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.3cx.com/docs/hosted-pbx-azure/ (checked 2026-11-18). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.3cx.com/docs/hosted-pbx-google-cloud/ (checked 2026-11-18). 

- digitalocean: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://www.3cx.com/docs/manual/install/ (checked 2026-11-18). 


### Cloud deployment evidence

- 3CX in the customer's AWS account (aws): https://www.3cx.com/docs/hosted-pbx-aws/
  3CX documents provisioning the PBX in a customer AWS account.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- 3CX in the customer's Azure account (azure): https://www.3cx.com/docs/hosted-pbx-azure/
  3CX documents provisioning the PBX in a customer Azure account.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- 3CX in the customer's Google Cloud account (gcp): https://www.3cx.com/docs/hosted-pbx-google-cloud/
  3CX documents provisioning the PBX in a customer Google Cloud account.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- 3CX in the customer's DigitalOcean account (digitalocean): https://www.3cx.com/docs/manual/install/
  The current private-cloud install guide identifies DigitalOcean as a supported customer-account deployment target.
  Source type: vendor-documentation; reviewed: 2026-11-18; vendor support: not-assessed.

- 3CX-published AWS self-hosted AMI (aws): https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm
  The vendor publishes the full PBX as a Debian 12 x86 AMI in the customer AWS account. Software licensing is external to AWS Marketplace; telecom and infrastructure charges are separate.
  Source type: marketplace-offer; reviewed: 2026-11-18; vendor support: not-assessed. Versions: 20.0.10.1785.


### Sources

- Install 3CX in a private cloud: https://www.3cx.com/docs/manual/install/

- Deploy 3CX on AWS: https://www.3cx.com/docs/hosted-pbx-aws/

- Deploy 3CX on Azure: https://www.3cx.com/docs/hosted-pbx-azure/

- Deploy 3CX on Google Cloud: https://www.3cx.com/docs/hosted-pbx-google-cloud/

- 3CX pricing: https://www.3cx.com/ordering/pricing/

- Exact vendor AWS AMI and external licence billing: https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm

- 3CX PBX security updates change log: https://www.3cx.com/blog/change-log/pbx-security-updates/

### Licensing sources

- https://www.3cx.com/ordering/pricing/

### Infrastructure sources

- https://www.3cx.com/docs/manual/install/


### Buyer diligence


Research coverage: 12/12 fields (100%); 9 documented, 3 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Documented. 3CX publishes prodview-f5qwwdeeq4uvm as an x86 AWS AMI, package 20.0.10.1785 on Debian 12. Its pricing explicitly requires an external 3CX billing/licence relationship; the software licence is purchased outside AWS Marketplace. AWS infrastructure charges remain separate. This is the customer-operated PBX, not Hosted by 3CX. Scope: 3CX AWS self-hosted AMI 20.0.10.1785, externally licensed. Source: https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm (reviewed 2026-11-18). Supporting source: Vendor AWS Marketplace installation guide — https://www.3cx.com/docs/pbx-amazon-aws-marketplace/. Offer prodview-f5qwwdeeq4uvm: 3CX; Amazon Machine Image (AMI), x86; package 20.0.10.1785; https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm.

- Cloud commitment eligibility: Explicitly unsupported. The reviewed 3CX AMI offer explicitly requires buying the software licence outside AWS Marketplace. That externally billed licence is not a software charge on the AWS Marketplace invoice for this offer. This answers the licence-billing route only; eligible EC2/EBS spend or a separately negotiated private offer still requires the buyer’s AWS agreement and seller order terms. Scope: Externally billed software licence for the exact reviewed public 3CX AMI offer; not all provider spend or future private offers. Source: https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm (reviewed 2026-11-18). Supporting source: AWS BYOL pricing boundary — https://docs.aws.amazon.com/marketplace/latest/userguide/BYOL-pricing.html. Supporting source: Commitment qualification remains product/agreement-specific — https://docs.aws.amazon.com/marketplace/latest/buyerguide/multi-product-solutions-buyer-faq.html.

- Single sign-on: Edition-dependent. The Microsoft 365 integration documents SSO to the 3CX web client and one-way scheduled user synchronization. It requires a supported Microsoft 365 Exchange plan and configured application permissions. This does not establish SCIM or every client’s login behavior. Deleted/disabled M365 users remain in 3CX until manually removed; SSO is not a substitute for offboarding. Scope: 3CX Self-Hosted: selected customer-operated edition. Source: https://www.3cx.com/docs/manual/microsoft-365/ (reviewed 2026-11-18).

- SCIM provisioning: Sources checked — unresolved. The M365 guide documents nightly one-way sync, not a SCIM endpoint. A user deleted or disabled in M365 remains in 3CX and must be removed manually; deleting only in 3CX causes recreation at the next sync while the M365 account remains. This confirms a manual offboarding requirement, but does not establish SCIM operations or active-session/extension revocation through a SCIM integration. Scope: 3CX Self-Hosted: selected customer-operated edition. Source: https://www.3cx.com/docs/manual/microsoft-365/ (reviewed 2026-11-18).

- Compliance attestations: Sources checked — unresolved. 3CX describes security reviews with Mandiant, ReversingLabs, Coverity and HackerOne. This establishes a vendor security-testing statement, not a current independent attestation whose scope covers the buyer’s PBX, recordings, carrier/transcription services and operations. Obtain the relevant report, audit period, findings/remediation and deployment boundary. Scope: 3CX Self-Hosted: selected customer-operated edition. Source: https://www.3cx.com/pbx/security/ (reviewed 2026-11-18).

- Security controls: Documented. The firewall guide specifies SIP/RTP, tunnel and HTTPS connectivity and requires uninspected outbound HTTPS for activation. Configure the required ports and TLS/FQDN correctly; external SIP trunks, push and meeting services create separate dependencies. M365 sync does not remove users deleted/disabled at the IdP; explicitly remove them in 3CX and review sessions, SIP/extension credentials and retained data. Current review: The November 2026 V20 SP9/SP10 security-hotfix log refreshes Linux packages including nginx, kernel, PostgreSQL, BIND, SASL and rsync. Apply the latest Admin Console update and verify the installed package set. Scope: Self-hosted 3CX V20 SP9/SP10 Linux packages; hosted-by-3CX service is outside this listing. Source: https://www.3cx.com/blog/change-log/pbx-security-updates/ (reviewed 2026-11-19). Supporting source: Prior security-controls source — https://www.3cx.com/docs/manual/firewall-router-configuration/. Supporting source: Microsoft 365 SSO configuration — https://www.3cx.com/docs/manual/microsoft-365/.

- Air-gapped operation: Explicitly unsupported. The standard documented self-hosted configuration requires outbound HTTPS to activate.3cx.com for licence activation and other external services for updates and selected functions. It is not a fully disconnected deployment path; a separate offline exception was not established. Scope: 3CX standard documented self-hosted activation and operation. Source: https://www.3cx.com/docs/manual/firewall-router-configuration/ (reviewed 2026-11-18).

- Deployment artifact / IaC: Documented. The current installation guide provisions a private-cloud PBX in the customer’s chosen AWS, Azure, Google Cloud or DigitalOcean account. This is a vendor deployment workflow, not a reviewed source-controlled Terraform or CloudFormation artifact. Scope: 3CX Self-Hosted: selected customer-operated edition. Source: https://www.3cx.com/docs/manual/install/ (reviewed 2026-11-18).

- Minimum footprint / sizing: Documented. The current small PBX table lists 2 vCPU/4 GB RAM and 80 GB SSD, with larger tiers and extra recording/log capacity. Its cloud table places up to 250 extensions in the large tier, with AWS t3.xlarge as an example. These are extension/call-capacity guidelines; HA, simultaneous calls and a 1 TB recording policy still need a design. Scope: 3CX Self-Hosted: selected customer-operated edition. Source: https://www.3cx.com/docs/recommended-hardware-specifications-for-3cx/ (reviewed 2026-11-18).

- License pricing: Documented. 3CX publishes annual system licences by edition and simultaneous-call capacity, with extension limits and feature differences. Obtain the selected self-hosted tier; a count of internal users alone does not price licences, trunks or calling charges. The reviewed AWS offer bills its software licence outside AWS Marketplace. Scope: 3CX Self-Hosted: selected customer-operated edition. Source: https://www.3cx.com/ordering/pricing/ (reviewed 2026-11-18). Supporting source: External licence billing in the exact AWS offer — https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm.

- Operating cost estimate: Sources checked — unresolved. Specify concurrent calls, extensions, edition, SIP trunks/minutes, recording/transcription volume, retention and HA/failover requirements. The t3.xlarge sizing example does not include carrier service, a second server, recording backup or external AI services. Scope: Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput. Source: https://www.3cx.com/docs/recommended-hardware-specifications-for-3cx/ (reviewed 2026-11-18). Supporting source: Current AWS Linux EC2 rates; workload/topology still required — https://b0.p.awsstatic.com/pricing/2.0/meteredUnitMaps/ec2/USD/current/ec2-ondemand-without-sec-sel/US%20East%20%28N.%20Virginia%29/Linux/index.json. Supporting source: Storage performance and charging inputs — https://aws.amazon.com/ebs/pricing/.

- Release snapshot / cadence: Documented. 3CX announced V20 Update 10 on November 11, 2026; the V20 change log identifies production build 20.0.10.1785. Exclude release candidates and separately versioned mobile clients from this PBX snapshot. Scope: 3CX Self-Hosted: selected customer-operated edition. Source: https://www.3cx.com/blog/releases/ai-agents-mcp-local-ai/ (reviewed 2026-11-18). Supporting source: Production PBX build number — https://www.3cx.com/blog/change-log/phone-system-change-log-v20/. Supporting source: AWS AMI package 20.0.10.1785 — https://aws.amazon.com/marketplace/pp/prodview-f5qwwdeeq4uvm.




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- 3CX V20 November 2026 Linux security hotfix (security-advisory): 3CX refreshed V20 SP9/SP10 Linux packages including nginx, the kernel, PostgreSQL, BIND, SASL and rsync. Scope: Self-hosted 3CX V20 SP9/SP10 Linux packages; hosted-by-3CX service is outside this listing. Conditions: The exact installed application and operating-system package set determines exposure. Action: Apply the latest Admin Console update, restart as directed and verify installed package versions. Source: https://www.3cx.com/blog/change-log/pbx-security-updates/; reviewed 2026-11-19.



