The criteria for Gartner's Magic Quadrant for Enterprise High- Productivity Application Platform as a Service


It's not easy to be included in Gartner's Magic Quadrant - any of them - because there are many inclusion and exclusion criteria. To give you a glimpse of the requirements, we highlighted the requirements for the Enterprise hpaPaaS Magic Quadrant for you. Source: Gartner
Obviously, the platform must be a cloud service, with the following characteristics:
- Available by subscription and accessible over internet technologies
- Available uniformly to all qualified subscribers
- Including some sharing of physical resources between logically isolated tenants (subscribers or applications)
- Including some self-service provisioning and management by subscribers
- Including bidirectional scaling without interruption of activities and with some automation
- Including some instrumentation for resource use tracking

It has to be an application platform as a service (aPaaS) offering:
-It encapsulates the underlying virtual or physical machines, their procurement, management and direct costs, and does not require tenants to be aware of them (optional access is okay)
- It delegates to the providers the patching, versioning and health of the platform stack

It has to provide a minimal set of aPaaS capabilities
- Support for the deployment of applications utilizing data schema and application logic
- Includes tools to develop, version, test, deploy, execute, administer, monitor and manage the applications and their relevant artifacts
- Allows for functional extensions through external or third-party services.

It has to provide hpaPaaS functionality
- It provides a low-code or no-code approach to application development It supports development and deployment by citizen developers
- It includes single-step deployment
- It has to be enterprise-grade and aimed at enterprise-class projects

The provider taking some responsibility for
- High availability and disaster recovery
- Security of access to application services
- Technical support to paying subscribers.
- Enabling third-party application access to application logic and/or data via services

It has to be provided as a "stand-alone" service
The platform's clients can subscribe to only the aPaaS capability and not to some other optional cloud service — for example, a SaaS application or another form of PaaS, such as BPM PaaS or dbPaaS — of which the aPaaS capabilities are just an "embedded" subset.
- It has to be generally available, with more than 200 organizations as paying customers (as of 1 September 2016).
- It has to generate an estimated revenue of at least $4 million (or equivalent) per year (that is, for the 12 months ending 31 August 2016).