no cloud based still has instances that do restrict CPUs and ram etc, as windows instances require these to work 
but they are flexible in the manner that we can add on demand CPU and RAM if required.
Even in amazon, and many others you still have max limits that can hit in the instance if you have an OS there.
There is another sense of the ‘cloud’ in that there is no real ‘frontend’ server
For hsphere to work, we still have to have a front end. At some point it MAY be possible for us to make a load balanced frontend that allows multiple windows instances to reply requests, and we are certainly looking into that, but at this time they are cloud instances, running on elastic CPU, RAM, network, and storage infrastructures.
Essentially what makes a cloud is a storage medium that is stored on the network with large ‘nodes’ that work together, however an instance and only access limited numbers of these at one time, and in this case windows will max at 4 CPUs with the Hyper-V infrastructure we are using. We have looked into some of the VMWare a bit, but it would not be cost effective for us to move, and in all ways still limits the windows instances as this is
vSphere up till Enterprise edition limits to 4 CPUs, just as Hyper-V does, and enterprise edition Vsphere allows 8 vCPUs for windows to address, so you still have some level of ‘maximum’ per instance.
however with this we can do things differently.
Let me use CF for example. ODBC is notoriously bad on it, taking down everything.
We are about to change all that in how it works. We are going to make many small instances, with less RAM and CPU allocations than the dual cpus, quad cores, dual cores etc we use now, putting instead just a dual vCPU, 2GB RAM instance, with only a handful of accounts on it, this will in turn not SOLVE the odbc issue, but it will prevent it from being noticed as widely since there will be less accounts per ‘server’ that Hsphere sees.
BTW there is a lot about what exactly a ‘cloud’ is, and we hope to address all those in the coming months and years, not in definitions but in functionality and services, no it won’t all be on Hsphere as that simply won’t support it.
What Mosso did with allowing php on linux instances asp.net on windows instances in a near seamless manner wasn’t and isn’t as rackspace cloud a perfect solution, but it was a nice step adding the load balancer a level of intelligent routing by platform as well as availability. I am not saying we will emulate this in any way, but it was a nice thing that was removing the ‘os’ from the user equation, which will in the end be the ultimate ‘cloud’ solution as I’d vision it. there will always be limits, a cloud doesn’t magically remove limits at all. in fact it introduces some, what we’ve done here doesn’t require special coding etc. To work with these past solutions sessions had to be re-written, using DB backends only, or various other session passing workarounds, making a lot of complexity. What we’ve done is make the instances on top of it, integrated to hsphere for the best of what we can offer to the user right now, without requiring extensive changes in billing, setup or plans. In fact there will be some plan updates soon 