There is a persistent belief that a self-hosted FreePBX build is the serious choice and hosted plans are for small businesses. That is not true in either direction. They solve different problems, and picking the wrong one is expensive in different ways.
What each actually is
Off-the-shelf hosted VoIP is a multi-tenant platform. You get a web console, standard features (IVR, queues, voicemail, recording, mobile apps), and the provider handles updates, security and scaling. You configure within the limits of what the platform exposes.
FreePBX is a management interface on top of Asterisk, the open-source telephony engine. You get a system where nearly anything is possible, running on infrastructure you or your provider maintain, which you are responsible for configuring, updating and securing.
When off-the-shelf is the right answer
For the large majority of businesses, it is. Choose hosted when:
- Your call flows are conventional: main line, a few departments, voicemail, maybe a queue
- You need mobile apps and remote work support out of the box
- You do not have someone in-house who wants to own a phone platform
- You want predictable per-seat cost with no maintenance burden
- Time to launch matters more than customization
The features people assume require a custom build (ring groups, time conditions, IVR menus, call recording, basic CRM integration) are standard on any competent hosted platform.
When a custom build earns its cost
FreePBX or raw Asterisk becomes the better choice when you hit something a platform cannot do:
Unusual call logic. Routing driven by live external data, complex conditional flows, multi-stage IVRs with database lookups, or per-call decisions your platform’s rule engine cannot express.
Deep integration. Real-time coupling to an internal system where you need to control what happens between call events rather than just receive webhooks.
Scale economics. At high channel counts, per-seat pricing stops making sense. A call center running hundreds of concurrent channels can often run them for materially less on dedicated infrastructure.
Compliance or data control. Requirements about exactly where recordings live, how long they are retained, and who can reach them, that a shared platform will not accommodate.
Reselling. If telephony is your product rather than your tooling, you need control of the stack.
The costs people forget
Custom builds carry ongoing obligations that rarely appear in the initial comparison.
Security is on you. Internet-facing SIP is scanned constantly. A misconfigured system becomes someone else’s long-distance service overnight, and toll fraud invoices are real and large. Fail2ban, proper firewalling, strong credentials and disabled anonymous SIP are not optional.
Updates are on you. Asterisk and the underlying OS need patching. Neglected systems accumulate known vulnerabilities.
Expertise is on you. Someone has to understand dialplan logic well enough to debug it at 9am when nothing routes. If that person leaves, you have a system nobody can maintain.
Budget maintenance realistically. The licensing is free; the operating cost is not.
The middle path most people want
Managed FreePBX: a custom-built Asterisk environment configured for your call flows, but hosted, monitored, patched and supported by a provider. You get the flexibility of a custom dialplan without owning the security and maintenance burden.
For teams whose requirements are genuinely unusual but who do not want to become a telephony shop, this is usually the correct answer, and it is worth asking about specifically because it sits between the two options most providers advertise.
How to decide
Write down the three call flows that matter most to your business exactly as you want them to work. Take them to a hosted provider and ask them to configure it. If they can, take the hosted plan. If the conversation turns into workarounds, you have found your reason for a custom build.