paas

It's not a PaaS, rather, it's (some of) the building blocks to create your own PaaS.

It's a complete solution for running containers that feels like a PaaS, but without all the opinionated crap associated with a PaaS.

We run Docker in production, as a PaaS no less, and this reads like a list of reasons to use a new-generation PaaS.

The whole point of a PaaS is to not code to an API.

If you're excited about building big data architectures and creating a PaaS then you should talk to us.

Purely in terms of the cost structure you could offer with such a PaaS, this could be a Heroku killer.

Instead of paying to use a multi-tenant, black box PaaS, you can have your own for a fraction of the price.

Currently, PaaS provisers such as RDS and Heroku Postgres don't support and it would not be easy to setup it manually.

Definitely a stark contrast from a lot of other PaaS providers (in particular, Heroku).

Bluemix is the best example of our commitment to this space and the Compose services are a natural complement to that PaaS environment.

And you're never investing in IT if you are doing IaaS or PaaS: you're just paying a third party for a temporary good.

Comparing to a self-hosted PaaS is fair for the open source containership project.

If you want to put files on a server and start a process, you are probably looking for something like Apache, not a "PaaS" necessarily.

They wanted Azure to be a lock-in PaaS, and only when they realised customers didn't want to deal with that mess did they go after IaaS and start "embracing" open source and Linux.) I apologize for the rant, but I do blame MS for doing all they can to drive developers and ops away from Windows,.