Server Size Calculator
How big should your RingQ PBX server be? Enter your extensions, how many calls happen at the same time at your busiest, and how much you record. You get the vCPU, memory and disk to run smoothly at peak, with room to spare.
Based on RingQ capacity tests, November 3, 2026.
Common server sizes
Measured sizes for a RingQ PBX with desk phone calls. Recording space assumes half of calls recorded over a 9 hour day.
| Calls at the same time | Extensions | vCPU | Memory | Recordings per month |
|---|---|---|---|---|
| 50 | up to 250 | 2 | 8 GB | 264 GB |
| 100 | up to 500 | 4 | 8 GB | 528 GB |
| 300 | up to 1,200 | 8 | 8 GB | 1.6 TB |
| 500 | up to 2,000 | 8 | 16 GB | 2.6 TB |
| 1,000 | up to 4,000 | 16 | 32 GB | 5.3 TB |
Where the numbers come from
We load tested a 4 vCPU RingQ server by adding calls until it started to strain at 280 calls. That gives about 224 safe calls, or 56 per vCPU.
Why 80%
We recommend a size where your busiest hour uses no more than 80% of the server's limit, so calls stay clear during spikes, backups and updates.
Already on RingQ?
Run the Capacity test in Settings on your own server. It measures your real limit and tells you if you need more CPU, memory or disk.
Ready to set up your server?
Install RingQ on AWS, DigitalOcean, Google Cloud or Azure. Estimates only: video meetings, queues and integrations can change what you need.