Originally published at ictpbx.com
Hosted PBX Solution: Cloud Convenience Without the Cloud Lock-In
A hosted PBX solution means your business phone system runs on a server somewhere other than your office — and that server handles everything from call routing to voicemail to auto-attendants. For most businesses, that's the right call. You skip the hardware, the maintenance, and the expertise required to run a phone system in-house. But there's a version of "hosted PBX" that costs you significantly more than it should, and another version that gives you everything without the per-seat fees. Understanding the difference saves you money every month.
What "Hosted PBX" Actually Means
The term gets used loosely, so it's worth pinning down. A hosted PBX is simply a PBX (Private Branch Exchange) system that runs on a remote server rather than hardware sitting in your server room. Your phones connect to it over the internet via SIP, and the host — whether that's a cloud vendor or your own VPS — handles call processing, routing, and features.
There are three deployment models people call "hosted PBX":
Cloud subscription PBX: A vendor like RingCentral, Dialpad, or Vonage hosts the system on their infrastructure. You pay per seat, per month, and you have no access to the underlying server. It's fully managed, but you're renting forever.
Self-hosted on your own cloud server: You spin up a VPS or dedicated server, install PBX software, and manage it yourself. You own the deployment; no per-seat fees. This is what most people mean when they say "self-hosted PBX."
Private cloud or hybrid: You run PBX software on infrastructure you control — whether that's a VPS at a data center, a cloud VM at AWS or DigitalOcean, or a dedicated server co-located at a hosting provider. It's hosted in the sense that it's not in your office, but it's yours.
For growing teams and service providers, the third option is almost always the better financial decision. The question is which PBX software you put on that server.
The Hidden Cost of Hosted PBX Subscriptions
Most cloud PBX vendors advertise an entry price that looks reasonable at first. $20–30 per user per month. Then you read the fine print.
Call recording costs extra. International SIP trunks cost extra. The analytics dashboard you actually need is on the next tier up. Your contact center features — call queues, IVR menus, agent reporting — those are enterprise tier. And when you need to add ten more seats, the bill scales linearly with your headcount forever.
A company with 50 seats at $25/user pays $1,250 per month, every month, indefinitely. That's $15,000 per year for a phone system. At 100 seats it doubles. None of that pays for features you own; it pays for continued access to features you've been renting.
I'd argue the per-seat model is fine for very small teams that genuinely don't want to touch infrastructure. But the moment your team grows past 20-30 people, the economics of self-managed hosted PBX become hard to ignore.
ICTPbx Hosted Deployment: Your Infrastructure, Your Rules
ICTPbx is built on FreeSWITCH (the media and call processing engine), ICTCore (REST API and core business logic), and an Angular web dashboard. It's designed from the start for multi-tenant, white-label deployment — which means it handles the complexity of running phone services for multiple organizations from a single server instance.
You can deploy it in three ways:
VPS (entry point): A $20–40/month VPS at any major provider — DigitalOcean, Vultr, Linode, AWS Lightsail — handles a small-to-medium deployment comfortably. For businesses up to 50 concurrent calls, a 4-core VPS with 8GB RAM gives you solid headroom. Your total monthly cost is the VPS, not the VPS plus per-seat fees.
Dedicated server (high-volume): When you're handling hundreds of concurrent calls or running the system for multiple clients, a dedicated server gives you predictable performance without the variability of shared cloud resources. FreeSWITCH performs well on bare metal.
Private cloud (enterprise and MSPs): For managed service providers running ICTPbx as a white-label service for their own clients, private cloud deployment behind a load balancer works well. The multi-tenant architecture means you add tenants (clients) without adding servers unnecessarily. See how ICTPbx handles multi-tenant open source PBX deployments for more on the architecture.
What You Get: Features That Don't Require an Upgrade
One of the frustrations with subscription PBX services is that the features you actually need often sit behind a higher pricing tier. With ICTPbx, the feature set doesn't change based on how much you pay per seat — because there's no per-seat fee.
The core feature set covers:
Auto-attendant (IVR): Multi-level IVR menus that route callers to the right department or extension without a live operator. You configure the menu tree and the audio prompts through the web dashboard.
Call queues: ACD (Automatic Call Distribution) queues with configurable ring strategies — round-robin, least-used, priority-based. Agents log in through the web panel or a SIP softphone.
Voicemail: Per-extension voicemail with voicemail-to-email delivery. Callers hear your greeting; the recording lands in the agent's email inbox.
Call recording: Record on-demand or automatically by extension, queue, or direction. Recordings are stored on your server — no third-party storage fees, no data leaving your infrastructure.
Call analytics: CDR (Call Detail Records) with per-extension, per-queue, and per-trunk reporting. You can pull this data directly via the REST API for custom dashboards.
Ring groups: Blast multiple extensions simultaneously or in a failover sequence for a single inbound number.
Fax over IP: T.38/FoIP support for businesses that still need fax capability integrated with their phone system.
The Angular dashboard makes configuration accessible without needing to edit FreeSWITCH XML directly. For most settings — adding extensions, configuring IVR menus, managing users — you're working in a browser UI, not a config file.
SIP Trunking: Connecting ICTPbx to Your Carrier
A hosted PBX still needs a connection to the public telephone network. That connection comes through a SIP trunk — a VoIP service that gives you inbound DID numbers and outbound PSTN calling at per-minute rates.
ICTPbx connects to any SIP-compatible carrier. You're not locked to a specific provider. Pick whoever offers the best rates and reliability for your region — Twilio, Telnyx, VoIP.ms, or a regional ITSP. You configure the trunk credentials in the ICTPbx admin panel, assign your DID numbers to extensions or IVR menus, and outbound calls go through whichever carrier you've configured.
For service providers running multi-tenant deployments, this matters a lot. You can connect each tenant to a different SIP trunk, or run all tenants through a shared carrier account with number-level routing. Either way, ICTPbx handles the separation.
Remote and Hybrid Workforce Support
If your team works from multiple locations — or fully remotely — a hosted PBX on a VPS serves distributed teams just as well as a cloud subscription service. The difference is where the server lives, not how the phones connect to it.
Remote employees register their SIP softphone (Zoiper, Linphone, or any SIP-compliant app) to your ICTPbx instance over the internet. They get the same extensions, call transfers, queue participation, and voicemail access as office-based staff. For teams that need a web-based phone, ICTPbx's WebRTC support means agents can take calls directly in a browser without installing anything.
The practical difference from a subscription service: your call data stays on your server. Call recordings, CDRs, voicemail — none of it passes through a vendor's infrastructure. For industries with data residency requirements, that's not a nice-to-have. It's the only compliant option.
Total Cost: Subscription vs Self-Hosted ICTPbx
Let's look at a realistic comparison for a 50-seat deployment over three years.
Cost ItemCloud Subscription PBXSelf-Hosted ICTPbx
Seats (50 users)$25/user/month = $1,250/moNot applicable (no per-seat fee)
Server infrastructureIncluded in subscription$40–80/month (VPS or dedicated)
SIP trunkingSometimes bundled, often per-minuteYour choice of carrier, per-minute
Call recording storageOften extra; may cap storageYour disk, your cost
3-year total (approx.)~$45,000~$1,500–3,000
That table doesn't account for setup time or ongoing administration — self-hosted has a real cost there. But the gap at 50 seats is large enough that even paying a sysadmin to manage the server for 2–3 hours per month leaves you significantly ahead. At 100 seats the math becomes almost absurd.
The more honest framing: subscription PBX is cheaper at 5 seats. The crossover point, in most cases, is somewhere between 10 and 20 users. Past that, self-hosted ICTPbx on a VPS wins on pure cost, every time.
Setup Time: Production-Ready in Under 2 Hours
The knock on self-hosted software is that it takes forever to set up. For ICTPbx on a modern VPS, that reputation is out of date.
The installation process follows a standard Linux deployment: provision the VPS with Ubuntu 22.04 LTS, run the ICTPbx installer script, configure your SIP trunk credentials and admin account, and add your first extensions. Most of that is wizard-driven. You don't need to touch FreeSWITCH configuration files for a standard deployment.
A realistic timeline for a first deployment, if you've set up Linux servers before: under 2 hours to a working system with extensions, IVR menu, and a SIP trunk connected. If you're new to VoIP infrastructure, add time for learning SIP trunk concepts and testing call quality. But the software itself doesn't require PBX expertise to get running.
For service providers setting this up as a white-label platform for their clients, the multi-tenant configuration adds some time — but the architecture is purpose-built for it. Learn more about ICTPbx's multi-tenant PBX platform to see how tenant isolation and branding work.
Who Should Use a Self-Hosted Hosted PBX
This setup makes the most sense for three types of organizations:
Growing businesses with 20+ seats where per-seat subscription costs are already noticeable on the monthly bill. The economics flip decisively at this scale, and the administrative overhead of a self-hosted system is manageable with basic Linux familiarity.
ITSPs and managed service providers that want to offer a white-label business phone service to their clients. ICTPbx's multi-tenant design means you manage one deployment and provision tenants as you acquire clients — no separate instance per customer.
Businesses with data residency or compliance requirements where call recordings and CDRs must stay on infrastructure you control. Healthcare, legal, and financial services businesses often find that vendor-hosted PBX creates compliance complications that self-hosted eliminates.
If you're a 5-person team that genuinely never wants to log into a server, a subscription service is probably the right call. But if you're past that point, the case for a self-managed hosted PBX solution gets stronger with every seat you add.
Frequently Asked Questions
What's the difference between hosted PBX and cloud PBX?
The terms are often used interchangeably, but there's a useful distinction: "cloud PBX" usually refers to a multi-tenant SaaS service where you share infrastructure with other customers and pay per seat. "Hosted PBX" can mean that, or it can mean PBX software you host yourself on cloud infrastructure you control. ICTPbx falls into the second category — it's PBX software you run on your own VPS or private cloud.
Do I need technical expertise to run ICTPbx?
Basic Linux server administration helps significantly. You'll be comfortable if you know how to provision a VPS, run commands from SSH, and follow installation documentation. You don't need deep VoIP expertise for a standard deployment — the web dashboard handles most configuration. For complex multi-tenant setups or high-availability configurations, more Linux and networking knowledge helps.
Can ICTPbx support remote workers?
Yes. Remote employees connect their SIP softphone or use the WebRTC-based browser phone to register with your ICTPbx server over the internet. They get full extension functionality — transfers, call queues, voicemail — identical to what office-based staff have. The only requirement is a reliable internet connection and a SIP client.
How does SIP trunking work with ICTPbx?
You sign up with any SIP-compatible carrier — Twilio, Telnyx, VoIP.ms, or a regional ITSP — and get inbound DID numbers plus outbound calling rates. You enter the trunk credentials in the ICTPbx admin panel, assign your DID numbers to extensions or IVR menus, and outbound calls route through your carrier. ICTPbx supports multiple trunks simultaneously for failover or cost optimization.
Is there a limit on how many extensions ICTPbx can handle?
The practical limit depends on your server hardware and the FreeSWITCH configuration, not any license restriction. A mid-range VPS handles dozens of concurrent calls comfortably. For high-volume deployments with hundreds of simultaneous calls, dedicated server hardware gives you predictable performance. ICTPbx doesn't impose a per-seat cap in the software.
What SIP phones and softphones work with ICTPbx?
Any SIP-compliant device or application works: Zoiper, Linphone, Grandstream hardware phones, Yealink desk phones, or any softphone that supports SIP registration. ICTPbx also includes WebRTC support for browser-based calling without a separate client install.
Related Resources
Ready to deploy a hosted PBX solution on infrastructure you own? Contact the ICTPbx team to get started or request a live demo of the platform.
Top comments (0)