OpenShift vs. tsuru

I needed a PaaS provider that didn't drop all the time and it's hard to find a good option for PHP applications. Openshift takes care of it. They are a little behind on PHP versions, but that can be solved with a custom cartridge. It requires a little more elbow grease to get rolling when you want to implement something they don't already have, but their quickstarts are great to get rolling with the basics quickly.

Tsuru allows developers the necessary and dreamed autonomy, maintaining the infrastructure department confident and is very business oriented as it improves the time to market with safety. Where is the magic?! It is not just starting to treat people as adults(that is mandatory), you also need a system that automatically recover itself(self-healing) after any mistake, misconfiguration, infrastructure problem, etc and (auto)scale easily as needed. We have it for about 4 years at Globo.com using Tsuru PaaS, one of the most loved projects we maintain, totally opensource, powered by Docker, no vendor lock-in, no comercial version(what we use is what we provide) and very receptive to new contributions, discussions, and fix of serious issues(stop the line mindset). Tsuru manages applications with millions of users with no headaches. The main value is that tsuru allowed a new and desired culture, finally developer can have the freedow they want to deploy(the freedom comes with responsability) - thousands of deploys/month and increasing - with increased stability/availability of ours portals We can finally rest calmally at night and in the weekends, letting tsuru dealing automatically with any operational problem may happen. Try it in your company, you too deserve to be happy! https://tsuru.io https://github.com/tsuru/tsuru