Layer 5 · self-hosting reality check
What it actually takes to self-host SuiteCRM
The docs say not stated by the vendor. Community guidance puts a test or development machine at 3 GB of RAM and about 10 GB of disk, with PHP's memory_limit at 256 MB or more.. In practice you want 4 GB. Even a test box is quoted at 3 GB, and production adds MySQL, the cron and, from 8.10, a Messenger worker.. Here is the honest version — real requirements, real monthly cost, what you will be maintaining, and the one thing that catches people out.
Usually reached from Salesforce alternatives, where SuiteCRM is one of the picks.
Wondering whether you need to at all? Is Salesforce free? — what the free tier actually allows, and where the wall is.
| RAM — documented minimum | not stated by the vendor. Community guidance puts a test or development machine at 3 GB of RAM and about 10 GB of disk, with PHP's memory_limit at 256 MB or more. |
|---|---|
| RAM — what it really needs | 4 GB. Even a test box is quoted at 3 GB, and production adds MySQL, the cron and, from 8.10, a Messenger worker. |
| CPU | 2 vCPU; not stated by the vendor |
| Disk | About 10 GB for a test install; production grows with uploaded documents, email attachments and the MySQL database |
| Monthly cost | $12–24/mo for a 10-user instance on a 4 GB VPS |
| Setup time | Half a day by hand on a LAMP box; there is no official one-command install |
| How you install it | Release zip onto Apache 2.4 with PHP 8.2–8.4 and MySQL 8 or MariaDB 10.6+, the DocumentRoot pointed at /public with mod_rewrite on, then the installer, the cron and, on 8.10+, a Messenger worker under Supervisor. There is no official Docker image. |
| Ongoing maintenance | An upgrade roughly every six months to stay supported, each through the command-line upgrader with permission and cache fixes afterwards. You also keep the cron and the Messenger worker running as the web server user. |
| Where it stops scaling | A 4 GB box suits a small team. The vendor publishes no sizing, so MySQL goes on its own host first, with PHP's memory_limit raised to 512 MB as data grows. |
The thing that catches people out
SuiteCRM 8 releases stop being supported as soon as the next one ships, with no security-only period: 8.9 came out in September 2025 and went end-of-life in April 2026. Self-hosting it means running the command-line upgrader about twice a year. There is no official Docker image to make that easier, and the Bitnami image most guides pointed to is now a frozen 'legacy' image. Plan on a normal VPS install, keep a staging copy to rehearse each upgrade, and on 8.10+ remember the new Messenger worker, without which bulk exports and some migrations sit at 'Pending' forever.
When not to self-host SuiteCRM
You want a CRM a non-specialist can keep running: EspoCRM is lighter and has an install script. Also skip it if you cannot commit to twice-yearly upgrades; a hosted CRM will serve you better.
Every guide here carries this section. A site that only ever tells you to self-host is selling something — the useful answer is sometimes no.
Other Layer 5 self-hosting guides
- Self-hosting LibreOffice2 GB with a large spreadsheet open
- Self-hosting ONLYOFFICE6 GB for the Document Server with a handful of concurrent editors
- Self-hosting Collabora Online4 GB, and roughly 1 GB per 20 concurrent documents
- Self-hosting CryptPad2 GB for a small instance
- Self-hosting Mattermost4 GB for a team of 50 with PostgreSQL on the same box
- Self-hosting Rocket.Chat6 GB with MongoDB on the same machine
Common questions
- How much RAM does SuiteCRM actually need?
- 4 GB. Even a test box is quoted at 3 GB, and production adds MySQL, the cron and, from 8.10, a Messenger worker. in practice. The documented minimum is not stated by the vendor. Community guidance puts a test or development machine at 3 GB of RAM and about 10 GB of disk, with PHP's memory_limit at 256 MB or more., which is the figure at which the process starts rather than the figure at which it works under real use. 2 vCPU; not stated by the vendor alongside it.
- What does self-hosting SuiteCRM cost per month?
- $12–24/mo for a 10-user instance on a 4 GB VPS This is commodity VPS pricing and excludes your time, which is the larger cost for most people — budget for an upgrade roughly every six months to stay supported, each through the command-line upgrader with permission and cache fixes afterwards. You also keep the cron and the Messenger worker running as the web server user.
- How long does it take to set up SuiteCRM?
- Half a day by hand on a LAMP box; there is no official one-command install, via Release zip onto Apache 2.4 with PHP 8.2–8.4 and MySQL 8 or MariaDB 10.6+, the DocumentRoot pointed at /public with mod_rewrite on, then the installer, the cron and, on 8.10+, a Messenger worker under Supervisor. There is no official Docker image..
- When should I NOT self-host SuiteCRM?
- You want a CRM a non-specialist can keep running: EspoCRM is lighter and has an install script. Also skip it if you cannot commit to twice-yearly upgrades; a hosted CRM will serve you better.
- What is the most common mistake when self-hosting SuiteCRM?
- SuiteCRM 8 releases stop being supported as soon as the next one ships, with no security-only period: 8.9 came out in September 2025 and went end-of-life in April 2026. Self-hosting it means running the command-line upgrader about twice a year. There is no official Docker image to make that easier, and the Bitnami image most guides pointed to is now a frozen 'legacy' image. Plan on a normal VPS install, keep a staging copy to rehearse each upgrade, and on 8.10+ remember the new Messenger worker, without which bulk exports and some migrations sit at 'Pending' forever.