Deploy Laravel to a server you own.
Connect a VPS over SSH and Depfloy provisions PHP, nginx and your database, then deploys every push as a new release. The symlink only flips once the build succeeds, so a failed deploy leaves the previous release serving.
- Runtime
- PHP 8.4
- Releases
- Zero-downtime symlink flip
- Rollback
- One click; rebuild depends on runtime and retained releases
Install the Laravel plugins from the project screen. Depfloy supervises each one, restarts it on deploy, and gives it its own log stream.
Cron entries and queue workers are configured next to the code they run, not in a separate place you forget about.
Shared files and directories are linked into each new release, so uploads and the environment file are not wiped when a deploy lands.
Laravel deploys the same way every other framework does on Depfloy: the release is built in its own directory while the current one keeps serving, and going live is an atomic symlink flip. What is Laravel-specific is everything around the release — the scheduler, the queue workers, and the first-party packages that need a supervised process of their own.
Laravel questions
Does Depfloy run my migrations? + −
What happens to queue workers during a deploy? + −
Which PHP version do I get? + −
9 other frameworks deploy the same way.
The release model is identical; only the build steps differ.
Deploy Laravel to your own server.
7 days free, no credit card. Your servers keep running exactly as Depfloy configured them.