Hey Thorsten, I've been using a service called Scalarium which essentially is what OpsWorks has become for a number of years since we moved off of RightScale (I'm sure you remember). And essentially, believe it or not: what you call lack of features — that is all we required. Scalarium is/was fully customizable through Chef. Something you guys are offering as well nowadays. And at the same time it comes with the benefit of not having to run a Chef server setup yourself. It also makes a few assumptions/choices for the user as to how the deployment should run, and we welcome these choices. Chef (specifically chef-solo) enables us not just to deploy on Scalarium or OpsWorks. We also use the same recipes to bootstrap developer VMs (Vagrant) or bootstrap a couple servers which are not on AWS. So there's no real vendor login or similar either. Add to that, if I decided to move to a full chef server setup, I'm almost there. I am sure OpsWorks will integrate with other services down the road — they already do a great deal with IAM. I also think they will keep this tool as open as possible: in case you noticed it comes with a haproxy role when technically there is a service (ELB) for that? With OpsWorks I can also run my own Memcached servers if I don't want to use ElastiCache. I can install my own MySQL server if I don't want to use RDS and the list goes on. As for adoption — I'm pretty sure their pricetag will be convincing for people who are running on top of AWS already. And yeah, point taken, AWS will not support Rackspace and whatever else is out there. But that wasn't a problem for us either. AWS is still the leader in cloud computing and nothing right now comes even close. I personally welcome this tighter integration (of Scalarium) into the company which owns and runs the PaaS. Looking forward to the service and stability and wish them overall best of luck.