Product Update: Cloud Sites

Cloud computing is quickly evolving.  At Rackspace, we naturally embrace change by continuously evolving our products and services to support the unique needs of our customers.  Cloud Sites is not an exception.

We’re fully committed to the Cloud Sites product and are in the process of expanding the team dedicated to the ongoing development. In the near future, Cloud Sites will offer:

• Improved DNS management capabilities to give users more control in managing their domains on our system.
• Better interoperability with other cloud products to provide a seamless experience with integrating different cloud resources.
• Public API access to provision and manage web sites and other resources.
• PHP 5.3 and .NET 4.0 language support providing users the ability to deploy new sites or automatically update their existing sites to the framework of their choice.

This is an exciting time for Cloud Sites, and as we continue to develop the product, we appreciate any feedback you have.  We invite you to submit suggestions through our User Voice customer feedback site,, where customers have the opportunity to discuss and vote on features that are most valuable to them.

Josh leads product development for the Cloud Platform Product Line where he is responsible for product management, engineering, and operations for the Cloud Sites, Load Balancing, Database and DNS product offerings.


  1. All sounds great and very exciting. Hopefully one of the “better interoperability with other cloud products” offerings will include a backup solution, which now has over 700 votes at User Voice and has been the #1 request for months now. Any chance RS could provide us with an update on that request?

  2. This post sounds encouraging, but I must admit I’m a little concerned with Rackspace’s commitment to Cloud Sites. I have put many of my clients on the Cloud sites, so I am hoping you don’t have any plans to discontinue the service.

    But it almost seems the way it is now presented on Rackspace’s website that you don’t want new customers to choose to use it. If you click on Cloud Hosting’s main tab, it is not even mentioned on that page, except in a little link. It seems to me that the writing is on the wall to eventually discontinue you it.

    I hope I am wrong, but maybe you can explain to me why there is so little mention of it if you are really committed to it?

  3. This post sounds like the same old same old.

    One day we will have ……

    “• Public API access to provision and manage web sites and other resources.”

    I remember that was going to be completed…. let me see, hmm 2 years ago. That’s why I signed up.

    A basic API isn’t innovation or product evolution, it is a necessity, and one that still has no delivery date, just further feel good lip service to “it’s coming one day”.

    On the other hand, I find it curious that the one selling point that differentiated this product from any other on the market (I could find) was the 24 X 7 end users support for $3 per month per client. This post makes no mention that “We will stop providing support for end users effective July 28, 2011.” Amazing how bad news has a fixed date and good news lives nebulously in the future.

    I agree with Michael Falciglia, I’m a little concerned too with Rackspace’s commitment to Cloud Sites. With no clear tool to migrate existing sites elsewhere, and the core nature of the product being diminished, at what point do I say its easier to give my customers to Rackspace, then to move them elsewhere.

    This look and feels like I’ve been recruited to build their shared hosting business under the guise of “neutrality” however the rug is now being gently slipped out under my feet and the customers tumble into Rackspaces lap.

  4. Josh,

    Really excited to hear about the commitment and the upcoming development for Cloud Sites. There are still a number of suggestions on the feedback site that haven’t received a response in a while though. Could we get some clarification there? Would be appreciated!

  5. Haven’t had a chance to read the feedback site, but when ‘upgrading’ to PHP 5.3, please don’t kill PHP 5.2. It’s stable, it works and is still supported.


Please enter your comment!
Please enter your name here