3CX Self-Hosted

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

7 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

3CX V20 November 2026 Linux security hotfix

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.

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.

Primary source · Reviewed 2026-11-19

What lands where

  1. Supplied by

    Vendor or project

    3CX deployment wizard or provider Marketplace path for AWS, Azure, Google Cloud or DigitalOcean

  2. Operated by

    Your team

    Customer manages the cloud instance, networking and firewall, DNS/FQDN, backups, upgrades, monitoring, trunks, endpoints and licensing.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install method3CX deployment wizard or provider Marketplace path for AWS, Azure, Google Cloud or DigitalOcean
InfrastructureServers / containers
3CX runs as a persistent PBX and communications application on a customer-managed cloud VM.
Licensing modelCommercial Only
3CX is proprietary commercial software licensed by edition and capacity; cloud hosting and telecom services are separate.
LicenseProprietary annual 3CX system license; edition and simultaneous-call entitlements vary.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

12 of 12 fields researched (100%) · 9 documented · 3 unresolved. Evidence coverage is not a feature score.

Marketplace delivery
AvailableEvidence and scope for Marketplace delivery

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.

3CX AWS self-hosted AMI 20.0.10.1785, externally licensed · Source ↗ · Vendor AWS Marketplace installation guide ↗ · Offer prodview-f5qwwdeeq4uvm ↗ — 3CX; Amazon Machine Image (AMI), x86; package 20.0.10.1785 · Reviewed 2026-11-18

Documented · Editor reviewed.

Cloud commitment eligibility
Not eligibleEvidence and scope for Cloud commitment eligibility

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.

Externally billed software licence for the exact reviewed public 3CX AMI offer; not all provider spend or future private offers · Source ↗ · AWS BYOL pricing boundary ↗ · Commitment qualification remains product/agreement-specific ↗ · Reviewed 2026-11-18

Explicitly unsupported · Editor reviewed.

Single sign-on
Edition-dependentEvidence and scope for Single sign-on

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.

3CX Self-Hosted: selected customer-operated edition · Source ↗ · Reviewed 2026-11-18

Edition-dependent · Editor reviewed.

SCIM provisioning
Not confirmedEvidence and scope for SCIM provisioning

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.

3CX Self-Hosted: selected customer-operated edition · Source ↗ · Reviewed 2026-11-18

Sources checked — unresolved · Editor reviewed.

Compliance attestations
Not confirmedEvidence and scope for Compliance attestations

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.

3CX Self-Hosted: selected customer-operated edition · Source ↗ · Reviewed 2026-11-18

Sources checked — unresolved · Editor reviewed.

Security controls
DocumentedEvidence and scope for Security controls

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.

Self-hosted 3CX V20 SP9/SP10 Linux packages; hosted-by-3CX service is outside this listing · Source ↗ · Prior security-controls source ↗ · Microsoft 365 SSO configuration ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Air-gapped operation
Not availableEvidence and scope for Air-gapped operation

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.

3CX standard documented self-hosted activation and operation · Source ↗ · Reviewed 2026-11-18

Explicitly unsupported · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

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.

3CX Self-Hosted: selected customer-operated edition · Source ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

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.

3CX Self-Hosted: selected customer-operated edition · Source ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

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.

3CX Self-Hosted: selected customer-operated edition · Source ↗ · External licence billing in the exact AWS offer ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Operating cost estimate
Not confirmedEvidence and scope for Operating cost estimate

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.

Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput · Source ↗ · Current AWS Linux EC2 rates; workload/topology still required ↗ · Storage performance and charging inputs ↗ · Reviewed 2026-11-18

Sources checked — unresolved · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

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.

3CX Self-Hosted: selected customer-operated edition · Source ↗ · Production PBX build number ↗ · AWS AMI package 20.0.10.1785 ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Scope & considerations

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.

Category fit

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

Compare within Collaboration

  • Apache AnswerSelf-hosted community questions, answers and knowledge content.
    • AWS
    • DigitalOcean
    • Railway
    • Linode
    • Vultr
    • Hostinger
    • LumaDock
    Customer-operated · Open Source / Open Core
  • BigBlueButtonSelf-hosted conferencing and virtual classroom platform.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    • Hetzner
    • Scaleway
    Customer-operated · Open Source / Open Core
  • BookStack Self-HostedSelf-hosted wiki and documentation organized into books, chapters and pages.
    • AWS
    • DigitalOcean
    • Linode
    • Vultr
    • Hostinger
    • LumaDock
    Customer-operated · Open Source / Open Core
  • Campfire (ONCE)Self-hosted group chat and team conversation application.
    • DigitalOcean
    Customer-operated · Open Source / Open Core
  • Collabora Online (CODE)Community office editing server for integration with a document platform.
    • AWS
    • DigitalOcean
    • Hetzner
    • Linode
    • Vultr
    • Hostinger
    • LumaDock
    Customer-operated · Open Source / Open Core
  • Confluence Data CenterCommercial self-managed Confluence edition for enterprise collaboration and knowledge management. New Data Center subscriptions are restricted to eligible existing Atlassian customers.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • DiscourseSelf-hosted discussion and community platform for workplace collaboration and customer support communities.
    • AWS
    • Google Cloud
    • DigitalOcean
    • Hetzner
    • Linode
    • Vultr
    Customer-operated · Open Source / Open Core
  • Docmost Self-HostedSelf-hosted collaborative wiki and documentation with real-time editing, spaces and page history.
    • Railway
    Customer-operated · Open Source / Open Core

Showing 8 of 25 other listings in Collaboration. These products address related workflows; read their category-fit notes before comparing scope. See all of Collaboration →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • 3CX in the customer's AWS account ↗ · AWS

      Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

      3CX documents provisioning the PBX in a customer AWS account.

    • 3CX in the customer's Azure account ↗ · Azure

      Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

      3CX documents provisioning the PBX in a customer Azure account.

    • 3CX in the customer's Google Cloud account ↗ · Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

      3CX documents provisioning the PBX in a customer Google Cloud account.

    • 3CX in the customer's DigitalOcean account ↗ · DigitalOcean

      Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.

      The current private-cloud install guide identifies DigitalOcean as a supported customer-account deployment target.

    • 3CX-published AWS self-hosted AMI ↗ · AWS

      Marketplace offer · Reviewed 2026-11-18 · Version: 20.0.10.1785. Vendor support commitment: not assessed; confirm the selected release and contract.

      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.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory