Run WordPress on your own VPS in one click

Why WordPress on a VPS instead of shared hosting

Choose shared or dedicated vCPU to match your workload. A VPS gives you root access; application performance depends on resources and configuration.

The trade-off is honesty: it's your server. You get root, and you get the responsibility that comes with it. This guide keeps that responsibility small.

Step 1 — Create the server with WordPress pre-selected

Create an account, go to Servers → New server, and pick:

• a region close to your readers (we offer regions across the EU, US and Asia);
• an Ubuntu or Debian image — the one-click installers are apt-based;
• the WordPress app in the one-click list. That's the whole "setup".

Step 2 — Finish the browser setup

WordPress starts with MariaDB 11 in Docker. Complete the browser installer; database credentials are in /root/wordpress-info.txt.

Step 3 — Give it a real domain and HTTPS

Connect a domain and configure HTTPS before using real accounts or credentials. The application container and reverse proxy must use different host ports.

What you're responsible for (the honest part)

• Back up application data and the database, then test a restore. Docker named volumes are not contained in the Compose project directory.
• Before updating containers, back up the data, read the upgrade instructions and select a compatible image version.
• Plugins. Most "WordPress is slow/hacked" stories are plugin stories. Install few, from known authors, and delete what you don't use.