# Inquiry about CloudQuery plugins and their current source status

**URL:** <https://community.cloudquery.io/t/inquiry-about-cloudquery-plugins-and-their-current-source-status/387>\
**Category:** CloudQuery Plugins\
**Created:** [February 8, 2024, 10:48pm UTC](https://community.cloudquery.io/t/inquiry-about-cloudquery-plugins-and-their-current-source-status/387 "2024-02-08T22:48:37Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![uncommon-pelican](https://avatars.discourse-cdn.com/v4/letter/u/c57346/32.png) [@uncommon-pelican](https://community.cloudquery.io/u/uncommon-pelican)\
**Post date:** [February 8, 2024, 10:48pm UTC](https://community.cloudquery.io/t/inquiry-about-cloudquery-plugins-and-their-current-source-status/387/1 "2024-02-08T22:48:37Z")

</div>

Hello CQ team,

We are reviewing CloudQuery as an option to set up a cloud asset inventory for AWS and Azure, and I’m spinning up a demo without an account. I noticed that the plugins used to be published in the main repo `cloudquery/cloudquery`, but they seem to be stale now. When using the `./cloudquery plugin install` command, they seem to be downloading from a GCP storage bucket. I can see that the update of the latest plugins (i.e., Azure Jan 31, 2024) are more recent than any change in the plugins directory (`cloudquery/cloudquery/tree/main/plugins/source/azure` Dec 22, 2023).

Are these plugins closed source now?

---

<div class="post-metadata">

**Author:** ![yevgenyp](https://avatars.discourse-cdn.com/v4/letter/y/3be4f8/32.png) [@yevgenyp](https://community.cloudquery.io/u/yevgenyp)\
**Post date:** [February 8, 2024, 10:52pm UTC](https://community.cloudquery.io/t/inquiry-about-cloudquery-plugins-and-their-current-source-status/387/2 "2024-02-08T22:52:59Z")

</div>

Hey! We host all the plugins today as part of our hub at [hub.cloudquery.io](https://hub.cloudquery.io) (underneath we use GCS for the storage).

The Azure plugin is open core; it contains some tables that are closed source. You can see which ones on our hub and the open core announcement on our [blog](https://yourbloglink.com).

---

<div class="post-metadata">

**Author:** ![uncommon-pelican](https://avatars.discourse-cdn.com/v4/letter/u/c57346/32.png) [@uncommon-pelican](https://community.cloudquery.io/u/uncommon-pelican)\
**Post date:** [February 8, 2024, 10:55pm UTC](https://community.cloudquery.io/t/inquiry-about-cloudquery-plugins-and-their-current-source-status/387/3 "2024-02-08T22:55:00Z")

</div>

Does that mean that the plugins no longer live in the `cloudquery/cloudquery` repo and they cannot be audited?

---

<div class="post-metadata">

**Author:** ![yevgenyp](https://avatars.discourse-cdn.com/v4/letter/y/3be4f8/32.png) [@yevgenyp](https://community.cloudquery.io/u/yevgenyp)\
**Post date:** [February 9, 2024, 2:42am UTC](https://community.cloudquery.io/t/inquiry-about-cloudquery-plugins-and-their-current-source-status/387/4 "2024-02-09T02:42:41Z")

</div>

It does live under `cloudquery/cloudquery` but premium tables live in a private fork. [Link to announcement](https://www.cloudquery.io/blog/announcing-open-core-plugins)  
If you need access to the full source for audit or other purposes, feel free to pick a slot [here](https://calendly.com/yevgenyp) and we can provide it as part of an enterprise contract.