Where can you host a Laravel app with GitHub deploys?
On a Frontend pack with a MySQL or PostgreSQL pack beside it: connect the repository, Laravel is detected, and each push to the branch deploys. The app gets its own CPU, memory and disk, a terminal for artisan commands, and your domain with a certificate. You pay one flat price per pack, which makes it a fit for an app that has outgrown shared hosting but does not need a server team.
Step by step
- 1
Deploy the repository
Dashboard → Deployments → New: select the repository and a pack. Laravel is detected from composer.json. The order creates an invoice and the build starts once it is paid.
- 2
Create the database
Dashboard → Databases → New: choose MySQL (or PostgreSQL) and a pack, then copy the host, port, database, user and password from its page.
- 3
Set the environment
On the site's Environment tab add APP_KEY (from php artisan key:generate --show), APP_URL, and the DB_ variables from the database page. Do not commit your .env file.
Variables are read at build time, so the site rebuilds after you change them; the current version keeps serving until the new build is ready.
- 4
Run migrations
Open the site's terminal and run the migration, or add it to the start command so it runs on each deploy.
In the site terminal
php artisan migrate --force php artisan config:cache && php artisan route:cache - 5
Attach the domain
Site → Domains tab → enter the domain and create the DNS record it shows. Set APP_URL to the new address.
What it costs
- A Frontend pack from $1/mo; $5/mo for the pack most production apps pick (1 vCPU / 4 GB / 25 GB).
- A database pack from $10/mo.
App
$1/mo
Starter Frontend pack, 1 vCPU / 1 GB RAM / 10 GB
Database, users and files
$5/mo
Smallest dedicated Supabase pack; several projects fit on one
Questions
Do queues and the scheduler work?+
A site runs one web process. For a queue worker or the scheduler, deploy a second site from the same repository with the worker as its start command, or use a Cloud Instance and run everything there.
Where should uploaded files go?+
In an S3-compatible bucket or the database. Do not rely on files written next to the code surviving a redeploy.
Can I run artisan commands?+
Yes, from the site's web terminal, or through an agent over MCP with site_terminal.
Do I need a Dockerfile?+
No. A standard Laravel repository builds as it is. A Dockerfile in the repository is used if present.
Is this shared hosting?+
No. Each pack is one isolated server for one app.
What does it cost?+
From $1/mo for the app and from $10/mo for the database.