Laravel applications often include much more than PHP-FPM. Queues, Horizon, Redis, schedulers, MySQL or PostgreSQL, WebSockets, and build tasks can all run on the same VPS.
The best server size depends on concurrency and background work rather than framework choice alone.
Key takeaways
- 2 GB can run a small Laravel app; 4 GB is a safer general production starting point.
- Queue workers and Horizon can increase memory use substantially.
- Redis and the database should be sized together with PHP workers.
- Deployments can create temporary CPU and memory spikes.
- Keep the application close to its database.
How much RAM for Laravel?
A small application with a modest database and a few workers can fit in 2 GB. Four gigabytes gives more room for PHP-FPM, queues, Redis, database cache, and deployment tasks.
The correct worker count depends on memory per process and request volume.
Queues and Horizon
Background jobs can consume more resources than the web application, especially when processing images, imports, exports, or external APIs. Horizon makes queue operations easier but does not remove the underlying capacity requirement.
Separate workers when jobs begin to interfere with web latency.
Database and Redis
MySQL or PostgreSQL and Redis are common parts of a Laravel stack. On small systems they can share one VPS, but they compete with PHP workers for memory.
As the application grows, moving the database or queue layer can provide independent scaling and isolation.
Deployment and CPU
Composer installs, asset builds, migrations, and container builds can create short bursts. Leave operational headroom so deploying a release does not starve live requests.
Dedicated CPU is usually unnecessary until sustained compute becomes measurable.
Frequently asked questions
Is 2 GB RAM enough for Laravel?
Yes for small applications, but 4 GB is a more comfortable production starting point when queues and databases share the server.
Does Laravel need Redis?
Not always, but Redis is commonly used for cache, sessions, queues, and Horizon.
Should Laravel use Docker?
It can, but Docker is optional. Traditional Nginx, PHP-FPM, systemd, and queue workers also work well.
When should Laravel workers move to another VPS?
When background jobs materially affect web performance or require independent scaling.