Deploy
Deploy Docker Compose, on a server run for you.
Bring your docker-compose.yml and Selfhost.dev deploys the whole multi-container app onto a single server we provision and set up. Your web service, workers and datastores come up together, with custom domains and SSL and no proxy or certificates to configure.
Why rent a VPS to run compose by hand, when Selfhost.dev can run it for you?
+$5.00 added at signup · deployment choice preserved · no card
What you get
Your whole compose stack.
On a server you control.
A docker-compose file is the easiest way to describe a multi-service app: a web container, a worker, a cache, a database, all wired together. Selfhost.dev deploys that compose file onto one dedicated server, brings the services up and handles the proxy and TLS, so you do not need a VPS and a manual docker compose up.
Deploy in 5 steps
From zero to live.
No server to set up.
From a compose file to a live multi-container app, on a server handled for you.
Create a Project
Name it and a dedicated server is provisioned for you.
Connect a repo with a compose file
Connect GitHub or paste a repo URL that contains your docker-compose.yml and pick the branch.
Select the Docker Compose build pack
Selfhost.dev reads your compose file and builds or pulls each service. Set which service is web-facing and its port.
Set environment variables
Provide the variables your services expect or paste a .env to import in bulk. They are passed to the right containers.
Point a domain and deploy
Map a custom domain to your web service and HTTPS goes live automatically. Push to redeploy the whole stack.
Environment variables
Configure it
in minutes.
Compose apps usually share a set of variables across services:
Paste a .env to import in bulk or set keys one by one. Values are wired into every build and deploy.
Key variables
Why Selfhost.dev
Docker Compose, the easy way.
On a server you control.
Deploy your compose file as-is
Bring the docker-compose.yml you already use in development and deploy the same stack to production.
Many services, one server
Web, worker, cache and database run together on a single project server, billed as one server.
A server you control
Live metrics and logs for your services on a dedicated server you control, not a shared platform.
Auto-deploy on push
Push to redeploy the whole stack, with rollback and streaming logs.
Custom domain + SSL
Point a domain at the web service and HTTPS is provisioned and renewed for you.
Pay only for what you run
From around $0.02/hr in Europe against prepaid credits, with no surprise invoices.
Drive it from your AI editor
Trigger deploys, stream logs, set env vars and add domains from Claude, Cursor or any MCP client: 239 MCP tools.
For managed databases, split them out
Running a database container in compose is fine for many apps. For a production database with PITR, pooling and Multi-AZ, attach a dedicated managed PostgreSQL instead and point your compose services at it.