I think it depends who's doing what themselves. For some, IaaS is more interesting, but for experienced application developers PaaS is likely to be very interesting as it provides higher utilization and choices of isolation (i.e. virtual or paravirtual). I always wonder if RightScale is a PaaS, though... I think of a platform as a thing you can build other things on (a framework for development) and I think of a project as a resource pool of developer ideas. I know that industry designations referring to cloud delivery intend to shed light on service level agreements, so I understand why we're saying it's not really PaaS as we know it. I still wonder if RightScale is a SaaS dashboard managing IaaS across clouds or if it's evolving into a service catalog of platform services... and maybe wondering and continuous curiosity are good things since we're dealing with services and people change when they move around and surround themselves differently... therefore services change and solution stacks can reproduce themselves asexually as new people have problems you've solved with the same old solution you invented in the beginning. For RighScale access to resources across multiple clouds is key right now, but client requirements and services change over time and PaaSification could happen at some point couldn't it? You can already instantiate a cloudfoundry deployment from the multi-cloud marketplace so it will be interesting to see what developers might require as customers of RightScale-as-a-non-platform-service.