1-click WordPress, on a server you own.

Pick WordPress, a server and a domain. Depfloy creates the MySQL database and user, installs WordPress and WP-CLI, replaces WP-Cron with a real scheduled task, and issues the certificate — with every step reporting what it did while you watch.

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
1-click install, database and all

Choose WordPress, a server and a domain, and answer four questions. Depfloy creates a MySQL database and a user scoped to it, installs WordPress and WP-CLI, writes wp-config.php with fresh salts, and runs the installer. Leave the administrator password empty and one is generated.

Watch the install happen

Every step is listed before it starts and reports what it did — the version installed, the database created, how long it took. A step that fails says why and stops there, leaving everything after it untouched. Fix it and run it again; the install picks up the same database rather than making a second one.

Real cron, not visitor-triggered cron

WordPress fires scheduled work from page loads unless told otherwise, so a quiet site never runs it and a busy one runs it on someone's request. The 1-click install turns WP-Cron off and schedules the due jobs every five minutes instead.

PHP that cannot run from your uploads folder

The nginx configuration refuses wp-config.php, refuses the installer scripts, and refuses to execute PHP under wp-content/uploads. A file someone uploads is served as a file.

Database and files, both backed up

A WordPress site is two things worth backing up. Depfloy schedules the MySQL database and the project files separately, to S3, Cloudflare R2, SFTP or the server's own disk — with restore.

WordPress is the oldest thing on this list and the one most often stuck on shared hosting. Here it goes on a VPS you rent, in a flow that takes a domain and four answers: the database, WP-CLI, the cron entry and the certificate are all set up while you watch the steps go by.

What you get afterwards is a server, not a tenancy. Scheduled backups of both the database and the files, with restore. TLS that renews itself. Uploads that cannot execute as PHP. And SSH, because it is your machine.

FAQ

WordPress questions

What does the 1-click install actually set up? +
A MySQL database and a user with rights to that database and nothing else. WordPress itself, plus WP-CLI left on the server for you to use over SSH. A cron entry running WordPress's due jobs every five minutes. The nginx rules above, and a Let's Encrypt certificate once DNS points at the server. You choose the site title, the administrator account and the language.
How does the domain get pointed at the server? +
If the zone is on a Cloudflare account you have connected to Depfloy, adding the domain opens the A record for it — unproxied, so the certificate can be issued — and the result is read back from Cloudflare rather than waited out as propagation. On any other DNS provider you create the record yourself first. Either way it has to resolve before you install, because WordPress records its own address during setup and a certificate cannot be issued for a name that does not reach the machine.
Can I run several WordPress sites on one server? +
Yes. Each one is its own project with its own domain, its own database and its own nginx configuration, and they appear side by side in the console. How many a server takes is a question of its memory and CPU, not of the plan you are on.
Can I install WooCommerce at the same time? +
Yes — pick the WooCommerce preset when you install and the plugin is installed and activated during setup. Nothing else about the install differs, and you can add it later from wp-admin like any other plugin if you change your mind.
Can I update WordPress from Depfloy? +
Yes. An installed site has an Update action that updates core, applies the database changes that come with it, then updates plugins and themes. WordPress's own updater keeps working too — the filesystem is writable by the web user, so no FTP credentials are ever asked for.
What happens if a step fails partway through? +
It stops at that step and tells you what the server said. Nothing is removed and nothing is half-linked — the steps after it were never reached. Run it again once you have fixed the cause; every step is safe to repeat, and the database created on the first attempt is reused.
Do I have to keep WordPress in git? +
No. The 1-click install needs no repository at all. If you already keep core and plugins in one and want a build step and releases you can roll back to, deploy it as a project like any other — uploads and wp-config go in shared directories and survive every deploy.

9 other frameworks deploy the same way.

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

Deploy WordPress to your own server.

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