CloudQuery plugin payment and compatibility issues with older versions

CloudQuery Plugins
1

I’ve been using CloudQuery for some time with old binaries, but I now need to redeploy. It looks like some of the plugins have become paid now. If the experts can answer a couple of questions, that would be great. My scenario is entirely self-hosted.

  1. Will the older CloudQuery version continue to work with the previous versions of the (unpaid) plugins?
  2. How does paying for the plugins work in this context? I didn’t get it from the documentation. I understand I’m going to be charged monthly, but where is it tracked if everything is self-hosted?
2

Hello @crisp-catfish,

Below is the announcement for transitioning the plugins to pay-per-row usage; you should find most of the information you’re looking for there.
CloudQuery Official: Free Plugins Moving to Paid

Regarding your questions:

  1. Older CloudQuery versions should, to the best of our knowledge, continue to work. However, they will not be receiving support or updates anymore; therefore, in order to get the latest features and fixes, you should consider upgrading.

  2. There are 2 tiers of plugins, a free one and a paid one. Furthermore, paid plugins have a free rows/month tier, which should be a safe starting point for trying out and testing. You can find the exact free row quota on the plugin details on the CloudQuery Hub. All of this can be monitored on CloudQuery Cloud under the Billing & Usage section of your team, while tracking will be linked through the CLOUDQUERY_API_KEY used when running syncs.

CloudQuery Cloud
CloudQuery Hub Plugins

I’ll link a couple of useful resources below alongside a deployment example to demonstrate how to use the API_KEY when running syncs, even on self-hosted environments.

CloudQuery Pricing
CloudQuery Deployment Guide

1 Like