Moving AWS/GCP/Azure plugins to open-core model

Michal Brutvan

Michal Brutvan

Header Image: Moving AWS/GCP/Azure plugins to open-core model
We are making changes to AWS, GCP and Azure plugins: Starting today and with their latest releases, these plugins are switching to an “open core” model. This change means that each plugin will be partially open source and free, but it will also provide optional advanced functionality and support for additional resources (tables) in a premium mode.
This change allows us to keep most of the plugins open source and fund the development from more advanced complex use cases.

What you need to do

If you only want to use the existing free tables of an open-core plugin, you do not need to do anything.
If you want to sync premium tables, add the table names in the CloudQuery configuration and make sure the CLI is authenticated. You can do this using the cloudquery login command or by setting an API key.
To find the list of premium tables, see the plugin documentation on CloudQuery Hub.

What about CloudQuery framework?

CloudQuery framework and SDK will always remain open-source, empowering developers to create their own plugins for free, internal use, or to sell on our Marketplace.

We would love to get your feedback!

Let us know what you think, we would love to hear your feedback on our plans! If you have any questions, comments, or suggestions, please feel free to reach out to us on DiscordGitHub, or just book a meeting.
Subscribe to product updates

Be the first to know about new features.