Updated MQ Status
This is a convenient status-update page for those service providers participating in the Cloud IaaS Magic Quadrant.
Last update: Tuesday, November 19th, 2013
The last “Magic Quadrant for Cloud Infrastructure as a Service” was published on August 19th, 2013. (If you’re not a client, see the free reprint.)
In 2014, we will be doing four Magic Quadrants: Cloud Infrastructure as a Service, plus three regional Magic Quadrants for Cloud-Enabled Managed Hosting (evolving the existing Managed Hosting MQs for North America and Europe, and adding Asia-Pacific).
Cloud IaaS MQ
The “Magic Quadrant for Cloud IaaS” continues the 9-month update cycle for the Magic Quadrant for Cloud IaaS. Like the previous Cloud IaaS MQ, it will be focused on true cloud IaaS — self-service, highly-automated, and on-demand, targeted at IT organizations that want to obtain virtual data center resources and manage the operations themselves, whether those resources are multi-tenant or single-tenant, hosted by the service provider or on-premises. (It is strictly a service provider evaluation, focused on highly-standardized offerings, and even though private cloud IaaS will be part of the evaluation, providers must have a public cloud IaaS offering to qualify.)
The MQ is expected to proceed according to the following approximate timeline:
- December 9th: Confirmation of contacts.
- January 6th: Send out the survey.
- January 20th: Deadline for returning the survey.
- January 27th: Inclusion notices sent out.
- February 10th: Deadline for briefings for included vendors.
- February 17th:Deadline for supplemental data.
- Week of March 3rd: Draft for vendor review.
Like all Magic Quadrant timelines, this one is subject to change.
Cloud-Enabled Managed Hosting MQ
These new Magic Quadrants cover the market that is created by the intersection of managed services and a cloud-enabled infrastructure platform (which might or might not be cloud IaaS). They will be conducted essentially simultaneously with the Cloud IaaS MQ, in an effort to reduce the amount of work that these MQs represent to vendors. They will, however, publish after the main Cloud IaaS MQ. (More on this to come.)