Comparison · Business phone systems
Hosted VoIP or on-premises PBX: choosing a business phone architecture
Last updated 25 October 2026 · 2 sources listed · Reading time about 4 minutes
Short answer
Hosted VoIP moves call control to a provider and charges per user, trading capital outlay and maintenance for dependence on your internet connection and the provider's platform. An on-premises PBX keeps control and local resilience but demands hardware, patching and in-house skill. Weigh staffing, site count, resilience needs, integrations and regulatory obligations.
Who this is for: An owner or operations lead replacing an ageing office phone system and deciding whether to host calling in the cloud or keep a private branch exchange on site.
What to evaluate
Internet dependency and resilience
A hosted system stops working if the connection fails, whereas an on-site PBX can still route internal calls and may keep local trunks alive.
How to check: Ask how calls fail over to mobile or an alternative route, and test whether you have redundant internet paths.
In-house technical capacity
On-premises systems require patching, backup, hardware replacement and someone who understands the dial plan.
How to check: Assess who would maintain the system and what happens if that person leaves.
Site count and remote working
Hosted platforms treat a home worker and a branch office in the same way, while a PBX needs tunnels or session border equipment to extend its reach.
How to check: Map every location and remote worker and ask how each connects and registers.
Integration with business tools
Calling that links to customer records, ticketing or messaging saves time, but connectors differ widely between platforms.
How to check: List the applications that must integrate and ask for a demonstration with your actual tools.
Total ownership profile
Hosted charges recur per user and feature, while on-premises systems front-load hardware and licences, then add support contracts and replacement cycles.
How to check: Build a multi-year comparison including hardware refresh, licensing, support, power and staff time.
Security and compliance duties
Call recording, retention, toll fraud exposure and data location rules affect both models in different ways.
How to check: Ask where recordings and logs are stored, who can access them, and how toll fraud is detected and capped.
Contract flexibility and exit
Hosted agreements can lock in user counts and terms, and porting numbers away later requires cooperation.
How to check: Ask how users can be added or removed, what notice is needed, and how number porting works at exit.
Comparison
| Architecture | Good when | Watch out for |
|---|---|---|
| Hosted VoIP | You have several sites or remote staff and limited IT capacity | Outages in your internet or the provider's platform stop calling. |
| On-premises PBX | You need local control, specialised integrations or strong on-site resilience | Hardware ageing, patching burden and costly capacity changes. |
| Hybrid with local gateway | You keep analogue devices such as door entry or fax while moving most users to cloud | Two systems to manage and a more complex dial plan. |
| Hosted with softphones only | Staff mostly work on laptops and mobile | Audio quality depends on headsets and home network quality. |
| Provider-managed on-premises system | You want local equipment without the in-house skill | Dependence on the managed service contract and its response commitments. |
Decision worksheet
Rate up to three options against this guide’s own criteria. It runs in your browser and saves only on this device. It is a thinking aid, not a recommendation.
1. Have you checked each criterion?
0 of 7 criteria checked.
2. Compare options (0 = fails or unknown, 3 = meets it well)
| Criterion | |||
|---|---|---|---|
| Internet dependency and resilience | |||
| In-house technical capacity | |||
| Site count and remote working | |||
| Integration with business tools | |||
| Total ownership profile | |||
| Security and compliance duties | |||
| Contract flexibility and exit | |||
| Total (max 21) | 0 | 0 | 0 |
Questions to ask before you commit
- What happens to calls if our internet connection fails, and can calls divert automatically to mobile numbers?
- Who maintains and patches the system, and what is the response commitment for faults?
- How are emergency calls routed and how is each user's location registered?
- What integrations exist for our customer records and collaboration tools?
- How is toll fraud detected and what spending limits can be set?
- Where are call recordings stored and for how long?
- How can we add or remove users, and is there a minimum commitment?
- How do we port our numbers away at the end of the contract?
Typical trade-offs
Cloud flexibility or local control
- Upside
- Cloud lets you add users and sites quickly with little hardware.
- Downside
- You depend on the provider's roadmap, pricing and uptime, with less freedom to customise.
Per-user recurring model or upfront investment
- Upside
- Recurring charges spread cost and avoid large purchases.
- Downside
- Over a long horizon, total spend can exceed owning hardware, and stopping payment stops service.
Desk phones or softphone-only
- Upside
- Desk phones give dependable audio and familiar operation.
- Downside
- Softphones cut hardware cost and suit mobile staff but rely on headsets and laptops.
Common mistakes
- Moving to hosted calling without testing the network. Assess bandwidth, jitter and router quality, and prioritise voice traffic first.
- Forgetting analogue devices such as alarms, lifts and card machines that need adapters or a gateway.
- Overlooking emergency calling obligations, including accurate location data for each extension.
- Underestimating the effort of number porting. Plan the timeline and keep the old service live until the port completes.
- Buying more features than the team will use, then paying for them on every seat.
Related questions
What is the difference between VoIP and a PBX?
VoIP describes carrying voice as data over an internet protocol network. A PBX is the switching system that connects internal extensions and routes calls to the outside world. Modern PBX systems often use VoIP internally, and hosted VoIP providers run the equivalent of a PBX in their own data centres. The real question for a buyer is where the call control software and hardware live and who looks after them, not whether voice travels over IP.
Will call quality suffer on a hosted system?
Quality depends mostly on the network between your handsets and the provider. Poor Wi-Fi, saturated links or routers that cannot prioritise voice cause choppy audio and delay. With a wired connection, adequate capacity and quality-of-service settings, hosted calls can be indistinguishable from traditional lines. Ask for a network readiness assessment and run a pilot with real users before committing the whole business.
Can I keep my existing phone numbers?
Numbers can usually be ported to a new provider, but the process involves paperwork, notice periods and coordination between the losing and gaining carriers. Delays or mismatches in account details can postpone the cutover. Start early, gather a recent bill and authorisation letter, and keep the old service active until the port is confirmed so that inbound calls are never interrupted.
Is an on-premises PBX obsolete?
No. It remains reasonable where sites need independence from the internet, where specialised integrations exist, or where a business has the skills and prefers a long equipment life. The decline in the market is real, but the best fit depends on your circumstances. Check the vendor's support horizon for the specific platform, because reaching end of support creates risk regardless of whether the system still functions.
How do I handle emergency calls on VoIP?
Emergency services need to know where a caller is, and with VoIP the user may not be at a fixed location. Providers must follow local rules on location registration, and administrators often need to keep each extension's address accurate, especially for remote staff. Ask how the platform handles nomadic users, and train employees to confirm their location if they call emergency services from a softphone.
Sources and further reading
These pages were reachable when we last checked. They informed definitions and rules referred to above; they do not endorse this guide. Where rules differ by country, check the authority for your location.
- Consumer help center — Federal Communications Commission, retrieved 27 October 2026
- Internet Engineering Task Force — IETF, retrieved 27 October 2026
Related guides
How to choose · Business phone systems
How to choose a business VoIP or unified communications provider
Shortlist providers by how well they fit your call flows, not by headline feature counts. Examine reliability commitments, emergency calling, support quality, integration depth, security practices, admin tooling and contract terms. Run a pilot with real users, including call handling, mobile apps and headsets, before moving the whole organisation.
Requirements · Business phone systems
What your network must provide before moving to business VoIP
Reliable VoIP depends on sufficient upstream and downstream capacity, low delay and jitter, prioritisation of voice traffic, a router that handles real-time traffic well, power for handsets and, ideally, a second internet path. Audit the network, test under load, and plan for the electrical and cabling needs of desk phones.
Problems & fixes · Business phone systems
Common problems when replacing a business phone system and how to avoid them
Migrations most often go wrong over number porting delays, forgotten analogue devices, emergency call location, call flows rebuilt from assumption rather than reality, and untrained staff. Plan a staged cutover, document every number and device, test with real users, keep the old system until the port is confirmed, and prepare a rollback.
Comparison · Mobile plans
SIM-only plan or handset contract: how to decide
A handset contract spreads the device cost into the monthly bill and ties you to a fixed term, while a SIM-only plan separates airtime from hardware and usually ends sooner or rolls month to month. Compare the total paid across the whole term, what happens if you leave early, and whether you want freedom to change handset or provider mid-term.
How to choose · Cybersecurity and IT
How to choose a business firewall
Choose a firewall by matching throughput under your real security features, management model and update commitments to your environment. Inspect how much traffic it can handle with inspection enabled, what remote access it supports, how policy is managed and logged, and how long the maker supplies security updates. Support lifetime and management effort matter more than the feature list.
Comparison · Retail and ecommerce
Hosted storefront service versus self-hosted ecommerce software
Hosted services trade flexibility for convenience: updates, security and uptime are the vendor's job. Self-hosted software trades convenience for control: you can alter anything, but you carry maintenance, hosting quality and breach risk. The decision turns on available technical skill, how unusual the business logic is, and how comfortable you are depending on a vendor's pricing and rules.
Problems & fixes · Business internet
Why business internet installations run late and how to manage the timeline
Delays come from survey findings, landlord and wayleave consents, civil works, equipment lead times and handover gaps. Order early, request a site survey, secure building permissions in parallel, ask for written milestones and plan an interim connection so that the business can operate while the permanent service is completed.