Deploy
Self-host WordPress,
with no shared-host limits.Run WordPress on a server you own, 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 you can SelfHost?
What you get
WordPress, your way.
On a server you actually own.
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 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.
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.
Create a Project
Name it and a dedicated server is provisioned for you in minutes.
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.
Add a managed database
Drop a MySQL into the project for WordPress to use, and set the database host, name, user, and password.
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.
Point your domain
Map your domain, verify DNS, and HTTPS goes live automatically. Add a headless frontend as a second service if you want.
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
What you get
WordPress, the easy way.
On a server you control.
Run a traditional WordPress site, or use it headless behind a Next.js, Astro, or other frontend deployed in the same project.
Run a build step, a second app, or a separate frontend on the same server. You are not boxed into one site per plan.
Give WordPress a one-click MySQL in the project, with the database operated for you.
A dedicated server with live metrics and logs, your files, your database, your domain.
Add your domain, verify DNS, and renewed HTTPS is handled automatically.
From around $0.02/hr against prepaid credits, paused at a zero balance.
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, WordPress and your headless frontend run on the same server you own, so the whole stack lives in one place.