Deploy Laravel to your own server without Forge.
Ployz deploys your Laravel app from GitHub to a server you rent, with no Dockerfile and no monthly fee. It runs the web app on FrankenPHP, your queue worker and the scheduler, adds MySQL or Postgres in one click, and runs php artisan migrate --force before every deploy. Your coding agent can run all of it, and deleting a database waits for you.
The same Laravel app, five bills.
A small Laravel app (web, a queue worker, MySQL and Redis on one 4 GB server) costs $19 a month with Forge on Hetzner, $36 with Forge on DigitalOcean and $32 on Laravel Cloud. On the same Hetzner server with Ployz it's $7, because Ployz is free on any number of servers. For the small app, Forge's $12 Hobby fee is most of the bill.
| Monthly bill | Small app | Medium app | With database backups |
|---|---|---|---|
| Forge + Hetzner (Europe) | $19 | $31 | $46 (Business plan) |
| Forge + DigitalOcean | $36 | $108 | $63 (Business plan) |
| Forge + Laravel VPS | $37 | $112 | $60 (Business plan) |
| Laravel Cloud (US East, always on) | $32 | $144 | Daily MySQL backups, billed with storage |
| Your own server + Ployz | $7 | $19 | $7: a restore point for every database is included |
The small app is a 1 GB app with its own queue worker, 1 GB MySQL and Redis; the medium one is a 4 GB app, a 1 GB worker, 4 GB MySQL and Redis on a 16 GB server. Every number, with its source, is in Laravel Forge pricing and Laravel Cloud pricing. Hetzner's CX servers are in Germany and Finland only. In the US, a DigitalOcean Droplet or Netcup's Manassas datacenter is the cheap option; see Hetzner vs DigitalOcean.
How to deploy Laravel to a VPS without Forge.
A Laravel app in production is four pieces: PHP behind a web server, php artisan queue:work kept running, the scheduler, and a database. Forge sets those up on your server with Nginx, Supervisor and a cron entry. Ployz runs each one as a service on your server instead, built from your repository.
$ curl -fsSL https://ployz.sh | sh
Installs the ployz CLI on macOS or Linux.
$ ployz login
Signs in to Ployz Cloud in your browser.
$ ployz up --server root@your-server
Installs Ployz on the server, builds this directory with no Dockerfile and gives it an HTTPS address.
Or paste Read ployz.dev/agents.md and deploy this repo to my server. into Claude Code, Codex or Cursor and it runs these steps for you. Then finish the app in the dashboard:
- Rent a server. Any provider works. Pick Ubuntu LTS, and give it 4 GB of RAM for the app, a worker and MySQL; builds run on the server too.
- Connect GitHub so every push deploys: add the repository as a service (Deploy from GitHub).
- Add the database. Click Create, then Database, then MySQL or PostgreSQL.
- Set the variables on the web service.
DB_CONNECTIONismysqlorpgsql, andDB_URLis a reference:${{ mysql.MYSQL_URL }}or${{ postgres.DATABASE_URL }}. AddAPP_KEY(fromphp artisan key:generate --show) as a sealed secret,APP_ENV=productionandAPP_DEBUG=false. SetDB_CONNECTIONbefore the first deploy: the build reads it to install the PDO driver. - Run migrations before each deploy. Set the pre-deploy command to
php artisan migrate --force, and setRAILPACK_SKIP_MIGRATIONS=trueso the web replicas don't migrate again as they start. - Set the health check to
/up, Laravel's built-in health route. With it, a new version must answer before the old one stops. - Add the queue worker. Add a second service from the same repository with the start command
php artisan queue:work --tries=3. Usephp artisan horizoninstead if you run Horizon on Redis. - Add the scheduler. One more service from the same repository, with the start command
php artisan schedule:work, and one replica. - Point your domain at the server, or keep the generated HTTPS address.
From then on, git push builds and deploys, and every pull request gets its own preview.
What Railpack does with a Laravel app.
Ployz builds with Railpack, so you don't need a Dockerfile. It finds Laravel by the artisan file and does what Laravel's deployment guide asks for:
- PHP and Composer. It reads the PHP version from
composer.json(8.2 and up, 8.4 by default), installs your Composer dependencies, and installs the PHP extensions Laravel needs plus anyext-*incomposer.json. - Vite. With a
package.json, it installs Node and runs your build script, sonpm run buildships your assets inside the image. - The web server. It serves
public/with FrankenPHP on the port Ployz gives the service. - On start, the web container runs
storage:linkandphp artisan optimize, which caches config, events, routes and views.
Your own Dockerfile works too: set Build method to Dockerfile. Either way the worker and scheduler run the same image as the web app, so they always have the same code.
Why the scheduler gets its own service. Laravel's scheduler needs something to run schedule:run every minute, which is what Forge's cron entry does. php artisan schedule:work "will run in the foreground and invoke the scheduler every minute until you terminate the command", so it runs as a service like any other. Keep it at one replica, or every replica runs each task. If you scale it anyway, Laravel's onOneServer() takes a lock in your cache so a task runs once.
Why migrations go in the pre-deploy command. Railpack's Laravel start script runs php artisan migrate --force in every web container as it starts. With two replicas, two migrations race. The pre-deploy command runs once with the new code before any replica is replaced, and if it fails, the deploy stops and the old version keeps serving.
Do you need Redis? Not for queues. New Laravel apps default to the database queue connection, which keeps jobs in a table of your database. Add Redis in one click if you use Horizon or want Redis for cache and sessions.
Uploads. A container's disk is replaced on every deploy. Put user uploads on S3-compatible storage, or attach a volume at storage/app; a service with a volume runs one replica.
Ployz, Forge and Laravel Cloud.
| What you need | Laravel Forge, Laravel Cloud | Ployz on your server |
|---|---|---|
| What you pay | Forge: $12, $19 or $39 a month, plus the server. Cloud: $5 or $20 a month, plus usage | The server. Ployz is free on any number of servers, custom domains included |
| Builds | Forge runs your deploy script (git pull, composer install) on the server. Cloud runs your build commands | No Dockerfile needed (Railpack runs Composer, your Vite build and the artisan caches), or bring your own Dockerfile |
| Queue worker | Forge: Supervisor on the server. Cloud: managed queues, billed per worker-hour | A service running `php artisan queue:work`, sharing the server's RAM |
| Scheduler | Forge: a cron entry. Cloud: built in | A service running `php artisan schedule:work`, with one replica |
| Migrations | Forge: a line in your deploy script. Cloud: a deploy command | A pre-deploy command, `php artisan migrate --force`, runs once before each deploy |
| Databases | Forge installs MySQL or Postgres on the server. Cloud sells Laravel MySQL from $6.60 and serverless Postgres | One-click MySQL, Postgres and Redis on your server |
| Database backups | Forge: Business plan only, to storage you provide. Cloud: daily MySQL backups | A restore point for every database; restore it, or move the database to another server |
| Previews per PR | Cloud: one app on Starter, unlimited on Growth | A preview environment for every pull request, with its own HTTPS address, on your servers |
| Monitoring | Forge: Business plan only. Cloud: Laravel runs the servers | Metrics for every service and server, searchable logs and crash emails |
| Coding agents | Forge and Cloud dashboards and APIs | One pasted line sets up the CLI and `ployz mcp`. Every deploy, restart or delete your agent asks for waits for you to approve |
Pick Forge if you want a PHP server the classic way, with SSH, Nginx config you can edit and GitLab or Bitbucket deploys. Pick Laravel Cloud if your app is idle most of the day and can hibernate. Pick Ployz if you want Forge's server bill without the fee, a preview for every pull request, and a coding agent that deploys for you.
What comes with it.
- Your coding agent runs it. Paste one line into Claude Code, Codex or Cursor and it installs Ployz, adds your server and ships the repo. Every deploy, restart or delete your agent asks for waits for you to approve, and no setting turns that off.
- A restore point for every database. Restore it, or move the database to a bigger server with seconds of downtime (how, in the docs).
- Monitoring and searchable logs for the web app, the worker, the scheduler and every server, with an email when a service crashes.
- More servers when you need them. Add a server with one command; it joins a private network, and the web app can run up to 50 replicas.
Coming from Forge, leave the Forge server running while you deploy to a new server with Ployz, copy the database across, and move the domain once the new one works.
Questions
How do I deploy Laravel to my own server without Forge?
Run the web app, a queue worker and the scheduler as three services from your repository, add MySQL or Postgres, and run php artisan migrate --force before each deploy. With Ployz, ployz up --server root@your-server installs everything on the server and builds Laravel with no Dockerfile, and it's free on any number of servers.
What is the cheapest way to host Laravel?
A server you rent, with no panel fee on top. A small Laravel app with a worker, MySQL and Redis fits a 4 GB Hetzner CX23 for about $7 a month with Ployz, against $19 with Forge on the same server and $32 on Laravel Cloud.
Is there a free alternative to Laravel Forge?
Yes. Ployz is free on any number of servers and deploys Laravel from GitHub with a queue worker, the scheduler, one-click MySQL or Postgres, HTTPS and a preview for every pull request. You pay only for the server.
How do I run the Laravel scheduler without cron?
Run php artisan schedule:work as a long-running service with one replica. It invokes the scheduler every minute, which is what the cron entry for schedule:run does on a classic server.
How do I run Laravel queue workers on my own server?
Run php artisan queue:work as its own service from the same code. Each deploy replaces the worker with one on the new code, so you don't need queue:restart, and a worker that crashes is started again.
Does Laravel need Redis in production?
No. New Laravel apps use the database queue connection by default, so jobs live in a table. Add Redis if you use Horizon or want it for cache and sessions.
Do I need a Dockerfile to deploy Laravel?
No. Railpack detects Laravel from the artisan file, installs PHP, Composer dependencies and your Vite build, and serves public/ with FrankenPHP. Your own Dockerfile works too.
Can my coding agent deploy my Laravel app?
Yes. Paste "Read ployz.dev/agents.md and deploy this repo to my server." into Claude Code, Codex or Cursor. It installs the CLI, registers ployz mcp and deploys. Every deploy, restart or delete your agent asks for waits for you to approve, and no setting turns that off.
What does Ployz cost?
Nothing, on any number of servers, with unlimited projects, preview environments, custom domains and members, and the dashboard is hosted for you. You pay your server provider for the servers.
Your servers. The whole platform. Free on your own servers.
Deploy your appFacts checked 2026-11-15.