Deploy
Deploy Docker Compose,
on a server run for you.Bring your docker-compose.yml and SelfHost deploys the whole multi-container app onto a single server we provision and maintain. Your web service, workers, and datastores come up together, with custom domains and SSL, and nothing for you to patch.
Why rent a VPS to run compose by hand, when you can SelfHost it?
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 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 in minutes.
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 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
What you get
Docker Compose, the easy way.
On a server you control.
Bring the docker-compose.yml you already use in development and deploy the same stack to production.
Web, worker, cache, and database run together on a single project server, billed as one server.
Live metrics and logs for your services on a dedicated server you own, not a shared platform.
Push to redeploy the whole stack, with rollback and streaming logs.
Point a domain at the web service and HTTPS is provisioned and renewed for you.
From around $0.02/hr against prepaid credits, paused at a zero balance.
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.