announcement
AWS/GCP/Azure plugins pricing changes
Yevgeny Pats •
Hi everyone, we are doing price changes to our AWS, GCP and Azure plugins and this will explain what the changes are, why we are changing it and who might be impacted. If you do have additional questions, please feel free to reach out to us via our support channel and we will get back to you right away.
In the last 6 months, we started looking at how we can turn CloudQuery into a sustainable business by experimenting with different business models. For our most popular plugins (AWS, GCP and Azure) we did this by adding new paid features, tables and doing volume based pricing. We did see some limited success, but for the most part it skewed our premium tables and features to be very expensive – to the point of not being affordable or worth going through procurement, given how much is available for free. Given those findings, we will be rolling out new versions of these plugins (old versions won’t be affected) where we move 80% of the tables to paid tables. This will make most of those plugins paid but hopefully should be affordable for everyone and make it sustainable so we can re-invest into adding new features, fixing bugs, improving performance, monitoring and so on.
Who is not impacted:
- Anyone using old versions of those plugins.
- Current paying customers are not impacted and price will remain the same for the next 12 months.
If anyone is in a PoC or has a production deployment of our free version and wants to upgrade to the latest versions, please reach out to us here and we will enable a prolonged free trial of 2 months for them to be able to see what the estimated cost is and see if CQ makes sense with the new pricing. This will also help us adjust the pricing to make sure it is affordable with the new split of tables. If there are special circumstances, such as long procurement processes or anything else, we are happy to work with you and potentially provide longer trials.
So what is open source and what not? CloudQuery Framework (SDKs) in all languages are open source while CloudQuery plugins are commercial and closed source (apart from some example plugins and some small amount of tables for AWS, GCP, Azure to give some flexibility and for learning purposes). Open source CloudQuery SDKs allows you to develop your own CloudQuery plugins without restrictions. Authors publishing their plugins to the CloudQuery Hub can choose whether their plugins are to be free or paid.
Hopefully this makes sense, I'm happy to answer questions and listen to additional feedback.