Deploy Laravel to your own server. Push, and it’s live.
PimiDeploy is a hosted server panel for the VPS you rent. It sets up a fresh Ubuntu 24.04 server, deploys from git with no downtime, and looks after queues, SSL, backups and health checks.
In private testing. It already runs our own production.
Push to main received Cloning into releases/20261011221402 Linking shared/.env and shared/storage Running your deploy script composer install --no-dev php artisan migrate --force Switching current → 20261011221402 Reloading PHP-FPM, restarting workers Health check: 200 OK ✓ Live in 21 s
A release should not need an SSH session
Your own VPS is cheap until every release means logging in, pulling, migrating and restarting workers by hand. Miss a step and the site is down, or the queue runs old code. PimiDeploy runs the same steps the same way every time.
Deploy Laravel in three steps
- 1
Connect a server
Create an Ubuntu 24.04 VPS at any host and add the panel’s SSH key. PimiDeploy installs nginx, PHP 8.4, your database, Redis and Node 22, then locks down SSH.
- 2
Add your app
Point a new site at your git repository. It gets its own Linux user, PHP pool and database. Connect GitHub, and the deploy key and webhook are added for you.
- 3
Push
Every push to your branch deploys. The new release goes live only if it built. Otherwise the one you had keeps serving.
Every step, and what a failed deploy looks like: how PimiDeploy works.
What a Laravel app needs on its server
Zero-downtime deploys
Each deploy is built in its own release folder and goes live only when it is ready. A push to your branch starts it.
Rollback and a health check
The last 5 releases are kept. After each deploy the panel checks the site answers, and can roll back by itself if it does not.
Queue workers and the scheduler
Run queue workers or Horizon under supervisor and turn on the scheduler. Workers restart on the new code after every deploy.
Free SSL
Let’s Encrypt certificates for your domain and its aliases, with http sent to https and renewal running on the server.
Database backups
MySQL, MariaDB or PostgreSQL 16, on a schedule, to the server or S3-compatible storage, with retention and restore.
Health checks and alerts
Every server and site is checked every 5 minutes, and certificates for expiry. Alerts by email, Slack, Discord or webhook.
WordPress sites run on the same servers
Create a WordPress site next to your Laravel apps. PimiDeploy installs it and handles SSL, PHP versions, wp-config.php and backups that include wp-content: WordPress on your own server.
It runs our own production
Before anyone else uses PimiDeploy, we do. On our own servers we measured about 3 minutes to provision and 21 seconds for a deploy.
It holds one SSH key. Your secrets stay on your server.
What it can touch
The panel reaches your server over SSH with one key, stored encrypted. A new server gets key-only SSH, fail2ban, automatic security updates and a firewall.
What stays on your server
Your app’s .env is read from the server and never stored in the panel. Each site has its own Linux user, PHP pool, database user and Redis user.
How you leave
Remove a server from the panel and its sites keep running. One tick also removes the panel’s key from the server.
Already run a server? Connect it read-only first: nothing changes until you say so. See what PimiDeploy can touch on your server.
What it does not do yet
- Ubuntu 24.04 only You create the VPS and point your DNS at it yourself.
- No deploys on a server it did not set up Planned. Today a server you already run is read-only.
- No MCP server Planned. Today every action is an API call.