I wouldn't, mainly because I don't trust a new platform is secure enough. Chicken and egg situation, I know.

I’ve always wondered why something like this isn’t a thing. AWS ECS had a half-hearted feature to deploy docker compose setups but they discontinued it awhile back. We use compose to run our app locally so it would be nice to just deploy that.

Like the other response, my concern would be reliability on a new service, but I’d use it after it was around for a year or two.

For reference, services trying this (or having tried this):

- https://kvmpods.com/

- https://dockerdeploy.cloud/

I would be interested, would even help testing and contribute but the next problem that arise if users had such easy way to deploy apps is, how do you handle backups, migration to new versions, single sign on, there are projects similar to this idea that already go very far, such as https://cloudron.io but they are "limited" in the amounts of apps they can provide with support and quality path for upgrades.

Inevitably, if I had all the apps I want to spin at hands, I would need a very neat way to make sure path to upgrades are smooth, don't break things already in place and potentially used in "production" by either friends of family..

Kubernetes is the standard now, why would I want to use something else?

I've not seen or used a docker-compose that was designed for production settings, it's primarily a dev time tool. Would we not have to maintain a second dc file with different settings?

You’re going to run into all the “death by a thousand cuts” problems that killed Mesos/Docker Swarm. Compliance, autoscaling, etc.. Then you’ll wish you went with Kobe or ECS..