Free and open

Deploy Laravel on your own server

A €5-a-month server handles most Laravel projects comfortably. What stops almost everyone isn't the price: it's setting up HTTPS, queues, backups and deploys that don't drop requests. That part is done.

By asking for it you agree to receive the kit and the odd email when I update it or publish something along the same lines. You can unsubscribe from any of them. privacy policy.

It reaches you straight away by email. Free, and no small print.

What's inside

Automatic HTTPS

The certificate is requested and renewed on its own. You never think about it again.

Zero-downtime deploys

The replacement comes up before the running one steps down. If the new one fails, the old one keeps serving and nobody notices.

Queues and scheduled tasks

With orderly shutdown: they finish the job in hand before going down.

Backups that check themselves

Every backup is restored into a throwaway database and its tables counted before it's trusted.

A locked-down server

Firewall, fail2ban and automatic security patches. And it won't lock you out if you haven't installed your key yet.

A one-glance check-up

One script tells you what's missing — certificate, backups, weak passwords — before a visitor finds out for you.

"Zero downtime" is measured, not promised

It's easy to write and hard to back up, so it was measured: a process hammering the page while deploys ran on top of it. Early versions did drop one request per deploy, and finding out why took four attempts.

9,000
requests across three deploys: 0
requests dropped: 91 MB
final image size: 6
containers, not one more

What you need

A VPS running Ubuntu 24.04 or Debian 12. 2 GB of memory is plenty
A domain pointing at its IP
A Laravel project. Tested against Laravel 13

And what it isn't

This doesn't replace a managed service with replicas across data centres. It replaces paying €60 a month for something that serves two hundred people. Be honest with yourself about which one you are.

Ask for it and I'll send it

The link reaches you straight away, with the three steps to get it running. And when I update the kit — because Docker and Laravel keep moving — I'll let you know.