> From our perspective, it was a matter of helping our partner and the Ruby community succeed.

I suppose what seems confusing to me is that there are a lot of things you could do to help your customers succeed, but many of them are fairly expensive - such as cutting your rates, or doing high end development work.

With more basic hosting, say EC2, I know that Amazon isn't going to do beans for me, so I'm on my own. I know exactly what the price does and doesn't include, and what I have to provide myself. EY seems fuzzier... it's almost like having an extra developer on staff in terms of talent, but it is and it isn't: you can't tell that person to go off and do something else.

Say I move one of my sites to EY; is your "whatever it takes" attitude going to include fixing up my ugly design/graphics work?:-)