@Livers This is a complex question, but, no, I don't think you need to remove the requirement. I think you imply that its not doable. > ..."the customers have to manage business continuity" indeed! i have heard others say it more harshly: blame application architecture, not infrastructure for failures. BTW, i assume that when you say "the providers" you mean the SaaS companies building on top of IaaS. the exact answer depends very much on the particulars of you applications. but, here is one idea. you can have your primary environment in one cloud and a 'warm' backup in a second cloud. what i mean here is that on the second cloud, you keep a database slave node that you are replication onto it so that you have an up-to-date copy of your data there. if you are using tools like rightscale, you can use servertemplates such that you have all the configurations of all your other app servers ready to launch in the second cloud. this also means you are only running (and paying) for one server on your DR (cloud) site but have the ability to launch the rest of your environment quickly if necessary. if you are using log shipping to sync to your remote db slave node, you can keep track of where thing broke down and recover from there between the two sites. we recently had two of our senior guys speak about many different type of failure scenarios and how to plan for them in a webinar: http://www.rightscale.com/info_center/webinars/outage-proof-cloud-apps.php if you want to talk to one of us to discuss you question specifically, we are always open to chat one-on-one. just email firstname.lastname@example.org and we can get a sales engineer with multi-cloud experience to explain how we do things.