Laravel Hosting on Your Own VPS
Laravel with working queues, a real scheduler and Redis — the parts shared hosting cannot provide.
Size a server for Laravel
Every stop is a real configuration you can deploy. Priced per 30 days, billed by the hour, exclusive of 18% GST.
What Laravel is
Laravel is the dominant PHP application framework, and the gap between running it on shared hosting and running it properly is larger than for most PHP software. The framework assumes infrastructure that shared hosting usually will not give you.
Queues are the clearest example. Laravel pushes slow work — email, image processing, API calls — onto a queue processed by a long-running worker. That worker is a persistent process, which shared hosting either forbids or kills. Without it, jobs either never run or fall back to synchronous execution, and the request that was supposed to be fast is not.
The scheduler is the second. Laravel's scheduler expects a single cron entry running every minute, from which it dispatches everything else. Hosts that limit cron to a few runs per day break it. Add Redis for cache and sessions and Horizon for queue visibility, and the requirements are simply those of a normal application server — which is what a VPS is.
Why run Laravel on a VPS
Long-running queue workers under a process supervisor, restarted on failure and on deploy.
A real one-minute cron entry, which is what the scheduler is built around.
Redis for cache, sessions and queues on the same machine.
Composer, artisan and full SSH — deploys stop being an FTP upload.
Choose the PHP version, and change it when the framework requires it.
Laravel features
PHP-FPM tuned for the plan, behind NGINX
Redis for cache, session and queue drivers
Supervisor-managed queue workers
Laravel Horizon for queue monitoring
Scheduler wired to system cron
Composer and artisan over SSH
MySQL or PostgreSQL locally
Recommended server
A starting point for Laravel, not a hard floor — size it on the sliders.
| Memory | 4 GB to start; 8 GB with several queue workers and Redis |
|---|---|
| CPU | 2 vCPU; 4 once workers run alongside web traffic |
| Storage | 40 GB |
| Operating system | Ubuntu 22.04 LTS |
How deployment works
Laravel is deployed with NGINX, PHP-FPM, Redis and a database, with queue workers under Supervisor and the scheduler on a one-minute cron. Workers are restarted on deploy — a worker started before a code change keeps running the old code until it is told otherwise, which is a genuinely confusing bug to chase.
What people run it for
SaaS applications
Background jobs, scheduled tasks and caching all working as designed.
APIs
Laravel or Lumen APIs with predictable worker counts.
Queue-heavy work
Notifications, exports and integrations processed off the request cycle.
Migrating off shared hosting
When queues and the scheduler stopped being optional.
Laravel hosting questions
Related applications
LEMP Hosting NGINX, MySQL and PHP-FPM — lower memory per connection and fast static file serving. 
LAMP Hosting Linux, Apache, MySQL and PHP, with .htaccess support and root over all of it. 
Redis Hosting In-memory cache, sessions and queues, priced as memory rather than per gigabyte. 
Django Hosting Django behind Gunicorn with PostgreSQL and Celery, on a server built for long-running processes. 
Ruby on Rails Hosting Rails behind Puma with Sidekiq and PostgreSQL, on a server with enough memory to matter. Deploy Laravel on your own server
Root access, your choice of size, and no container between you and the application.