Cloud Blog

WSO2 Cloud Pricing Changed

WSO2 Cloud has been around successfully for more than 5 years. We introduced “WSO2 Cloud – Beta” in 2014 and went on to commercially launch the service in May 2015.  At that time we  introduced a tier based pricing model for WSO2 API Cloud and WSO2 Integration Cloud. The pricing for WSO2 Identity Cloud was based on the number of users.

Very recently WSO2 announced a new pricing strategy for on-premises customers. With the new WSO2 pricing strategy, WSO2 Cloud also rolled out a new pricing model for all cloud offerings from the beginning of Q2 2019. Following are the key highlights of the new pricing model:

  • The pricing model is similar across all cloud offerings and includes just two pricing tiers, namely “Micro” and “Standard”. For those who have requirements beyond these two plans, a custom tier can be requested.
  • There are no feature limitations across tiers. All the features are supported in all the tiers. This is a bold step we took to provide users the freedom and flexibility to decide on the best pricing plan in a simple and straightforward manner. The new approach to pricing places us in a unique position compared to other cloud vendors who restrict features depending on the pricing tier.
  • Following is how each cloud controls the usage per pay.
    • API Cloud – Monthly API call volume
    • Integration Cloud – Allocated CPU and memory resources for the applications
    • Identity Cloud – Number of authenticated users in a month
  • Public cloud pricing can be combined with on-premises pricing for the customers who use both cloud services and on-premises products. This eases the procurement process for users and also provides the flexibility to pay for both subscriptions at once.
  • If you are running any on-premise components such as on-premise gateway, they are changed following the WSO2’s on-premise pricing.
  • Standard tier gets one pre-production environment for free. If you are buying the Micro tier and if you want a pre-production environment, you need to buy another Micro tier subscription for it.
  • Similar to the old pricing, users can pay on a monthly basis or annual basis. Those who opt to go for annual payment receive a 10% discount.

Following table depicts the resources you get in each tier for each cloud offering per month. As explained above, the numbers given below are the only controls imposed on the subscription.

What happens to the existing customers?
We will not do any changes to the pricing model of our existing customers. We will continue to grandfather them for as long as they wish. If existing customers want to migrate to the new pricing model, they can easily do so by contacting us.

We recommend you to have a look at the pricing pages of API, integration and identity clouds. If you need any clarifications, do not hesitate to reach out to us via cloud@wso2.com. In our next blog post, we will take you through different pricing scenarios relevant to API cloud.

Go hybrid with WSO2 Cloud Microgateway: Join our webinar to learn how

WSO2 API Cloud provides a fully fledged, easy to use hybrid API management solution, which supports the best of both cloud and on-premises API management. WSO2 Cloud Microgateway is container-friendly. Since it can run in any infrastructure, it supports multi-cloud deployment, which relieves you from vendor lock-in as well. The latest addition to WSO2 Cloud Microgateway is the ability to add labels to group APIs so that it is possible to selectively deploy APIs by configuring the microgateway with a required label.

Our upcoming webinar “Deep-Dive into Hybrid API Management with WSO2 Cloud Microgateway” is a good starting point for anyone looking at adopting a hybrid API management approach. This will happen on Wednesday, July 31, 2019 from 9:00 a.m. – 10:00 a.m. (PDT).

In this webinar, we will discuss and demonstrate:

  • Hybrid API management
  • WSO2 Cloud Microgateway:
    • Overview
    • Key features
    • API grouping
  • Microgateway Deployment options:
    • Multi-cloud deployment
    • Deploying in containers

Click here to register and reserve your spot to learn about hybrid API management with WSO2 Cloud, and to go through a quick demonstration of a sample use case.

Overview of the sample use case

We will also have a live Q&A just after the demonstration. This is a great opportunity for you to ask questions and clarify any doubts you may have.

Hope to see you there!

Explore What’s New in WSO2 API Cloud

We have made great progress with WSO2 API Cloud and we are excited to introduce the latest features and enhancements to WSO2 API Cloud.
WSO2 API Cloud can now help you solve many more of your business requirements with the following new features and enhancements that we have rolled out:

  • Hybrid API Management via Microgateways:
    You can now go for hybrid API management with WSO2 API Cloud using the Microgateway that we’ve introduced. You can basically run the Microgateway anywhere, including in Kubernetes or Docker environments. For detailed information, see our documentation on Hybrid API Management.
  • Labels to group APIs and support to deploy grouped APIs via Microgateways:
    If you have a business requirement where you want to group a set of APIs together, now you can create a label and attach it to all the APIs that you want to group together. Once you group APIs together, you can deploy the grouped APIs via a Microgateway. For more details, see Deploying Grouped APIs Using a Microgateway.
  • Enhancements to API analytics:
    We have made significant changes to the internal analytics architecture to improve the overall real-time analytics capabilities. To learn about the real-time API analytics capabilities that we provide, take a look at our documentation on WSO2 API Cloud Analytics.
    Since our former approach of triggering alerts based on percentile values was complex to understand, we now provide support for you to trigger some of the alert types by configuring required threshold values per API. You can configure threshold values for the Abnormal Response Time and Abnormal Backend Time alert types via the Publisher, whereas the Abnormal Request Count alert type can be configured via the Store. For detailed information on how you can configure alert types, see Configuring Alerts.

Do try out WSO2 API Cloud to understand how our enterprise-ready solution for creating, publishing, and managing all aspects of an API and its lifecycle can help you quickly share business capabilities with customers and partners across the globe.

 

Categories

Recent Posts

Most Popular Posts