Deploy

Self-host WordPress, with no shared-host limits.

Run WordPress on a server you control, deployed from a Docker image or a Compose file, with a managed database, a custom domain, and SSL handled. Use it as a full site or as a headless CMS behind your own frontend, and run your other apps on the same server.

Outgrew your shared host? Why move hosts again, when Selfhost.dev can run it for you?

Deploy WordPress See pricing
Full or headless /Managed MySQL /Custom domain + SSL /From ~$0.02/hr

What you get

WordPress, your way.
On a server you control.

Shared hosts are fine until you outgrow them: you cannot run a separate frontend, a build step, or a second app, and going headless usually means moving hosts entirely. On Selfhost.dev you get a real server, 40 GB SSD, 4 GB RAM, 2 vCPUs, where WordPress runs from Docker with a managed MySQL, and your headless frontend and other apps live right beside it. One server, no per-site plan.

Docker or Docker Compose

Deploy in 5 steps

From zero to live.
No server to set up.

From zero to a live WordPress site on a server you control.

1

Create a Project

Name it and a dedicated server is provisioned for you in minutes.

2

Deploy WordPress from Docker

Add a service from the official WordPress Docker image, or a docker-compose.yml that pairs WordPress with a database, and deploy it.

3

Add a managed database

Drop a MySQL into the project for WordPress to use, and set the database host, name, user, and password.

4

Set env vars and storage

Configure the WordPress database variables and any keys, pasting a .env to import in bulk. Persist uploads on the server volume.

5

Point your domain

Map your domain, verify DNS, and HTTPS goes live automatically. Add a headless frontend as a second service if you want.

Deploy WordPress free

Environment variables

Configure it
in minutes.

WordPress in Docker reads its database config from the environment:

Paste a .env to import in bulk, or set keys one by one. Values are wired into every build and deploy.

Key variables

WORDPRESS_DB_HOST Host of your project MySQL database.
WORDPRESS_DB_NAME The database name for the site.
WORDPRESS_DB_USER / WORDPRESS_DB_PASSWORD Credentials WordPress uses to connect.
WORDPRESS_CONFIG_EXTRA Optional extra wp-config settings, for example for headless or multisite.

Why Selfhost.dev

WordPress, the easy way.
On a server you control.

Full site or headless CMS

Run a traditional WordPress site, or use it headless behind a Next.js, Astro, or other frontend deployed in the same project.

No shared-host limits

Run a build step, a second app, or a separate frontend on the same server. You are not boxed into one site per plan.

Managed MySQL

Give WordPress a one-click MySQL in the project, with the database operated for you.

A server you control

A dedicated server with live metrics and logs, your files, your database, your domain.

Custom domain + SSL

Add your domain, verify DNS, and renewed HTTPS is handled automatically.

Pay only for what you run

From around $0.02/hr against prepaid credits, paused at a zero balance.

Drive it from your AI editor

Trigger deploys, stream logs, set env vars, and add domains from Claude, Cursor, or any MCP client: 150+ MCP tools.

Which one

The headless move shared hosts cannot make

Going headless usually means leaving your host: the CMS stays put while the new frontend lives somewhere else. On Selfhost.dev, WordPress and your headless frontend run on the same server you control, so the whole stack lives in one place.

Keep exploring

Related guides.

All deploy guides Deploy with Docker Coolify alternative Managed MySQL Deploy a Laravel app How Projects work Pricing and credits

Frequently Asked Questions

Can I self-host WordPress on Selfhost.dev?
Yes. Deploy WordPress from the official Docker image or a Compose file onto your project server, add a managed MySQL, set the database environment variables, and point your domain. WordPress is not a one-click template; it deploys via Docker, which gives you the full, standard WordPress.
Can I run WordPress as a headless CMS?
Yes. Run WordPress for content and the REST or GraphQL API, and deploy your frontend (Next.js, Astro, or another framework) as a second service in the same project, on the same server.
What database does WordPress use here?
MySQL. Add a one-click MySQL inside the project and point the WordPress database variables at it.
How is this different from shared hosting like Hostinger?
A shared host gives you one constrained site environment. Selfhost.dev gives you a real server, 40 GB SSD, 4 GB RAM, 2 vCPUs, where you can run WordPress, a headless frontend, and other apps together, billed as one server, with no per-site plan limits.
How much does it cost to host WordPress?
Pay-as-you-go from around $0.02/hr per project server (about $0.50 a day), no tiers. Signing up gets you a $1 welcome credit, roughly 48 hours of a project server, no card needed. See pricing.
Can I manage my WordPress deployment with AI?
Yes. The Selfhost.dev MCP server ships 150+ tools across 23 modules: trigger deploys, stream build logs, set environment variables, add domains, and manage the project from Claude, Cursor, Windsurf, or any MCP client. Explore the MCP server.

WordPress, full or headless.
On a server you control.

Full or headless
No shared-host limits
Run a project free for ~48 hours
Deploy WordPress