What is the best deployment tool for PHP?
For a team or agency running several PHP apps on its own servers, the best PHP deployment tool is one that also builds the servers and runs the workers, and DeployManage Growth at $129 a month covers 10 servers, 50 sites per server and 10 members with atomic releases. For a single developer who is comfortable maintaining scripts, Deployer is the strongest choice and has no licence fee. For a team whose servers are already built and only needs deploys, Envoyer at $10 to $50 a month is cheaper.
The honest split is about scope. Deployer, Envoyer and DeployHQ deploy code. Laravel Forge and DeployManage deploy code and also install and patch the server underneath it. If you already have a sysadmin keeping Nginx, PHP and Supervisor in shape, a deploy only tool is enough. If nobody on the team wants that job, the panel is what you are really buying.
Laravel Forge is the cheaper panel at $12 to $39 a month. Its native zero downtime deploys are limited to one server per site, which is fine for most apps. DeployManage costs more and is aimed at teams that want more seats, a per member activity log and several PHP frameworks in one place.
How do I deploy a PHP application with zero downtime?
Build each release in a new directory, finish every install and build step there, then switch a symlink that the web server points at. Because the switch is a single filesystem rename, requests either hit the old release or the new one, never a mix. Shared files such as .env, uploads and logs live outside the release folders and are linked in.
In DeployManage the layout on the server looks like this:
releases/20261009120000, one folder per deploy, the newest five are keptcurrent, a symlink to the live release, which Nginx serves.env and storage, kept once at the site root and linked into each release
Your deploy script runs inside the new release with DM_RELEASE_DIR and DM_COMMIT set, so a step such as php bin/console cache:warmup or a WordPress uploads link works without hard coded paths. If any command fails, the script stops and current keeps pointing at the old release.
One thing a symlink switch cannot fix on its own is a database migration that breaks the old code. Add columns before you use them and drop them a release later, and both releases can run against the same schema for the seconds the switch takes.
How do I deploy a PHP application to a server?
Install a web server and PHP-FPM on the server, put the code in a directory the web server serves, install dependencies with Composer, write the environment file and point a domain at it with TLS. Every later deploy repeats the code and dependency steps.
Done by hand, that first setup is an afternoon of apt installs, an Nginx server block, a PHP-FPM pool, a Let's Encrypt certificate and a Supervisor config if the app has queue workers. The repeat steps are where most outages happen, because git pull and composer install in the live directory leave the site half updated while they run.
A deployment tool turns the first setup into a form and the repeat steps into a button or a push. With DeployManage you create the server, add the site with its domain, project type and PHP version, connect the repository and press Deploy. The certificate is issued with Let's Encrypt from the site screen.
Deployer vs a hosted PHP deployment tool
Deployer is a free, MIT licensed PHP tool that deploys over SSH from your machine or a CI job, with recipes for Laravel, Symfony, WordPress and other frameworks, release folders and rollback. It is excellent at the deploy itself. What it leaves to you is everything around it.
| Job | With Deployer | With DeployManage |
|---|
| Run the deploy | dep deploy from a laptop or a CI pipeline you maintain | A button or a git push webhook |
| Build the server | Separate scripts, Ansible or by hand | Included, same stack on every server |
| Who can deploy | Whoever holds the SSH key | Named members, each action logged |
| Queue workers | Your own Supervisor config | Managed per site |
| Software cost | None, plus the hours to maintain it | $59 to $299 a month |
If one person deploys one or two apps, stay on Deployer. The case for paying starts when several people deploy, when servers multiply, or when the developer who wrote the recipes leaves.
How much does a PHP deployment tool cost?
Between nothing and about $300 a month for the software, plus the servers. Deployer has no licence fee. Envoyer is $10, $20 or $50 a month by project count with unlimited members. DeployHQ has a free tier and paid plans of EUR 9 to EUR 99 a month. Laravel Forge is $12, $19 or $39 a month. DeployManage is $59 (3 servers, 2 members), $129 (10 servers, 10 members, atomic releases and quick deploy) or $299 (unlimited), and half that per month when billed yearly.
A worked example for a small agency with 12 PHP sites on two 4 GB servers at $24 each:
| Setup | Servers | Software | Monthly total |
|---|
| Deployer, servers built by hand | $48 | $0 | $48 plus maintenance time |
| Envoyer Plus (20 projects), servers built by hand | $48 | $20 | $68 |
| Laravel Forge Growth | $48 | $19 | $67 |
| DeployManage Growth, monthly | $48 | $129 | $177 |
| DeployManage Growth, billed yearly | $48 | $64 | $112 |
On price alone Forge and Envoyer win this table, and we would rather say so than have you find out later. What the DeployManage line pays for is that nobody on the team builds servers or keeps Supervisor configs, that 10 people get their own logins with an activity log, and that Laravel, Symfony and WordPress sites run on the same panel.
Which PHP frameworks and apps can it deploy?
Any PHP application that installs with Composer or ships as plain files. The project types in the site form are General PHP or Laravel, Symfony, WordPress and static HTML, and the deploy script is yours to edit, so Statamic, Craft CMS, Drupal, Slim or a legacy app without a framework deploy the same way.
Framework pages with worked setups:
The provisioning script installs PHP and Composer but not Node. If your release builds front end assets, build them in CI and commit or upload the result, or install Node on the server once and call npm from the deploy script.
Can I roll back a PHP deployment?
Yes. Redeploy the last known good commit and it goes live as a new release through the same symlink switch, usually in under a minute for a typical Composer app. The five most recent release folders stay on disk, which keeps the previous code available while you investigate.
Rolling back code does not roll back the database. If the bad release ran a migration, write a follow up migration rather than restoring a backup over live data, unless the data itself is damaged.
Ready to stop managing servers by hand? DeployManage provisions, deploys and monitors your fleet from one dashboard.
Get started
