Deploy

Laravel hosting,

without the server admin.

Deploy a Laravel app straight from GitHub onto a server we provision and maintain. SelfHost builds it with PHP and Composer, runs your migrations, and handles a managed database, queues, and SSL, with auto-deploy on push.

Why hand-roll PHP-FPM, Nginx, and a VPS, when you can SelfHost it?

Deploy Laravel See pricing
PHP + Composer /Managed MySQL or Postgres /Queues + SSL /From ~$0.02/hr

What you get

Your Laravel app, in production.
On a server you control.

Laravel in production usually means PHP-FPM, a web server, a MySQL or Postgres database, a queue worker, and TLS. SelfHost builds your app with Composer, runs it on a dedicated server, and gives you a managed database to point at. Add a worker for queues and a domain, and you are live.

Nixpacks (PHP, auto), or your Dockerfile

Deploy in 5 steps

From zero to live.
No server to set up.

From repo to a live Laravel app, with PHP, the database, and TLS handled.

1

Create a Project

Name it and a dedicated server is provisioned for you in minutes.

2

Connect your Laravel repo

Connect GitHub or paste a repo URL, pick a branch, and enable auto-deploy on push. The build runs composer install and your asset build.

3

Run migrations and set the key

Add php artisan migrate and key generation to the deploy step, and set APP_KEY and APP_ENV.

4

Add a managed database

Drop a MySQL or PostgreSQL into the project, or attach a dedicated managed Postgres instance, and set the DB_ connection variables.

5

Set env vars and go live

Paste your .env to import in bulk, point a domain, and HTTPS is provisioned automatically. Add a queue worker if your app uses one.

Environment variables

Configure it
in minutes.

Laravel reads its config from .env. The essentials:

Paste a .env to import in bulk, or set keys one by one. Values are wired into every build and deploy.

Key variables

APP_KEY The Laravel application key; generate one and keep it secret.
APP_ENV / APP_DEBUG Set to production and false for a live app.
DB_CONNECTION / DB_* Database connection details for your project or managed database.
QUEUE_CONNECTION Set to redis or database if you run queued jobs.

What you get

Laravel, the easy way.
On a server you control.

PHP and Composer

The build installs Composer dependencies and builds your assets. Bring a Dockerfile for full control.

Managed MySQL or Postgres

Add a one-click MySQL or PostgreSQL in the project, or a dedicated managed Postgres instance.

Queues and workers

Run a queue worker as a second service alongside the web app, on the same server.

Auto-deploy on push

Every push builds, migrates, and ships, with PR previews, rollback, and logs.

Custom domain + SSL

Add your domain, verify DNS, and renewed HTTPS is handled for you.

Pay only for what you run

From around $0.02/hr against prepaid credits, paused at a zero balance.

Which one

Web, worker, and database on one server

Run your Laravel app, a queue worker, Redis, and a database on the same project server, billed as one server rather than a stack of add-ons.

Keep exploring

Related guides.

All deploy guides Managed PostgreSQL Heroku alternative Pricing and credits

Frequently Asked Questions

How do I host a Laravel app on SelfHost?
Connect your GitHub repo, and the build runs composer install and your asset build on a server we provision. Add migrations to the deploy step, set APP_KEY and the DB variables, add a managed database and a domain, and enable auto-deploy on push.
MySQL or Postgres for Laravel?
Either. Add a one-click MySQL or PostgreSQL inside the project, or attach a dedicated managed PostgreSQL instance, then set Laravel DB_ variables to match. Managed PostgreSQL.
Can I run queue workers and the scheduler?
Yes. Add a worker service for queues and run the scheduler on the same project server, alongside your web app.
How much does Laravel hosting cost?
Pay-as-you-go from around $0.02/hr per project server (about $0.50 a day), no tiers. Link a card for a welcome credit worth roughly 48 hours. See pricing.
Do I have to manage the server?
No. SelfHost provisions and runs the server, including OS patching and uptime. You get metrics and logs and simply deploy. How Projects work.

Your Laravel app, in production.
On a server run for you.

Database included
Queues + SSL
Run a project free for ~48 hours
Deploy Laravel