As a user of JFrog SaaS, you may initially only subscribe to Artifactory. You will find that transfer of Data Transfer Quota is part of your billing cycles and that you have some maximum before you are charged additional “overage” fees.
When you then add Xray to your SaaS licensing, you may notice a spike in this quota usage (perhaps even double).
Note:
It is an expected and intentional design for Xray’s internal artifact downloads to count toward your SaaS data transfer quota (which may equate to a doubling of your quota usage).
Why does my SaaS Data Transfer Quota Usage increase when I start using Xray?
Unlike Artifactory, which primarily relies on artifact metadata and can re-use SHA-256 for optimization purposes, Xray must fetch a binary copy of the artifact and recursively unpack its layers to identify all underlying packages and dependencies. When an build/artifact is uploaded to Artifactory and Xray has marked the relevant build/repo for indexing based on your configurations, Xray will fetch a copy of that artifact for indexing and scanning. This action counts as another data transfer activity, and counts towards your quota total.
Notably, Xray will not re-use data from existing artifacts as well; 2 uploads of the same binaries in separate repos or under different names will be scanned and indexed as separate items.
If you have additional questions about your billing and Data Transfer Quota usage, please contact your Account Manager(s) or otherwise reach out to our support team via support@jfrog.com.
Additionally, you can refer to this document which explores the Artifactory side of data transfer quota further:
https://jfrog.com/help/r/artifactory-private-links-and-data-transfer-costs/artifactory-private-links-and-data-transfer-costs