Maskinvarukrav för 3CX: RAM, CPU, lagring och samtidiga samtal
Planera 3CX-hårdvara för vCPU, RAM, SSD-lagring, anknytningar, inspelningar, nätverkskapacitet och en deployment-topologi som stöds.
3CX hardware requirements at a glance
Size 3CX from verified upstream requirements first, then add headroom for workload and persistent data.
- RAM
- Small PBX tier: 4 GB; larger tiers rise to 8 GB, 16 GB, and 32+ GB
- CPU
- Small PBX tier: 2 vCPU with a modern Core i3-class baseline
- Storage
- At least 40 GB for base system; current PBX table starts at 80 GB SSD for Small
- Network
- At least 1Gb LAN; 10Gb is required for 1000+ extensions
- Deployment constraint
- Dedicated supported Windows or Debian-based instance
- Best Zima path
- Dedicated VM rather than direct Custom App container
From official requirements to the right setup
Start with current upstream facts for 3CX, then size the actual workload rather than copying generic container or app-store labels.
-
Official requirements
-
Confirm your needs
-
Leave room to grow
-
Run it on ZimaOS
Check every playback client
- Extension count
- Concurrent calls
- Queues/group calls
- Recording retention
- Voicemail retention
- Backup retention
- 1Gb/10Gb networking
- Dedicated VM resources
Official minimum requirements
3CX publishes numerical hardware guidance by deployment tier, so these numbers can be used directly as official sizing references.
For the Small PBX tier, 3CX lists 2 vCPU, 4 GB RAM, and 80 GB SSD. It also requires at least 40 GB for the base installation and additional storage for recordings, voicemail, logs, and backups.
| Requirement | Official minimum | What this supports |
|---|---|---|
| 2 vCPU; Core i3 13th Gen+ or equivalent family | Current small Linux/Windows PBX baseline. | |
| 4 GB | Current small PBX table. | |
| 80 GB SSD | Current small PBX table. | |
| At least 40 GB | Additional space is required for backup, voicemail, recordings, and logging. | |
| At least 1Gb | 10Gb required for 1000+ extensions. | |
| Required | 3CX's Debian installer states the instance must be dedicated to 3CX. | |
| Not required | No GPU requirement for the PBX. |
When to upgrade your hardware
More extensions/calls
Recording growth
Network scale
Plan hardware growth with confidence
Dedicated SSD VM storage
Use SSD-backed storage for the dedicated 3CX VM.
SSD/NVMeMore VM RAM
Allocate RAM according to the official Small/Medium/Large/Enterprise tier.
Tier-appropriate RAMRecording/backup capacity
Add storage outside the base PBX allocation for recordings, voicemail, logs, and backups.
Additional SSD/HDD capacityNetwork upgrade
Use 1Gb minimum and 10Gb for 1000+ extension scale.
1Gb/10Gb EthernetCan it run on ZimaOS?
Custom install path is not a supported direct-container recommendation
No specific ZimaOS one-click 3CX app page was verified, and upstream requires a dedicated supported instance. Do not deploy 3CX as an ordinary shared Custom App container.
Custom install 3CX in the ZimaOS app ↗Prefer a dedicated Linux or Windows VM
Use a dedicated supported VM/instance and allocate resources according to the official 3CX tier.
Open 3CX Debian installation guidance ↗Follow the official hardware table
Use extension/call scale, recordings, and networking to select the right tier.
Open 3CX hardware requirements ↗Zima hardware for 3CX
3CX is a special-case workload: the right Zima hardware is the hardware capable of hosting a dedicated VM that meets 3CX's published PBX tier.
Choose by workload
Allocate at least the official Small tier to the VM and leave host overhead outside it.
Follow the next official 3CX tier rather than extrapolating from home-server rules.
Direct ZimaOS container deployment should be treated as unsupported/non-recommended unless 3CX explicitly documents such a topology in the future.
| Zima hardware | Best for | Example workload | Core configuration | Recommended boundary | Next step |
|---|---|---|---|---|---|
| ZimaCube 2 Pro | CPU-heavier, database-heavier, and higher-concurrency workloads | Larger SQL/search workloads, many users, or broader server consolidation |
|
16 GB RAM can still constrain very large AI or enterprise workloads | Get Now |
What the Press Says
Highlights from trusted reviewers worldwide.
“ZimaCube 2: Not just another NAS, tested with 25TB storage, local AI agents, 4K transcoding, and real homelab workflows.”Read full review
“The ZimaBoard 2 is a compact x86 server board that can be turned into a mini NAS, home server, media box, or self-hosting hub.”Read full review
“ZimaCube 2: A modern, high-performance NAS with plenty of room to grow—built for users who want more than basic storage.”Read full review
“Coverage focused on ZimaCube 2's open hardware foundation, no monthly fee, and self-hosting flexibility.”Read full review
Loved by the Community
Stories and reviews from people who build with Zima every day.
Zima Blade Little yet Powerful
Maybe I am not digital natives but I live with PCs since 12 years old in 1984 when IBM PC clone come to my home. Many years have passed and many operating system I've tried. For me Zima blade and CasaOS was a quantum leap for home PC enthusiast and server lab machine to make me stay curious and relevant for this era.
Very good!!
I use ZimaCube Pro as 5th Proxmox cluster node. It runs several VMs and containers, including a VM with GPU passthrough to run a self-hosted LLM. A specific LXC container runs a Samba server for NAS capabilities using four of six RAID 6 SATA HDDs with ZFS.
Great innovation for mini server!
It is very useful and makes a powerful mini server for many purposes, including university and college students in engineering and electronics. Thank you so much for making this server.
Avaliação ZimaBoard 2
Construí um servidor de uso pessoal. O desempenho está muito bom e funciona perfeitamente onde quer que eu esteja. A surpresa é não dependermos de grandes estruturas para termos nosso próprio servidor de dados. Como iniciante, estou gostando bastante do ZimaOS, pois ele é simples e eficiente.
Frequently asked questions
How much RAM does a small 3CX PBX need?
The current official Small tier lists 4 GB RAM.
How many vCPUs does a small 3CX PBX need?
The current official Small tier lists 2 vCPU.
How much storage does 3CX need?
3CX requires at least 40 GB for the base installation; the current Small PBX table lists 80 GB SSD.
How much space do recordings use?
3CX states that one minute of recorded audio is approximately 1 MB.
What network speed does 3CX require?
At least 1Gb LAN is required; 10Gb is required for 1000+ extensions.
Can I run 3CX as a normal ZimaOS Docker app?
That is not the supported topology documented by 3CX. The Debian guide requires a dedicated instance.
Does 3CX need a GPU?
No.
What is the recommended ZimaOS topology?
Use a dedicated VM that meets the official 3CX hardware tier rather than a shared Custom App container.
