A little experimental app could easily start to overrun limits without the user knowing and run up a huge bill, and this is the only thing about their service which I found unsettling - it gives the impression they're happy to trick you into paying more than you wanted, which I'm sure is not the intended one.
With Engine Yard you get a proven, scalable, and supported Rails stack, except you retain complete control over it. You have a dashboard and support desk, but you also have root access and the AWS keys. There is complete transparency in what you are charged, and you can run anything you want, just add a chef recipe, you don't have to be nickled and dimed by an add-on or external service just because you need a different piece of software.
Heroku is great if it fits your use case, but if it doesn't then there's no reason you have to go completely vanilla EC2.
Why would you assume this? I explicitly remember using the beta databases for free with the understanding that with the continued usage of those products outside of the beta period, I'd be charged.
Never assume. Always ask if you aren't sure.
> notice will be provided to all beta users prior to GA release
The only notice I received was in the email newsletter (which I didn't read). It seems reasonable to expect a specific notice based on the language in the blog post.
I am not affiliated with Cloudfoundry and earn no money from them neither do i have any formal relationship with Vmware. I am bullish on cloudfoundry and use bosh multi-instance and multi-cloud deploy. You can see how cloudfoundry works by testing the commercial version on cloudfoundry.com and the opensource community based articles on cloudfoundry.org.
You can run Java, Ruby, Node, Python, PhP tec and comes preinstalled Postgresql, Mysql, Mongodb, Redis, Rabbitmq.
Go give it a ride.
Shameless Plug: There are much more cloud services out there these days. It's not just two. Have a look at the PHP ones here: http://blog.fortrabbit.com/comparing-cloud-hosting-platforms...
What the new interface appears to do is that it forces users to RTFM. Probably the first step every user in a self-serve system should do before opening a ticket.
After you have searched for the info, then probably you should open a ticket.
Now, if you have premium support. That is a whole new story.
As for current invoices amount, the old dashboard used to show you your current usage. I'm not sure when this got lost, but the new dashboard doesn't have it.
I can pretty much guarantee that Heroku are fully aware of both of these problems and acting on them…
When I did find it their customer service was just nasty. "He doesn't have time..." after the fact I was willing to spend a couple hundred dollars doing business with them. He told The irony here is heroku is owned by salesforce....
OP then proceeds to cite the email which verifies just that:
"We will also begin billing for the paid plans as of August 1st"
Regarding opt-in, he has already supplied his payment info as an existing customer.
Since OP expected this, and did not check in August, I can't help but feel this rant is a bit unmerited. Blaming Heroku is not entirely justified here.
So these knocks against Heroku don't ring true for me. I even have to wonder if the author overlooked pointers/responses/notices (as with his opt-in-before-billing-begins assumption).
I'm an apps guy, not devops, and definitely not ops. I can manage an AWS deployment if I have to, but it's not on my top ten list of activities that I consider to be fun.
That said, it is still way too difficult to find.