Deploy PHP without adopting a framework.

Not every PHP application is a framework app. Depfloy provisions PHP 8.4 and nginx, deploys your repository as a release, and gives you the same rollback, SSL and backups as everything else.

What runs on the server
Runtime
PHP 8.4
Releases
Zero-downtime symlink flip
Rollback
One click; rebuild depends on runtime and retained releases
The deploy script Depfloy runs
composer install --no-dev --optimize-autoloader
Your deploy script, your commands

There is no framework convention to satisfy. Whatever the release needs — a build step, a migration runner, a cache warm — goes in the script and runs on the server.

Shared directories for anything that persists

Uploads, generated files and configuration that must outlive a release are linked in rather than copied, so a deploy never destroys them.

nginx configuration you can edit

The generated site config is a starting point, not a black box — edit it from the dashboard when the app needs something specific.

Plenty of working PHP predates the frameworks around it. The release model here does not require you to restructure anything: connect a repository, name the commands that build it, and get rollback and TLS on top.

FAQ

PHP questions

Does my project need Composer? +
No. If there is no composer.json, drop the install step from the deploy script; the release model does not depend on it.
Can I set the PHP version and extensions? +
PHP 8.4 is provisioned by default and managed from the server's PHP screen, where extensions are installed too.
Is this suitable for a legacy application? +
Often yes — an app that expects a normal filesystem and a long-running server is exactly what a VPS provides, and shared directories cover the paths it writes to.

9 other frameworks deploy the same way.

The release model is identical; only the build steps differ.

Deploy PHP to your own server.

7 days free, no credit card. Your servers keep running exactly as Depfloy configured them.