Data Catalog is deprecated and will be discontinued on January 30, 2026. For steps to transition your Data Catalog users, workloads, and content to Dataplex Universal Catalog, see Transition from Data Catalog to Dataplex Universal Catalog.
Stay organized with collections
Save and categorize content based on your preferences.
This page provides examples of Data Catalog pricing.
Data Catalog pricing considerations
Metadata storage charges for a tag are billed to the project where the tag
template was created.
API charges are billed to different projects depending on specific calls:
Read methods (get, lookup, list, and search) are billed to the
project of the account that authorized the API calls.
Write methods (create, update, delete, and rename) for all stored
entities, except tags, are billed to the project of the mutated entity.
Write methods for tags are billed to the project of the tag template used
to create the tag.
Data Catalog pricing examples
Small tags
User A creates and applies small tags (1024 bytes each).
For $10 per month, the user can store 5GiB of metadata, which corresponds
approximately to 5M tags. Assuming one tag per table, it amounts to a total of
5M tagged tables.
User B creates 5M tags of 1K bytes each on the 10th of the month,
and deletes the tags on 20th. The cost is $3.33, calculated as 5GiB of data
divided by one-third month:
5GiB * $2 // 5M tags using 1K bytes memory each amounts to 5GiB of metadata
* 1/3 // The tags were stored for 10 days (between the 10th and 20th day of the month), so the cost is divided by one-third.
---
= $3.33
Large tags
User C creates and applies large tags (10K bytes each).
For $10 per month, the user can store 5GiB of metadata, which corresponds to
approximately 500K tags. Assuming one tag per table, it amounts to a total of
500K tagged tables.
User D creates 10 templates (for example ETL, Data Governance, Data Quality),
and applies large tags (10K bytes each) using each of the 10 templates.
For $10 per month, the user can store 5GiB of metadata, which corresponds
approximately to 500K tags. Assuming 10 tags per table, it amounts to a total of
50K tagged tables.
Estimate data lineage pricing
Data lineage pricing example
User E enables data lineage to track lineage for
BigQuery in their project. The project is in the us-central1
location. During 1 month, data lineage consumes 100 DCU-hours
of Dataplex Universal Catalog Premium processing, and generates 1GiB
of data lineage metadata. The cost is:
100 * $0.089 // 100 DCU-hours of Dataplex Universal Catalog Premium processing billed at $0.089 per DCU-hr
+ (1GiB - 1MiB) * $2 // cost of storing 1GiB data lineage metadata excluding 1MiB of free storage per month
---
= $10.9
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-03 UTC."],[[["\u003cp\u003eThis page provides details on Data Catalog pricing, including metadata storage and API call charges, along with specific cost examples.\u003c/p\u003e\n"],["\u003cp\u003eMetadata storage costs for tags are billed to the project where the tag template was created, and read method API calls are billed to the project of the account that authorized the call.\u003c/p\u003e\n"],["\u003cp\u003eThe cost of tag storage is calculated based on the size and quantity of tags, for example, $10 per month allows for storing 5GiB of metadata, which translates to approximately 5 million small tags (1024 bytes each) or 500,000 large tags (10K bytes each).\u003c/p\u003e\n"],["\u003cp\u003eData lineage pricing involves Dataplex Premium processing charges (billed per DCU-hour) and metadata storage costs (excluding 1MiB of free monthly storage).\u003c/p\u003e\n"],["\u003cp\u003eWrite method API calls for all stored entities except tags, are billed to the project of the mutated entity, whereas write method API calls for tags are billed to the project of the tag template used to create the tag.\u003c/p\u003e\n"]]],[],null,["# Data Catalog pricing examples\n\nThis page provides examples of Data Catalog pricing.\n\n### Data Catalog pricing considerations\n\nMetadata storage charges for a tag are billed to the project where the tag\ntemplate was created.\n\nAPI charges are billed to different projects depending on specific calls:\n\n- Read methods (`get`, `lookup`, `list`, and `search`) are billed to the project of the account that authorized the API calls.\n- Write methods (`create`, `update`, `delete`, and `rename`) for all stored entities, except tags, are billed to the project of the mutated entity.\n- Write methods for tags are billed to the project of the tag template used to create the tag.\n\n### Data Catalog pricing examples\n\n#### Small tags\n\n- User A creates and applies small tags (1024 bytes each). For $10 per month, the user can store 5GiB of metadata, which corresponds approximately to 5M tags. Assuming one tag per table, it amounts to a total of 5M tagged tables.\n- User B creates 5M tags of 1K bytes each on the 10th of the month,\n and deletes the tags on 20th. The cost is $3.33, calculated as 5GiB of data\n divided by one-third month:\n\n 5GiB * $2 // 5M tags using 1K bytes memory each amounts to 5GiB of metadata\n * 1/3 // The tags were stored for 10 days (between the 10th and 20th day of the month), so the cost is divided by one-third.\n ---\n = $3.33\n\n#### Large tags\n\n- User C creates and applies large tags (10K bytes each).\n For $10 per month, the user can store 5GiB of metadata, which corresponds to\n approximately 500K tags. Assuming one tag per table, it amounts to a total of\n 500K tagged tables.\n\n- User D creates 10 templates (for example ETL, Data Governance, Data Quality),\n and applies large tags (10K bytes each) using each of the 10 templates.\n For $10 per month, the user can store 5GiB of metadata, which corresponds\n approximately to 500K tags. Assuming 10 tags per table, it amounts to a total of\n 50K tagged tables.\n\nEstimate data lineage pricing\n-----------------------------\n\n| **Important:** Only certain executions generate lineage, which can differ between supported systems. For information on supported systems, see [About data lineage](/data-catalog/docs/concepts/about-data-lineage#lineage-supported-systems).\n\n### Data lineage pricing example\n\nUser E enables data lineage to track lineage for\nBigQuery in their project. The project is in the `us-central1`\nlocation. During 1 month, data lineage consumes 100 DCU-hours\nof Dataplex Universal Catalog Premium processing, and generates 1GiB\nof data lineage metadata. The cost is: \n\n 100 * $0.089 // 100 DCU-hours of Dataplex Universal Catalog Premium processing billed at $0.089 per DCU-hr\n + (1GiB - 1MiB) * $2 // cost of storing 1GiB data lineage metadata excluding 1MiB of free storage per month\n ---\n = $10.9"]]
