ThisCalculator

Everyday

SuiteCRM Server Requirements: What Your VPS Needs

Updated · Standard formula, shown below

SuiteCRM is a popular open-source CRM that you host yourself, and choosing the right VPS resources is the difference between a smooth experience and constant slowdowns. This guide breaks down the minimum and recommended server specifications, explains how SuiteCRM uses each resource, and helps you pick a VPS that fits your team size and workload.

Minimum vs. Recommended Requirements

SuiteCRM officially lists PHP 7.4 or 8.x, MySQL 5.7 or MariaDB 10.x, and Apache or Nginx as its core software stack. For hardware, the official documentation doesn’t give strict numbers, but the community and hosting providers have settled on practical baselines. For a small team (up to 10 users) with light usage, a VPS with 2 CPU cores, 4 GB RAM, and 40 GB SSD storage is the realistic minimum. Below that, you’ll see page loads of several seconds and timeouts during imports.

For a mid-sized team (10–50 users) or if you use email campaigns, reports, or API integrations, step up to 4 CPU cores, 8 GB RAM, and 80 GB SSD. This gives you headroom for database queries and background jobs. For 50+ users or heavy customization, plan for 8+ cores and 16 GB RAM, and consider separating the database onto its own server.

Why SuiteCRM Is Resource-Hungry

Unlike a simple website, SuiteCRM is a PHP application with a MySQL/MariaDB backend that runs hundreds of queries per page view. Every list view, detail view, and dashboard widget triggers multiple database joins and calculations. The default installation also includes a cron-based scheduler for email campaigns, workflow rules, and report generation, which adds load even when no one is logged in.

Another factor is that SuiteCRM builds its UI dynamically. Each user’s role permissions, assigned records, and custom fields affect what gets loaded. The more modules you enable (Leads, Opportunities, Cases, etc.), the more tables and queries are involved. This is why a server that comfortably runs a WordPress site often struggles with SuiteCRM.

Key Components: CPU, RAM, Storage, and Bandwidth

Here’s how each VPS resource affects SuiteCRM performance:

  • CPU: Handles PHP processing and database query execution. More cores help with concurrent users and background cron jobs. A single-core VPS will bottleneck quickly.
  • RAM: PHP workers and MySQL both cache data in memory. 4 GB is the sweet spot for small installs; 8 GB lets MySQL cache more of your database, dramatically speeding up repeated queries.
  • Storage: Use SSD, not HDD. SuiteCRM reads and writes many small files (uploads, cache, logs). An SSD gives 10–20x faster I/O, which directly reduces page load times. 40 GB is enough for the software plus a few thousand records; plan 80+ GB if you store attachments or email archives.
  • Bandwidth: Not usually a bottleneck unless you run mass email campaigns from the server. If you do, check your VPS provider’s monthly transfer limit—sending 10,000 emails with attachments can consume several GB.

How to Choose the Right VPS Plan

Start by estimating your user count and the intensity of use. A sales team that logs calls and emails all day creates more load than a small admin team that checks records occasionally. Also consider whether you’ll use SuiteCRM’s built-in email client, which polls mail servers and stores messages, increasing both storage and CPU usage.

When comparing VPS plans, look at the burst vs. sustained CPU. Some providers advertise high cores but throttle after a few minutes. For SuiteCRM, sustained performance matters more than burst. Check the provider’s fair-use policy and look for plans with dedicated CPU or at least a clear allocation.

Finally, choose a provider that offers easy scaling. You’ll likely start small and upgrade as your team grows. A VPS that lets you add RAM or CPU without migrating is a big advantage. Also verify the provider supports your preferred OS (Ubuntu 22.04 LTS is a common choice) and has good documentation for installing PHP and MySQL.

Common Performance Problems and Fixes

If your SuiteCRM runs slowly, the first thing to check is MySQL’s slow query log. Long-running queries often come from missing indexes on custom fields or from large list views. Adding indexes to frequently searched fields can cut query time by 90%.

Another common issue is PHP memory limit. If you see white screens or “Allowed memory size exhausted” errors, increase memory_limit in your php.ini to at least 256 MB, and ideally 512 MB. Also check max_execution_time—set it to 300 seconds for cron jobs and large imports.

Cache configuration matters too. Enable OPcache for PHP and ensure SuiteCRM’s cache directory is writable. If you use a reverse proxy like Nginx, enable caching for static assets. For large installations, consider moving the cron job to run every 5 minutes instead of every minute, and stagger heavy reports to off-peak hours.

VPS vs. Shared Hosting vs. SuiteCRM Cloud

Shared hosting almost always fails for SuiteCRM because it limits PHP processes and memory, and other tenants on the server can degrade your performance. A VPS gives you dedicated resources and root access to tune PHP and MySQL. The trade-off is that you must manage the server yourself—updates, security patches, and backups are your responsibility.

SuiteCRM also offers an official cloud hosting service, which handles all administration and scaling, but it costs more per month than a comparable VPS. If you have the technical skills or a managed VPS provider (where the host handles the OS), a VPS is the most cost-effective option. Managed VPS plans cost more than unmanaged ones but save you time and reduce the risk of misconfiguration.

Costs and Budgeting

An unmanaged VPS with 4 GB RAM and 2 CPU cores typically costs between $10 and $20 per month from major providers. Managed VPS plans with the same specs run $30–$50 per month. Add the cost of a domain name (around $10/year) and an SSL certificate (free via Let’s Encrypt).

Don’t forget backup costs. Many providers charge extra for off-site backups, or you can use a free tool like Rclone to copy your database and files to object storage. The cost of downtime is usually higher than the cost of a slightly beefier server, so avoid the cheapest plan if you rely on SuiteCRM for daily operations.

Frequently Asked Questions

Can I run SuiteCRM on 2 GB RAM?

Technically yes, but only for a single user or very light testing. With 2 GB, PHP workers and MySQL will compete for memory, causing frequent swapping to disk and slow page loads. You’ll also hit memory limits during imports or when running reports. For any real production use, 4 GB is the minimum.

Is MySQL or MariaDB better for SuiteCRM?

Both work well. MariaDB is a drop-in replacement for MySQL and is often faster due to better query optimization. If your VPS provider offers MariaDB 10.4 or newer, it’s a solid choice. Just make sure you use InnoDB as the storage engine, not MyISAM, for reliability.

Does SuiteCRM need a dedicated IP address?

No, but it helps. A dedicated IP makes it easier to set up SSL and avoid blacklisting issues if you send emails from the server. Shared IPs work fine for most installations, but if you run email campaigns, a dedicated IP gives you better control over your sender reputation.

How much storage do I need for 10,000 records?

SuiteCRM stores each record as a row in the database, plus files for attachments. A rough estimate: 10,000 records with basic fields use about 500 MB of database storage. If you attach files or emails, that can grow to several GB. Start with 40 GB and monitor your usage.

Can I use Docker to run SuiteCRM on a VPS?

Yes, Docker is a convenient way to deploy SuiteCRM with all dependencies. However, it adds a layer of abstraction that can complicate performance tuning and backups. If you’re comfortable with Docker, use the official images and ensure your data volumes are persistent. Otherwise, a traditional LAMP stack is simpler to troubleshoot.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.