Comparing to a self-hosted PaaS is fair for the open source containership project.
It has built in high availability, automatic clustering of nodes, loadbalancing, service discovery, persistent data management, internal DNS, and support for easily extending the core of the system with plugins (plus more).
Of your examples I would say it is most like Openshift Origin.
Dokku being mainly aimed at people running a single standalone server.
ContainerShip Cloud (https://cloud.containership.io) is a hosted service that lets you launch and scale ContainerShip clusters with a click across multiple providers. You can backup clusters, share them, and move them between clouds.
Is anyone even using CF anymore especially in production? The spring/tomcat jee based setup seems a bit antiquated when there are so many lighter weight alternatives available.
It has built in high availability, automatic clustering of nodes, loadbalancing, service discovery, persistent data management, internal DNS, and support for easily extending the core of the system with plugins (plus more).
Of your examples I would say it is most like Openshift Origin. Dokku being mainly aimed at people running a single standalone server.
ContainerShip Cloud (https://cloud.containership.io) is a hosted service that lets you launch and scale ContainerShip clusters with a click across multiple providers. You can backup clusters, share them, and move them between clouds.
I wrote a getting started post that shows step by step how to use ContainerShip on DigitalOcean that may be of interest: https://medium.com/containership-articles/getting-started-gu...