Out of the box OpenShift has a variety of languages and frameworks as well as ProstgreSQL, MySQL, and MongoDB database options (plus custom cartridges). You get three free gears (i.e. containers) so up to 3 small apps.

I've only used it to create a small Python/Flask app http://wwos-bitmason.rhcloud.com/ but there are lots of examples and information on the OpenShift blog.

[Disclaimer: I work for Red Hat.]

I use OpenShift and I think it's fantastic. You can even install your own SSL cert on the free tier (if you register their "Bronze" level, IIRC) for no additional charge. It's perfect for a hobbyist project and then scaling it up if necessary.

Cloud Foundry. You can try it through Pivotal Web Services or BlueMix.

It reuses Heroku's code for several buildpacks, particularly Ruby.

I know that it works really well because (disclaimer!) I worked on the Cloud Foundry Buildpacks team for Pivotal.

How easy is it to migrate your database, app, addons and configuration from Heroku to Bluemix? I'm going to consider a new host once Heroku ends it's grandfathered prices on Feb 1, 2016.

I'd recommend Pivotal Web Services[0], aka PWS, aka "p-dubs", buuuut that's only because I work for the company running it :)

If you have a 12-factor app that pulls config from the environment, it should ideally not be too traumatic. Services are meant to be injected by the platform.

Apps should be the easiest part. Of the buildpacks: Ruby, Python and Node are based on Heroku's and are very nearly identical. Go is based on a community buildpack, PHP is a complete ground-up rewrite and Java is a ground-up rewrite maintained by the Spring team.

If you signup for PWS and you find things broken or missing, email me: [email protected], and I will find who can help you.

[0] http://run.pivotal.io/

I've used OpenShift and it's pretty straightforward to use. I don't feel like it's as easy to use as Heroku, but it got the job done. If I left my app idle (I think for 24 hrs or more), I noticed that it took awhile for it to awake when I tried to access it again.

So is it not in fact up for 24hrs if it has to wake up when you try to access it again?

According to https://www.openshift.com/products/pricing/plan-comparison the free plan idles after 24 hours of inactivity (https://developers.openshift.com/en/managing-idling.html)

However you can work around it by hitting your server with an http request every 24 hours, or upgrade to the Bronze Plan which apparently has $0 base price anyway so I'm not sure what the downside is.

Openshift user here: there is no downside. Bronze truly is $0/mo. It's just that you have to given them a CC number (while you do not need to do that for the "free" plan). Why the CC number? Bronze lets you pay for more features if you want them—but there's no obligation.

Are there any ways to be hit by surprise charges on Bronze? I'm assuming setting up a ping via the New Relic trick people used on Heroku is sufficient.

Also, for a relative novice, how easy is it to get a Rails or Sinatra app up and running?

My concern longer-term is that Openshift would go the same route as Heroku. Is there anything about their business model that might indicate that's not a major risk?

Do you know how powerfull the free gears are that one gets with each price plan? I have a fantasy basketball league that a few of my coworkers and I play and a free service would be ideal for that. Can the free gear (as a scaled app) manage a postgres database with around 600 MB, or would that be too much?

Note that, for some reason, they limit regions that can use their paid tiers. So, you can't use them if you're in third world countries like Australia or New Zealand.