Choosing the right server for your FreePBX deployment isn’t just about picking a price point — it’s about matching your infrastructure to your call volume, storage needs, and reliability requirements. This guide will help you find the right fit.
Understanding What Drives Resource Needs #
Before diving into plans, it helps to understand the three main factors that determine how much server you need:
- Concurrent calls — The number of active calls at any given moment is the primary driver of CPU and RAM usage. A system with 50 extensions but a peak of 5 simultaneous calls needs far less than one with 20 extensions that runs a busy call center.
- Call recordings — Recording calls consumes disk space quickly. Even at modest bitrates, a few hundred recorded calls per month adds up fast.
- Features and modules — IVRs, voicemail, conference bridges, call queues, and third-party integrations (CRMs, reporting tools) all add to resource consumption.
General Sizing Reference #
| Scenario | Concurrent Calls | Extensions | Recommended Plan |
|---|---|---|---|
| Home office / hobbyist | 1–3 | 1–10 | Economy |
| Small office | 3–8 | 10–30 | Economy or Business |
| Growing SMB | 8–20 | 30–75 | Business |
| Active SMB / call recording | 15–30 | 50–150 | Business (expanded) |
| Multi-site or high availability | 25+ | 100+ | Enterprise |
| Call center / high availability | 30+ | Any | Enterprise (expanded) |
Rule of thumb: FreePBX is not particularly CPU-hungry for basic call routing, but RAM matters for active calls and loaded modules. Disk fills up faster than most people expect once call recording is enabled.
The Plans #
🟢 Economy — Start smart, grow when you need to #
1 vCPU core / 2GB RAM / 40GB Disk Expandable to: 6GB RAM · 60GB Disk
The Economy plan is a capable starting point for small deployments. It handles light to moderate FreePBX workloads without breaking a sweat, and the expansion options give you some headroom if your needs grow modestly.
Best for:
- Home offices, hobbyists, and lab environments
- Small offices with 10–25 extensions and low concurrent call volume (under 8 simultaneous calls)
- Deployments without heavy call recording — 40GB fills up faster than you’d think
- Testing and staging environments
Expansion options: Add RAM in 2GB increments (up to 6GB) or disk in 20GB increments (up to 60GB) as your needs grow.
⚠️ If you anticipate call recording, plan to add disk early — or consider stepping up to Business.
🔵 Business — The workhorse for growing organizations #
1 vCPU core / 4GB RAM / 100GB Disk Expandable to: 12GB RAM · 1TB Disk · 8 CPU Cores
The Business plan is where most small-to-midsize deployments will be happiest. The base configuration handles a solid range of workloads, and the expansion options are generous — particularly for disk, which can grow to 1TB to accommodate call recording archives or large voicemail stores.
Best for:
- Small to mid-sized businesses with 25–100 extensions
- Deployments with 8–25 concurrent calls at peak
- Organizations with active call recording needs — the generous disk upgrade path has you covered
- FreePBX environments running resource-intensive modules like reporting, CRM integrations, or conference bridges
- Resellers and MSPs hosting multiple tenants on a single instance
Expansion options:
- RAM: Up to 12GB in 2GB increments
- Disk: +50GB, +150GB, +400GB, or +900GB upgrades (up to 1TB total)
- CPU: Upgrade to 2, 4, 6, or 8 cores for demanding workloads
🔴 Enterprise — Performance, reliability, and room to scale #
2 vCPU cores / 4GB RAM / 100GB Disk Expandable to: 16GB RAM · 1TB Disk · 12 CPU Cores · Block Storage · Private VLANs · Full VM Backups
The Enterprise plan isn’t just a bigger box — it’s a fundamentally different class of hardware. If uptime and I/O performance matter to your business, this is where you want to be.
Best for:
- Larger organizations with 100+ extensions or 25+ concurrent calls
- High-availability deployments where downtime is not acceptable
- Businesses requiring full VM-level backups (not just config backups)
- Call centers and high-volume inbound/outbound environments
- Deployments integrating external firewalls, security appliances, or network segmentation via private VLANs
- Multi-server architectures (e.g., FreePBX + separate database or SIP proxy)
Expansion options:
- RAM: Up to 16GB in 2GB increments
- Disk: +50GB, +150GB, +400GB, or +900GB upgrades (up to 1TB total)
- CPU: Upgrade to 2, 4, 6, 8, 10, or 12 cores
- Block storage: For large recording archives or external data volumes
- Private VLANs: Isolate and secure your network topology
- Full VM backups: Snapshot-level protection for complete system recovery
Disk Planning: Don’t Get Caught Off Guard #
Call recordings are the number one cause of unexpected disk exhaustion. Use this rough guide to plan ahead:
| Recording Volume | Approx. Monthly Storage |
|---|---|
| Light (few calls recorded, <500/mo) | ~2–5 GB/month |
| Moderate (most calls recorded, ~2,000/mo) | ~10–20 GB/month |
| Heavy (call center, 10,000+ calls/mo) | ~50–100 GB/month |
Estimates based on GSM/G.711 codec at typical call lengths. Stereo recording approximately doubles storage usage.
Still Not Sure? #
Start with the plan that covers your current extension count and concurrent call estimate, then expand as needed. All plans support live upgrades — no migrations required for RAM and disk changes.
If you’re deploying for a business with specific uptime requirements or complex network needs, we’re happy to talk through your requirements and recommend a configuration.