CloudQuery News

Important Update: CloudQuery Official Free Plugins Moving to Paid

• April 22, 2024

Edit (June 14, 2024) At the time of publishing this announcement, the AWS, GCP, and Azure plugins still had a subset of tables that were free to sync. The latest versions of these plugins have the free tables reduced to only tables that contain static data with large amount of rows, such as aws_appstream_images or azure_authorization_provider_operations_metadata. These tables are marked as Free in the plugin documentation.

Edit (December 18, 2024) Documented the process of upgrading CloudQuery integration from free to paid tier.

We recently announced that we were moving our plugins from free to paid, starting with AWS, GCP, and Azure. Today we are finalizing those with other plugins in order to ensure that CloudQuery is sustainable and can provide the highest quality plugins.

Here is what this means for you:

Free Usage Up to a Quota: You can still leverage the functionality of our paid plugins, up to a designated monthly quota. This allows you to explore the power of CloudQuery without initial investment.
Pay-Per-Row for Continued Usage: Once your usage exceeds the monthly quota, a fee will be applied based on the number of rows processed. This ensures fair pricing based on your actual needs. See our pricing page for the details.
Open Source Legacy Available: We understand the value of open-source contributions. Previous versions of our free plugins will remain available on our GitHub repository for those who prefer this model. However, old versions won’t be maintained.
New Free Plugins: We will continue to accept free plugins for the Hub. Those will be community-supported with no SLA..
What is open source: CloudQuery SDKs are open source under the permissive Mozilla Public License (MPL) to enable users to write their own custom plugins and use the same engine that powers the official CloudQuery plugins.

This change empowers us to dedicate more resources to developing new features and functionality for all CloudQuery users.

We appreciate your understanding and continued support. If you have any questions about these changes, please do not hesitate to reach out to our team.

How to Upgrade CloudQuery Integration from Free to Paid #

Step 1: Update CloudQuery CLI #

Via Homebrew:
- Upgrade to the latest version:
  brew upgrade cloudquery/tap/cloudquery
- To install a specific version:
  brew install cloudquery/tap/cloudquery@<version>
  (e.g., brew install cloudquery/tap/[email protected])
Alternatively, download the latest CLI version from the Releases Page.

Step 2: Log In or Generate an API Key #

If you need to set up a new CloudQuery account, be sure to contact us to get set up. If you already have a CloudQuery account, you can proceed with the following steps:

For Local Environments:

You can log in by running:
```
cloudquery login
```

This is the easiest option for local testing or development.

For Production Environments:

Follow the steps in the Generate API Key Documentation.
Use the CLOUDQUERY_API_KEY environment variable during the sync process:
```
export CLOUDQUERY_API_KEY=<your-api-key>
```

Step 3: Review Plugin Changelog for Breaking Changes #

If upgrading from an older plugin version, check the plugin’s changelog on the CloudQuery Hub, and review breaking changes and update your configurations or table queries accordingly.

Step 4: Run the Sync Process #

Once updated, run the sync as usual. The CLI will prompt you to log in or provide the API key if required.

Step 5: Verify Migration #

Validate the upgraded plugin’s tables and functionality, you will need to make sure your queries and workflows align with the new plugin version.

Summary #

Upgrading to a paid plugin is a straightforward process, but if you need assistance or have questions, we're here to help!

Contact us to discuss upgrading.
Join our Community to connect with other users and get support.
You can also try CloudQuery out locally with our Quick Start Guide.

Written by Yevgeny Pats

Yevgeny Pats is the Co-Founder & CEO at CloudQuery. Prior to establishing CloudQuery, he successfully founded and exited other startups. He has a background in software engineering and cybersecurity.

On this page