>Part of the big ease of Heroku is, that you don't have to create Heroku before you use it. I agree. It defeats the purpose of services like Heroku where users

>Part of the big ease of Heroku is, that you don't have to create Heroku before you use it. I agree. It defeats the purpose of services like Heroku where users want a place to upload code and have it just work. You also make a good point on maturity. It took many engineers years to make Heroku a mature product and keep it humming. I do think this stuff is cool though. There's definitely a place for this sort of thing but I don't know if it should be marketed as PaaS. As soon as something becomes DIY, I would stop considering it SaaS or PaaS. Full disclosure: I'm an Engineer at Salesforce which owns Heroku