What do you prefer, and why?<p>Other than the support plan, I don't quite understand why I should use EY instead of Heroku. Why do you use one instead of the other?<p>Thanks!<p>Edit: I use Heroku but I see a lot of companies using EY.
I use EC2 for one project and Heroku for everything else. I don't think I'll use anything besides Heroku moving forward because it's so ridiculously easy to set up and use.<p>A couple days ago, I needed to set up a new website, so I registered the domain at Godaddy, created a new (free) app on Heroku, and pointed the new domain at the Heroku app via the free, integrated Zerigo solution. I had the app running on a Heroku subdomain within minutes, and was done within 4 hours, including domain resolution.<p>The speed and cost at which I can produce and validate an idea on Heroku is unmatched by anything else I've seen. Outside of the cost of the domain and my time, I have zero costs to toss a domain up on Heroku. If the idea bears fruit, I can transition over to a paid Heroku plan and keep running with it. If it doesn't, there's no real loss to me.<p>Meanwhile, it doesn't look like EY offers anything that would cost me less than $85/month.
Both are great, but different. EngineYard provides much more.<p>For example, I'm an EngineYard customer. EngineYard developers and support people have spent upwards of 100 hours with me discussing more advanced needs for security, scaling, integration, and professional services.<p>EngineYard's leadership has especially impressed me with Rails 3, JRuby, and Rubinius.<p><a href="http://www.engineyard.com/company/press/10-06-09-engine-yard-announces-ga-of-rubinius-1" rel="nofollow">http://www.engineyard.com/company/press/10-06-09-engine-yard...</a>
Use EngineYard if you need better control over servers, installing custom unix packets and stuff like that. Use Heroku for everything else. I've had great experience with both companies, so I believe that you can't go wrong with any of them.