Laravel hosting with queues and the scheduler: the options compared
A Laravel app in production is three processes: the web server, a queue worker that is restarted on every deploy, and the scheduler run every minute. On Livops the web app runs from a push with APP_KEY generated and migrations run, for 39 credits a month (39,000 so'm), and the worker and the scheduler are services of their own at 19 credits each. Here is how Render, Railway, Fly.io and a VPS compare.
By Livops team, the people who build and run LivopsUpdated
Most Laravel hosting comparisons price one web server. A real Laravel app is usually three processes: the web server, a queue worker for the jobs it dispatches, and the scheduler, which has to run every minute. This page covers what Laravel itself asks of each, compares Render, Railway, Fly.io and a VPS on all three with each provider’s own numbers, and ends with exactly how Livops runs them.
What does a Laravel app need in production?
PHP, with public/ as the web root
Laravel 13 needs PHP 8.3 or newer and the usual extensions[1]. The web server must send every request to public/index.php; serving the project’s top folder would expose its configuration files[1]. FrankenPHP does this with one command, frankenphp php-server -r public/[1]. Laravel also writes to storage and bootstrap/cache, so those two folders must be writable[1].
Configuration cached, keys from the environment
php artisan optimize caches the configuration, events, routes and views, and belongs in every deploy[1]. Once the configuration is cached the .env file is not loaded, so env() may only be called inside config files[1]. APP_DEBUG must be false in production, or error pages expose configuration values[1]. And APP_KEY must be set before the first page is served.
Behind a proxy, trusted
A platform terminates HTTPS in front of the app, and Laravel then sometimes generates http:// links; the fix is the TrustProxies middleware[4]. When you do not know the proxies’ addresses, trust all of them in bootstrap/app.php[4]:
->withMiddleware(function (Middleware $middleware): void {
$middleware->trustProxies(at: '*');
})
A queue worker that is restarted on every deploy
New apps use the database queue connection, whose jobs table comes in Laravel’s default migrations[2]. php artisan queue:work processes the jobs, and a process monitor such as Supervisor keeps it running[2]. Workers are long-lived and keep the booted app in memory, so they do not notice new code until they are restarted on deploy[2]. --tries=3 caps the attempts per job, and --max-time=3600 makes a worker exit after an hour so it starts fresh[2]. On SIGTERM a worker finishes its current job before it exits[2].
php artisan queue:work --tries=3 --max-time=3600
The scheduler, every minute
Laravel’s scheduler needs a single cron entry that runs php artisan schedule:run every minute[3]. schedule:work runs the same scheduler in the foreground, and Laravel documents it for running the scheduler locally[3]. If the scheduler could run in two places at once, onOneServer keeps a task to one of them, and needs a database, Memcached, DynamoDB or Redis cache[3].
The options at a glance
The cost of the web app, a worker and the scheduler together is what to compare.
| Option | What it is | Web app | Queue worker | Scheduler | What you still maintain |
|---|---|---|---|---|---|
| Livops | A platform; servers in Uzbekistan | 39 credits (39,000 so’m) a month | 19 credits a month | 19 credits a month | Your code |
| A VPS in Uzbekistan | A virtual machine with root | 82,000 so’m a month for all three: 1 vCPU, 2 GB, 30 GB HDD (SmartCloud)[5] | On the same machine | On the same machine | PHP, the web server, Supervisor, cron, HTTPS, the database, backups |
| Railway | A platform billed by usage | Hobby plan: $5 a month, including the same amount of usage; then about $10 per GB of RAM and $20 per vCPU a month[6] | Billed by the same usage | Billed by the same usage | Your code |
| Render | A platform | $7 a month: 0.5 CPU, 512 MB[7] | $7 a month as a background worker[7] | A cron job from $0.00016 a minute while it runs, at least $1 a month[7][8] | A Dockerfile: PHP is not among Render’s native runtimes[7] |
| Fly.io | Virtual machines billed by the second | $2.19 a month for 256 MB; $3.69 for 512 MB[10] | Another machine at the same prices | Another machine at the same prices | Your code |
Other providers’ prices are from each provider’s own page, read on 20 November 2026; the dates are in Sources below. Livops prices are the ones the cabinet bills today.
Each option
Livops
The web app is set up from the repository: PHP from composer.json, Composer and the front-end build, APP_KEY, migrations and the config cache (details below). The worker and the scheduler are two more services from the same repository. Payment is in so’m through Payme or Click, with no card, and the servers are in Uzbekistan — close to users there, farther from users elsewhere. Three services cost more than one VPS; and you get no root.
A VPS
For a Laravel app with a worker and a scheduler, a VPS is the cheapest option by far: all three run on one 82,000 so’m machine[5], beside MySQL or PostgreSQL. In exchange, you set up PHP-FPM and Nginx, a Supervisor program for queue:work, the crontab line, a certificate, backups, and a deploy script that restarts the workers. Laravel Forge exists to do exactly that for you on your own server[1].
Railway
Every process is a service billed by the same usage: memory about $10 per GB and CPU about $20 per vCPU a month, after the $5 Hobby plan’s included usage[6]. It is paid by credit card[6].
Render
A web service and a background worker are $7 a month each for 512 MB; a cron job is billed by the minute it runs, with a $1 monthly minimum, and stopped after 12 hours[7][8]. At most one run of a cron job is active at a time[8], which suits schedule:run. PHP is not one of Render’s native runtimes, so a Laravel app runs from your own Docker image[7].
Fly.io
The cheapest machine is $2.19 a month for 256 MB and $3.69 for 512 MB, billed by the second[10]. A worker is one more machine; Managed Postgres starts at $38 a month[10]. A card is needed once the trial ends[10].
VPS or platform: what do you maintain?
Laravel is where this choice is closest. On a VPS the three processes share one machine, and Supervisor and cron are a few lines of configuration you write once — but every deploy must restart the workers, and the server’s updates, disk and certificate are yours. On a platform each process is a service that is deployed, restarted and logged on its own; you pay per process and give up root.
Where can you run Laravel for free?
- Livops has no free tier for apps, workers or cron jobs. On an account that has not paid yet, the first bot or app runs for 15 minutes on a zero balance, once. One 500 MB database per team is free, and starts once the account has credits.
- Render gives free instances to web services, PostgreSQL and Key Value, not to background workers or cron jobs; a free web service spins down after 15 minutes without inbound traffic[9].
- Railway has a Free plan with $1 of usage a month and up to 0.5 GB per service, whose services sleep after 5 to 10 minutes without outbound traffic; a trial gives $5 of credit for 30 days, with no card[6].
- Fly.io has no free tier for new organizations; a trial gives $1 of credit for 7 days[10].
Laravel on Livops
The web app
- Push the repository. In the cabinet, click New project and choose it, or upload the folder as a
.zip. - Under Databases, add PostgreSQL or MySQL.
DB_CONNECTION,DB_HOST,DB_PORT,DB_DATABASE,DB_USERNAMEandDB_PASSWORDare written into every service in the environment. - Deploy. The log shows Composer, the front-end build, the migration and the start.
Livops makes it a Laravel project when artisan sits beside composer.json and there is no Dockerfile. It installs with composer install --no-dev --optimize-autoloader --no-interaction, then runs npm ci (or npm install without a lock file) and npm run build when there is a package.json. The PHP version is the one require.php in composer.json allows: 8.2, 8.3, 8.4 or 8.5, and 8.3 when it says nothing. When the project is created, APP_KEY is generated and saved as a secret variable, unless you gave one. The start command:
export SESSION_DRIVER=${SESSION_DRIVER:-cookie} CACHE_STORE=${CACHE_STORE:-file} LOG_CHANNEL=${LOG_CHANNEL:-stderr}; php artisan migrate --force; php artisan optimize >/dev/null 2>&1 || true; exec frankenphp php-server --listen :${PORT:-3000} --root public/
- The defaults — sessions in a cookie, the cache in files, logs to the Logs tab — are used only for variables you have not set. Set
CACHE_STORE=databaseorredisyourself if you needonOneServeror shared locks. migrate --forceruns before the config is cached, on every start; without a database it fails at once and the server starts anyway.optimizeruns as the app starts, with the project’s variables in place, so the cached config has your values, not the build’s.- Proxy headers: the platform’s proxy sends
X-Forwarded-Proto: https. Add thetrustProxies(at: '*')line above, or Laravel may buildhttp://links. - Health: put
"healthPath": "/up"inlivops.jsonand a new version counts as started only once Laravel’s health route answers. - If the new version does not answer within a minute, the deploy fails and the version that worked keeps serving; if the build fails, the running version is left alone. Recent versions stay in Deploys for a one-click rollback.
The queue worker and the scheduler
Each is one more service from the same repository, and each is deployed by the same git push as the web app, so a worker never keeps running old code. The cabinet’s new-project form makes a Laravel repository a web app and does not offer another type for it, so these two are added with the type set:
- from an MCP client connected to Livops (Claude Code, Cursor, Codex CLI), with
add_stack_serviceandkindset toworkerorcron; see MCP. Then set the Start command in the service’s settings and, for cron, its Schedule; - or with
kindandstartin alivops.jsonthat is in the repository when that service is created. A service that already exists keeps its own type, and its build log notes the difference.
| Service | Type | Start command | Schedule |
|---|---|---|---|
| Queue worker | worker |
php artisan queue:work --tries=3 --max-time=3600 |
— |
| Scheduler | cron |
php artisan schedule:run |
* * * * * |
The shortest cron interval on Livops is one minute, which is exactly what schedule:run needs, and the schedule is read in UTC. Two variables to set once:
APP_KEY. Every Laravel service created from the repository gets its own generated key. Give the worker and the scheduler the web app’s, so they decrypt what it encrypts: under their Variables, makeAPP_KEYa reference to the web service’sAPP_KEY— typing a dollar sign and two braces in the value starts one; see References.LOG_CHANNEL=stderr. The defaults above belong to the web app’s start command only. As a shared variable of the environment it reaches the worker and the scheduler too, and their output shows in their Logs.
What it costs
The web app is 39 credits a month (39,000 so’m); a worker and a cron service are 19 credits a month each. One credit is 1,000 so’m, and bought credits never expire. See Pricing for plans, and Cron and workers for the schedule syntax.
Questions
Does Livops generate APP_KEY?
Yes. When a Laravel project is created, Livops generates APP_KEY the way key:generate does, base64 and 32 random bytes, and saves it as a secret variable, unless you gave a value. A project built from your own Dockerfile gets none; set it under Variables.
Are migrations run on deploy?
Yes. The start command runs php artisan migrate --force before it caches the config and starts the server. If there is no database yet, the migration fails at once and the server starts anyway.
How do I run the queue worker?
As a second service from the same repository, of type worker, with php artisan queue:work as its start command. It costs 19 credits a month, and every push to its branch deploys it again with the new code, so it never keeps running yesterday's classes.
How do I run the Laravel scheduler?
As a service of type cron with the schedule * * * * * and the start command php artisan schedule:run, which is the one cron entry Laravel asks for. Livops' shortest interval is one minute, which is what the scheduler needs. The schedule is read in UTC.
Which database does Laravel get?
Add PostgreSQL or MySQL to the project and DB_CONNECTION, DB_HOST, DB_PORT, DB_DATABASE, DB_USERNAME and DB_PASSWORD are written into every service in the environment, the worker and the scheduler included. Redis arrives as REDIS_URL.
Which PHP version does it run?
The one composer.json asks for in require.php: 8.2, 8.3, 8.4 or 8.5. With no constraint, 8.3. Laravel 13 needs PHP 8.3 or newer.
Who wrote this comparison?
The Livops team. Every price and limit of another provider on this page links to that provider's own page, with the day we read it.
Sources
- Laravel 13.x — Deployment (laravel.com). Checked .
- Laravel 13.x — Queues (laravel.com). Checked .
- Laravel 13.x — Task Scheduling (laravel.com). Checked .
- Laravel 13.x — HTTP Requests (trusted proxies) (laravel.com). Checked .
- SmartCloud — VDS plans (smartcloud.uz). Checked .
- Railway — Pricing (railway.com). Checked .
- Render — Pricing (render.com). Checked .
- Render — Cron jobs (render.com). Checked .
- Render — Deploy for free (render.com). Checked .
- Fly.io — Pricing (docs.fly.io). Checked .
Put your project online today
Connect GitHub or drop a folder. No card is asked for.
Deploy your Laravel appRelated
- Laravel: No application encryption key has been specifiedLaravel's encrypter has no key, because the APP_KEY environment variable is empty on the server. Generate one with php artisan key:generate --show, set it as APP_KEY where the app runs, clear any cached configuration, and keep the same key from then on.
- App not listening on $PORT: why the health check failed after deployThe platform started your app, tried the port it gave it, and nothing answered in time. Almost always the app listens on its own fixed port instead of the PORT variable, listens on localhost (127.0.0.1) instead of 0.0.0.0, or crashed or was still starting when the check gave up. Listen on 0.0.0.0 and the port in PORT, and it passes.
- Next.js hosting without Vercel: the options comparedNext.js runs on any host that runs Node: next build, then next start, and every feature works, Server Actions and image optimization included. On Livops a repository with next in package.json runs as a server from a push for 39 credits a month (39,000 so'm), and a static export is free. Here is how Vercel, Render, Railway, Fly.io and a VPS compare.
- Django hosting in 2026: how to deploy a Django app, and whereA Django app in production needs a WSGI or ASGI server instead of runserver, DEBUG off, ALLOWED_HOSTS set, collected static files and migrations on every deploy. On Livops a repository with manage.py and requirements.txt gets all of that from a push, for 39 credits a month (39,000 so'm). Here is how Render, Railway, Fly.io and a VPS compare.