$10 Million Round For Ruby On Rails Startup Heroku (YC W08)
techcrunch.com
techcrunch.com
From the design of their website to the naming schemes, the price points and so on it all seems to be equally well thought out.
Back when considering which platform to try next (python/django or ruby/rails) I was very impressed with the way they did their best to minimize the surprise factor and to really inform the user up front of what they're getting in to.
The documentation is also excellent. I still don't know if I made the right choice, but I'm a bit too far in to django now to easily back out again so I guess I'll stick to it, but to see Heroku has now found very solid financing is definitely a factor to consider.
http://blog.heroku.com/archives/2010/4/28/node_js_support_ex...
Not sure how much of that is just venting or how much it actually keeps some people at bay but it's pretty obvious some (anonymous people on an online forum, FWIW...) think it too costly.
Only then you'd be comparing apples-to-apples and then you'd see that by the time you've factored in the 24x7 system administration, monitoring, guy-on-standby for when you're on the road and so on that it really isn't that bad.
Of course it will be higher in absolute dollars if you don't factor in your own time and how much that costs, maybe there is even a small premium if you do, but outsourcing has other advantages besides the ones that translate directly in to money, and those can be valuable by themselves (for instance the time freed up).
If you can't make your business model earn back what Heroku costs you at a given scale then that is of course a problem, but if you can't do that then you probably have a problem anyway, and even free servers wouldn't solve that.
$ git init && git add . && git commit -m "init"
$ heroku create
$ git push heroku master
Subsequent deploys go like this: $ git commit -am "Changed some stuff"
$ git push heroku
(The book is currently in progress, but I've written 11 of 12 chapters, so it's likely to be done before you would have time to reach Chapter 12. Also, the current book uses Rails 2.3.5, but a Rails 3 version is also in the works.)EDIT: Also, the add-ons they have are really good, and they have a ton in the pipeline. They have all the tools I needed to get up-and-running (including a tool that sends your local DB to the production Heroku server or vice versa in one command).
With $10mm in the bank, 60k apps in the cloud, Amazon's AWS backend, Heroku's rockstar team, and a real revenue model, I think it's safe to say that you can bet your business on Heroku.
My new project sure as hell will...
If you really had to move off of Heroku (if they went under or become prohibitively expensive) you could move onto your own servers running essentially the same stack (except of course manually configured and maintained), which is more than you can say for AppEngine, for example.
Another interesting question is how well they scale. http://success.heroku.com/ has some interesting companies, but nothing with very high traffic (or am I wrong)?
PS. I'm a happy heroku user myself.
Given that their profit margin on a paying customer is not 100%, more like 15-20%, they would probably need 5x as much, or 10k paying customers, to cover the costs.
The basic bill would be much lower but I once you start adding addons the bills adds up quickly.
It's a great service and I'm glad to see it continue to grow.
One note on the article though, it says: "Heroku aims to make software development more accessible for a wider range of people. It does so by providing a browser-based programming environment that cuts out steps traditionally needed to produce RoR applications."
Didn't they cut that entirely? Even Heroku Garden is closed right?
I think they're roughly comparable but the deal breakers for me were Postgres, Addons, and the Git Workflow.
$10 million is a huge amount, it sounds like they have huge plans.
Think of money that you can get your hands on before you've earned it as a growth accelerator. You could for instance stave off a potential competitor by grabbing a larger share of the market than you would have been able to do if you both relied on organic growth. In the arms races that start-ups are bound to find themselves in sooner or later a couple of million in hard cash can make an enormous difference in the long term outcome.
But that's really looking at the tea-leaves, I have 0 evidence for any that.
It would make some sense though, given that they've ironed out a lot of the issues they had initially, their price points have been adjusted to the point where a lot of the users are happy (and I find it commendable how they worked with the userbase establishing how much was reasonable), the only thing they have to do now is sit back and watch it grow.
But they may have decided that sitting back and watching is not their style.
Time will tell, but I'll certainly be watching for any major announcement.
Heroku is a cloud-based deployment and hosting solution for Ruby apps (and soon to be Node.js javascript apps too). Google App Engine is for Python and Java.
The same exact code that you would deploy to a VPS can run on Heroku without issue, save some limitations like the read-only filesystem. That's a big plus.
A+ for ease of use, and as I learn more I see opportunities in other server environments. My cofounder is kicking up nginx, thin and padrino
My favorite heroku project (and personal first) http://imagebrowser.heroku.com enjoy. Semantic entity extraction and image browsing as well as search within twitter streams.
I have one app on heroku, it's probably easier to use, but I have more apps on Google Appengine with jruby simply because it stays free-er for longer. I've come up against Heroku's free limits.
I'm glad that they're successful. It's good when a good taste wins.