Those are too low level for most users and you&#x27;ll eventually end up (poorly) re-inventing a PaaS if you need things like configuration, authorisation, scaling, routing, rollbacks, etc. I&#x27;ve found Deis (<a href="https:&#x2F;&#x2F;github.com&#x2F;deis&#x2F;deis" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;deis&#x2F;deis</a>) to hit the sweet spot between flexibility and convenience.<p>It is built on top of docker and Kubernetes (CoreOS&#x2F;fleet in v1), and lets you deploy docker containers natively and&#x2F;or automatically builds those for you using Heroku buildpacks or Dockerfiles when doing git push deployments. You can also drop down to the Kubernetes level if you need to for things that don&#x27;t really fit the 12-factor app model without breaking Deis.<p>That being said, I&#x27;m totally biased as I wrote an Heroku-like UI for it (<a href="http:&#x2F;&#x2F;deisdash.com&#x2F;about" rel="nofollow">http:&#x2F;&#x2F;deisdash.com&#x2F;about</a>) and using it for our infrastructure at work. Other similar alternatives are <a href="http:&#x2F;&#x2F;pivotal.io&#x2F;platform" rel="nofollow">http:&#x2F;&#x2F;pivotal.io&#x2F;platform</a>, <a href="https:&#x2F;&#x2F;flynn.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;flynn.io&#x2F;</a>, <a href="https:&#x2F;&#x2F;www.openshift.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.openshift.com&#x2F;</a>, <a href="https:&#x2F;&#x2F;github.com&#x2F;dokku&#x2F;dokku" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;dokku&#x2F;dokku</a> (for single server), etc.