3CX Self-Hosted vs Cloud: Which Is Right for Australian Businesses?

3CX is unusual among business PBX platforms in that it gives you a genuine choice of deployment model. You can run 3CX on your own hardware or VPS (self-hosted), or you can have 3CX host it for you in their cloud infrastructure (3CX hosted). The core PBX software is the same, but Hosted by 3CX has additional deployment restrictions and does not include support for configuration, SIP trunks or IP phones. For Australian businesses evaluating 3CX, this choice has real implications for cost, IT workload, data sovereignty, and reliability.

Quick Verdict

What the Deployment Choice Actually Means

For up to 10 users, 3CX offers the separate shared SMB Free service; new dedicated Hosted by 3CX deployments start at 8 SC. At larger simultaneous-call tiers, self-hosting may reduce the direct hosting charge, but the result depends on the current 3CX edition, promotions, VPS specification, backup costs and IT labour. If you're evaluating this now, get the comparison right before you commit. Migrating between hosting models later is possible but disruptive.

Self-hosting 3CX is not as complex as it sounds for a small business. An Australian-hosted VPS from a provider such as BinaryLane is one self-hosting option. 3CX provides a Debian 12 ISO and guided deployment workflows, but installation still requires system, network, split-DNS and firewall configuration. If you have no IT capability in-house, cloud-hosted is the simpler choice. Self-hosting requires a technically capable administrator or partner familiar with the hosting provider, networking and 3CX's supported configuration.

3CX is a software PBX, a Windows or Linux application that handles VoIP call processing, the web client, mobile apps, conferencing, and administration. When 3CX talks about 'self-hosted vs cloud', they mean:

Self-hosted: You install 3CX on a server you control, either physical hardware in your office or a VPS you provision at a cloud provider (AWS, Azure, BinaryLane, Vultr, etc.). You manage OS updates, 3CX updates, backups, and uptime. 3CX provides the software license. Your data stays on infrastructure you control.

3CX Cloud (hosted by 3CX): 3CX provisions and manages the server for you. You pay an annual system licence and, for Hosted by 3CX, a hosting charge based on the simultaneous-call tier. Updates happen automatically. 3CX is responsible for server uptime. Your PBX is deployed on infrastructure managed by 3CX; Australia is an available region, but the selected region and the residency of connected services should be confirmed.

The 3CX application itself is identical in both deployments. Core client and PBX features are available in both deployments subject to the selected edition, but Hosted by 3CX has deployment restrictions, including SBC or router-phone requirements for IP phones, no SSH or failover mode, and customer-managed backups. The choice affects server management and cost as well as phone connectivity, administrative access, failover options and backup responsibility.

Cost Comparison

3CX pricing uses simultaneous calls (SC) as its unit, not users. A 4 SC licence allows four active internal or external calls at once, but current 3CX policy limits 4 SC Free to 10 users and a paid 4 SC tier to 15 users. This is different from most cloud phone system companies that price per user per month.

On 3CX's current published pricing the gap is narrower than it is often assumed to be. The licence costs the same either way, so the only real difference is your VPS bill against the Hosted by 3CX charge. At 8 SC that is a saving of roughly $175 to $235 a year for self-hosting. At 16 SC it is about $245 to $425, and at 32 SC about $560 to $800. Self-hosting is cheaper and the gap does widen with scale, but at small-business scale it is a few hundred dollars a year, which one or two support incidents of your own IT time can erase. The question is whether your IT team's time to manage the server costs less than the hosting charge.

Self-Hosted vs 3CX Cloud: What It Actually Costs

An 8 SC (8 simultaneous calls) deployment is a realistic reference for a business with 15 to 25 staff and moderate call volume. Self-hosted on a Linux VPS: the 3CX PRO 8 SC annual licence is AUD $635, which is USD $395 on 3CX's own price list (read 7 September 2026, ex GST). BinaryLane offers a 2 vCPU, 4 GB VPS in this price range, but its base storage is below 3CX's current suggested small-system specification; price a VPS that meets the actual user, workload, storage and backup requirements. An 8-channel SIP trunk from an AU provider costs $48 to $80 per month ($576 to $960/year). Recalculate the annual and per-user totals using a current VPS quote that meets 3CX's guidance for the actual user count, workload, storage and backup design.On 3CX Hosted the same 8 SC PRO licence is AUD $635 plus a Hosted by 3CX charge of AUD $475 a year, so $1,110 before calls, with SIP trunk costs still on top ($576 to $960). Annual total: $1,686 to $2,070 AUD. The annual saving from self-hosting at this scale is $175 to $235, before IT time, and it is simply the hosting charge less what you pay your own VPS provider. At 16 SC the saving grows to roughly $245 to $425. At small scale, the decision is less about cost and more about whether your business has someone available to manage the VPS and respond quickly when issues arise.

IT Requirements for Self-Hosting

Running 3CX self-hosted on a Linux VPS (Debian 12 is the recommended OS for 3CX Linux) requires someone who can:

• Provision and harden a Linux VPS
• Install and configure 3CX using the 3CX installation script
• Manage firewall rules using 3CX's current firewall guide; the required inbound and outbound ports depend on apps, SBCs, SIP trunks, push services and conferencing as well as HTTPS, SIP and RTP.
• Apply 3CX updates when notified (3CX releases updates regularly; some are security patches requiring prompt application)
• Diagnose call quality issues at the network and SIP level when they occur
• Restore from backup if the VPS or 3CX installation fails

This is not an entry-level task. Ongoing management time varies with deployment complexity, monitoring, backup design, update frequency and incident volume; estimate it from the proposed support arrangement rather than using a universal monthly figure. The problem is incident response, when 3CX breaks at 9am on a Monday, someone needs to diagnose and fix it promptly. Cloud hosting removes much of the server and operating-system incident burden, but configuration, SIP-trunk, phone and backup issues still require an administrator or knowledgeable partner.

Data Sovereignty: Where Is Your Call Data?

For organisations subject to specific legal, contractual or risk-management obligations, verify where call recordings, call records and voicemail are stored and whether cross-border handling is permitted.

Self-hosted: Full control. Choosing an Australian VPS can keep PBX-resident data in the selected Australian region, but verify the locations used by SIP trunks, backups, conferencing, transcription, CRM and other connected services separately. You can verify the physical location and document it for compliance purposes.

3CX Cloud: 3CX says its hosted service is distributed across dozens of data centres worldwide, with Australia available as a deployment region. 3CX Hosted supports deployment in Australia when the appropriate Australian region is selected; confirm the selected region and the residency scope for all connected services before deployment. For businesses with strict data sovereignty requirements, this eliminates 3CX Cloud as an option and makes self-hosting on an Australian VPS the correct choice.

The data sovereignty question carries different weight depending on your industry. Healthcare organisations should assess the privacy, health-record and contractual obligations that apply to their recordings and call metadata; do not attribute a general call-data residency rule to ADHA without a specific applicable source. APRA-regulated entities and legal practices may have additional risk-management, notification and confidentiality obligations, but these are not blanket Australian-data-residency rules. Whether data location is a legal, contractual or risk requirement depends on the organisation, the information and the applicable obligations; it should not be assumed to be only a preference. If Australian data residency is mandatory, confirm that an Australian Hosted by 3CX region is selected and assess the locations used by SIP, backup and integration services; an Australian self-hosted VPS is another option.

Reliability and Uptime

3CX currently states an average hosted-service SLA figure of 99.99%, while noting that system updates may cause limited downtime; verify the applicable service terms and exclusions. For most Australian SMBs, this is acceptable.

For self-hosted, your uptime is whatever you engineer. Self-hosted availability depends on the selected provider's applicable SLA, the architecture, maintenance, monitoring, backups and incident response; verify the commitment for the exact VPS service. Response time matters too: an unattended failed VPS could mean hours of phone system downtime. If you self-host, configure uptime monitoring (UptimeRobot is free for basic checks) and receive immediate alerts when 3CX becomes unreachable.

The practical uptime difference between well-managed self-hosted and 3CX Cloud is small. Cloud reduces the human response burden for server and operating-system failures, but administrators or partners must still respond to configuration, SIP-trunk, phone and backup incidents.

The support experience differs significantly between options. On 3CX Cloud, infrastructure issues are handled directly by 3CX. On self-hosted, your IT person or MSP manages the VPS, OS, and 3CX application layer. For a hosted-infrastructure fault, contact 3CX; configuration, SIP-trunk and IP-phone faults may still require your partner or support provider, and 4 SC hosting has additional support limitations. Factor your expected response time into the availability assessment, not just the theoretical uptime figures from the SLA.

Which Should You Choose?

For most Australian small businesses (under 20 staff, no specific compliance requirements, no dedicated IT staff), 3CX Cloud is the lower-risk choice. The hosting premium is real but manageable at small scale, and the absence of server management overhead is worth it. If 3CX Cloud's pricing at your scale is higher than you want to pay, the alternative is not necessarily self-hosted 3CX, it may be a fully managed Australian cloud phone system from a local provider (Maxotel and similar), which includes both the software and the hosting in a simple per-user monthly fee with Australian support. See our best cloud phone system companies in Australia comparison.

For businesses with 30+ users, in-house IT capability, and a preference for data control, self-hosted 3CX on an Australian VPS is a strong option. The annual savings at scale are significant, and the IT overhead is manageable with the right skills in place.

If you are evaluating 3CX as part of a broader decision about which phone system is right for your business, our guide to the best phone system for small business in Australia covers the full landscape, from self-hosted PBX through to managed cloud, with per-user cost comparisons and an honest assessment of when 3CX makes sense versus a simpler managed option.

The 3CX decision sits within the larger question of moving from a traditional phone setup to internet-based calling. Our guide to cloud phone systems vs traditional phones for Australian businesses covers the full comparison: what you gain, what you give up, and the NBN-specific constraints that affect every Australian business on this transition.

What Most Businesses Get Wrong With 3CX Hosting

Underestimating the ongoing Linux management requirement. 3CX on a Linux VPS is not install-and-forget. Administrators must monitor and apply supported 3CX updates and maintain backups and firewall configuration, but should not install Debian updates manually; 3CX-managed FQDN subscriptions include automatic Let's Encrypt renewal. The honest question is not "can I install it?" but "can I diagnose and fix a problem at 9am on a Tuesday when staff cannot make calls?" If the answer is uncertain, 3CX Cloud is worth the premium.

Not counting IT time in the self-hosted TCO. The cost comparison tables in this guide assume zero cost for internal IT time. If your IT person or MSP spends four hours per year on 3CX maintenance at $120 per hour, that is $480 per year, which narrows the gap at lower simultaneous call counts significantly. At 8 SC, whether self-hosting is cheaper depends on current hosting charges, VPS and backup costs, and actual labour; it does not necessarily remain cheaper once IT time is included. At four SC, include your real labour rate before assuming it is cheaper.

Choosing 3CX when a simpler managed cloud system is enough. 3CX is a powerful PBX platform with advanced features that some small businesses may not need. For a five-person business that needs inbound routing, voicemail to email, and a mobile app, a managed Australian cloud phone provider handles all of that without any infrastructure to manage. The right question is whether your business will actually use the features that justify 3CX specifically: advanced IVR scripting, CRM integration, contact centre routing, or BLF monitoring across a large extension set. If the answer is no, simpler is faster and often cheaper.

Mistake 4: Treating the deployment choice as permanent. Businesses that start on 3CX Cloud can migrate to self-hosted later, and vice versa. Migration time varies with backup size, DNS propagation, SIP-provider restrictions, SBC or phone preparation and the destination's requirements; plan and test the change rather than assuming a half-day duration. If you are genuinely uncertain, starting on 3CX Cloud is the lower-risk path. The cost differential at small scale is manageable, and you can reassess once you have a clearer view of your actual call volume and IT capacity.

Your Next Steps

Before choosing a deployment model:

• List the specific 3CX features your business will actually configure (advanced IVR, CRM integration, contact centre). If none apply, compare a managed cloud system first
• Honestly assess whether in-house Linux admin capability exists for self-hosted maintenance, not just installation
• Run the full TCO comparison including VPS cost plus estimated maintenance hours at your actual IT labour rate
• If choosing 3CX Cloud: confirm data sovereignty requirements and whether Australian data centre hosting is needed
• If choosing self-hosted: test the VPS deployment in a non-production environment before decommissioning your current phone service

Can I switch between self-hosted and 3CX Cloud later?

Yes. 3CX supports migration between deployment models, you can export your configuration (extensions, ring groups, IVR, call recordings) from one instance and import it into another. The migration is not instant but is well-documented. If you start with cloud and later want to self-host (or vice versa), it is a manageable process.

Does 3CX Cloud host data in Australia?

3CX Hosted supports deployment in Australia when the Australian region is selected; confirm the region shown during provisioning and verify the residency of connected services. If AU data residency is a compliance requirement, self-hosting on an Australian VPS is the correct choice.

Is the 3CX free plan genuinely free, or does it have hidden costs?

Hosted SMB Free currently includes free hosting for up to 10 users but has a limited feature set. Self-hosted 4 SC Basic Free is a separate limited edition that requires annual manual renewal; its VPS, SIP trunk, numbers and calls remain separate costs. You also need a SIP trunk from an Australian carrier for phone numbers and PSTN calls, that is a separate ongoing cost regardless of the deployment model.

How does 3CX compare to FreePBX for self-hosted deployments?

3CX is a commercial product with a polished web client, iOS/Android apps, and paid support. FreePBX is open-source with a larger module ecosystem but requires more Linux and telephony expertise to maintain. 3CX's management interface is significantly more approachable for non-specialists. FreePBX has no commercial per-SC licensing cost. See our 3CX vs FreePBX comparison.

Do I need a static IP address for 3CX self-hosted?

3CX requires a dedicated public IP for self-hosted deployments and specifies a static IP for on-premises installations; do not assume DDNS is a supported substitute. Static-IP availability and pricing vary by ISP and plan; check the current terms of the specific NBN service. For a self-hosted phone system, that cost is usually worth it. 3CX Cloud has no static IP requirement because 3CX manages the infrastructure.

Related reading:

• 3CX review for Australian businesses
• 3CX pricing guide for Australia
• 3CX vs FreePBX
• Best cloud phone system companies in Australia

Not sure which option is right after reading this? Tell us your team size, whether you have IT support in-house, and whether data sovereignty is a requirement for your industry. We'll give you a specific recommendation. We reply personally, usually within one business day.