NewOut Plane raises funding, backed by Maza VenturesRead the announcement
CMS

WordPress

Overview

Deploy a self-hosted WordPress instance with a MySQL database and persistent storage on Out Plane. WordPress powers over 40% of the web and gives you access to 60,000+ plugins, thousands of themes, and a mature REST API for headless architectures. With Out Plane, your installation includes built-in SSL.

Self-hosting WordPress means full control over your data, plugins, and performance optimizations. Unlike managed WordPress hosts, you are free to install any plugin, customize PHP settings, and integrate with external services without restrictions. Out Plane handles database provisioning, storage volumes, and networking so you can focus on content.

Ideal for blogs, business websites, WooCommerce stores, membership sites, and headless CMS setups that need a reliable, scalable backend with zero vendor lock-in.


Self-Hosted WordPress: Docker Setup, Costs and Upkeep

Updated

Self-hosted WordPress is the free, open source WordPress software from WordPress.org running on hosting you choose, instead of on a WordPress.com plan. On Out Plane you run it as two apps: the official wordpress:7.1.4-apache Docker image on port 80, and a MariaDB 11.4 database on a private port, each with its own 10 GB volume.

Out Plane runs the servers, HTTPS and the private network. You own WordPress: plugins, updates and backups. This guide follows the official image docs. For other apps, see all templates.

What You Need

  • An Out Plane plan. Starter allows 3 apps and 30 GB of volume storage, enough for this setup. Starter and Pro both start with a 14 day free trial.
  • Two apps. WordPress on op-34 (1 vCPU, 2 GB) and MariaDB on op-22 (1 vCPU, 512 MB) as starting sizes.
  • Two 10 GB volumes. A volume's size is fixed at creation (10 to 50 GB), so go bigger for a large media library.
  • A MySQL compatible database. WordPress recommends MariaDB 10.11+ or MySQL 8.0+ (requirements). Out Plane manages PostgreSQL only, so MariaDB runs as an app you operate.

An app with a volume runs as a single instance, so you scale WordPress up to a larger size, not out.

Deploy WordPress on Out Plane

The Deploy WordPress button opens the Out Plane console with nothing pre-filled. Create the database first.

  1. Create the database app. Open Create new → Application, choose the Image source, enter mariadb:11.4 and name it wpdb01.
  2. Keep its port private. Add port 3306, protocol TCP, with Public TCP access unchecked.
  3. Size and storage. Pick op-22 under Compute. Under Volumes, select Create volume, 10 GB, mount path /var/lib/mysql.
  4. Paste the variables, then select Deploy app:
bash
MARIADB_DATABASE=wordpress
MARIADB_USER=wordpress
MARIADB_PASSWORD=<db-password>
MARIADB_ROOT_PASSWORD=<root-password>
  1. Create the WordPress app from the image wordpress:7.1.4-apache and name it wpsite.
  2. Expose port 80. Protocol HTTP, with Public HTTPS access checked.
  3. Size and storage. Pick op-34 and a new 10 GB volume at /var/www/html, which holds WordPress core, wp-config.php, themes, plugins and uploads.
  4. Point WordPress at the database, then select Deploy app. wpdb01:3306 is the database's internal address, reachable only by apps in your team:
bash
WORDPRESS_DB_HOST=wpdb01:3306
WORDPRESS_DB_USER=wordpress
WORDPRESS_DB_PASSWORD=<db-password>
WORDPRESS_DB_NAME=wordpress
  1. Install WordPress at once. Open https://wpsite-80-acme.outplane.app, with your team's slug in place of acme, and enter the site title, admin user, password and email. Until you finish, anyone who opens the URL sees the same installer.

"Error establishing a database connection" means wpdb01 is still deploying or the passwords differ.

The same setup with the outplane CLI:

bash
outplane volume create wpdbdata --size 10 --json --fields id
outplane app create wpdb01 --image mariadb:11.4 --port 3306:tcp --size op-22 \
  --volume <DB_VOLUME_ID>:/var/lib/mysql \
  --env MARIADB_DATABASE=wordpress --env MARIADB_USER=wordpress \
  --env MARIADB_PASSWORD=<db-password> --env MARIADB_ROOT_PASSWORD=<root-password>
outplane volume create wpfiles --size 10 --json --fields id
outplane app create wpsite --image wordpress:7.1.4-apache --port 80:http:public --size op-34 \
  --volume <WP_VOLUME_ID>:/var/www/html \
  --env WORDPRESS_DB_HOST=wpdb01:3306 --env WORDPRESS_DB_USER=wordpress \
  --env WORDPRESS_DB_PASSWORD=<db-password> --env WORDPRESS_DB_NAME=wordpress
outplane app get wpdb01
outplane app get wpsite

Attaching a volume at creation is best effort, so outplane app get confirms the mount.

WordPress Docker Environment Variables

The image builds wp-config.php from WORDPRESS_* variables:

VariableWhat it does
WORDPRESS_DB_HOSTDatabase host and port.
WORDPRESS_DB_USER, WORDPRESS_DB_PASSWORDDatabase login.
WORDPRESS_DB_NAMEMust already exist. MARIADB_DATABASE creates it.
WORDPRESS_TABLE_PREFIXTable prefix, default wp_.
WORDPRESS_DEBUGAny value turns on WP_DEBUG. Leave unset in production.
WORDPRESS_CONFIG_EXTRAPHP code run inside wp-config.php.

Skip the *_KEY and *_SALT variables: on the first start the image writes random values into wp-config.php on the volume. Variables live in Settings → Environment and apply on the next deployment, so use Save & deploy.

Two behaviors of the image catch most people:

  • Email does not send. The image has no mail setup, so password resets never arrive. Install an SMTP plugin and connect a mail provider.
  • Uploads stop at 2 MB, PHP's default upload_max_filesize. To raise it, create the app from a GitHub repository with this Dockerfile instead of the plain image:
dockerfile
FROM wordpress:7.1.4-apache
RUN printf "upload_max_filesize = 64M\npost_max_size = 64M\n" > "$PHP_INI_DIR/conf.d/uploads.ini"

From WordPress Docker Compose to Out Plane

Out Plane deploys images and repositories, not Compose files, so each service in the image's Compose example becomes an app:

ComposeOut Plane
wordpress service, ports: 8080:80App wpsite, port 80 HTTP, public
db service, mysql:8.0App wpdb01, private TCP port 3306
WORDPRESS_DB_HOST: dbWORDPRESS_DB_HOST=wpdb01:3306
Named volumes wordpress and dbVolumes at /var/www/html and /var/lib/mysql

To keep MySQL, deploy mysql:8.0 with the MYSQL_* variables from that file instead.

Custom Domain and HTTPS

  1. On Domains, select Add domain, enter the bare host, such as blog.example.com, and pick wpsite on port 80.
  2. In the DNS dialog, a subdomain takes a CNAME to domains-management.outplane.app. A root domain takes an A record named @ with the value shown.
  3. DNS takes 5 to 30 minutes. HTTPS is issued automatically once the record resolves.

WordPress stores the address you installed it on, so update WordPress Address (URL) and Site Address (URL) under Settings → General. To pin it in config, as the WordPress docs describe:

bash
WORDPRESS_CONFIG_EXTRA=define('WP_HOME','https://blog.example.com'); define('WP_SITEURL','https://blog.example.com');

Links in existing posts keep the old address, so add the domain before you publish. Starter includes 5 domains, Pro 25. See the custom domain docs.

Updates and Backups

WordPress core, themes and plugins update from Dashboard → Updates, and WordPress's automatic background updates stay on. The image copies WordPress onto the volume only on the first start, so a newer image tag changes PHP and Apache, not your WordPress version.

Image apps never deploy on their own. Open Deployments, select Deploy and enter the full reference, for example wordpress:7.1.4-php8.4-apache to move from PHP 8.3 to 8.4. To roll back, deploy the previous tag.

bash
outplane deploy create wpsite --image wordpress:7.1.4-php8.4-apache --wait

For MariaDB, pin a major version such as 11.4. Apart from MARIADB_AUTO_UPGRADE, the MARIADB_* variables act only on an empty volume, so editing MARIADB_PASSWORD later changes nothing: change the password in SQL, then update WORDPRESS_DB_PASSWORD. Set MARIADB_AUTO_UPGRADE=1 before a major version upgrade.

Out Plane does not snapshot volumes, so run your own backups:

  • A backup plugin that sends the database and wp-content to S3 compatible storage, such as an Out Plane bucket.
  • A dump before risky updates, from the Shell tab on wpdb01. It sits on the same volume, so it covers a bad update, not a lost volume.
bash
mariadb-dump -u root -p"$MARIADB_ROOT_PASSWORD" wordpress > /var/lib/mysql/before-update.sql

What WordPress Costs on Out Plane

Compute is billed per instance-minute. Volumes cost $0.30 per GB per month while they exist.

ItemRate30 days
wpsite on op-34$0.0004167 per minute$18.00
wpdb01 on op-22$0.0001389 per minute$6.00
Two 10 GB volumes$0.30 per GB per month$6.00
Usage total$30.00

Starter is $9 a month with $9 of usage included, so this setup costs $30 a month. Pro is $29 with $15 included, so $44. Bandwidth, SSL and custom domains are not billed. Starter and Pro both start with a 14 day free trial. See pricing.

Self-Hosted WordPress vs WordPress.com or a VPS

WordPress.com runs the same software as a managed service. On 2026-11-11 its pricing page listed Personal at US$4 and Business at US$25 a month billed yearly, excluding taxes, with plugins on every paid plan. For one blog with no custom code, that is the simpler path.

Self-hosting fits when you want your own PHP image and php.ini, a database you can dump at any time, and WordPress on one private network with your other apps. A VPS gives that control, but you also patch the OS, install Docker and manage certificates. More in self-hosted vs managed PaaS.

FAQ

What is a self-hosted WordPress site?

A site running the open source WordPress software from WordPress.org on hosting you pick, not on WordPress.com. You install it, update it and back it up.

Yes. WordPress is released under the GPLv2 or later, which lets anyone run, modify and share it. You stay responsible for your content and visitor data.

What is the difference between cloud and self-hosted WordPress?

With hosted WordPress, the provider runs the servers and the software. Self-hosted means you choose where it runs and operate it. Out Plane sits between: it runs the servers, HTTPS and networking, and you run WordPress and its database.

Can WordPress use Out Plane's managed PostgreSQL?

No. WordPress requires MariaDB or MySQL, so the database runs as its own app with a volume, as shown above.



Start deploying in minutes

Connect your GitHub repository and deploy your first application today. Start with a 14-day free trial.

Start 14-day free trial