Dataplex pricing
Dataplex pricing is based on pay-as-you-go usage. Dataplex currently charges for Dataplex standard and premium processing, which cover the data discovery and exploration workbench features respectively, as well as Dataplex shuffle storage for disk usage in the exploration workbench. Dataplex standard and premium processing are metered by Data Compute Unit (DCU). 1 DCU is comparable to 1 vCPU and 4GB of RAM.
Note: The data exploration workbench feature is currently free of charge in the preview phase. It will be billed as part of the Dataplex Premium tier when it is generally available.
Dataplex standard processing pricing
Dataplex standard tier covers the data discovery functionality that discovers metadata across Dataplex managed data. Below are the prices as per the region of your choice.
Dataplex premium processing pricing
Dataplex premium tier covers the usage of data exploration workbench in Dataplex. The compute charge is calculated based on the number of nodes specified for the Explore environments as well as their runtime. Below are the prices as per the region of your choice.
Dataplex shuffle storage pricing
Shuffle storage pricing covers any disk storage specified in the environments configured for the data exploration workbench.
Dataplex free tier
As part of the Google Cloud Free Tier, Dataplex offers some resources free of charge up to a specific limit. These free usage limits are available during and after the free trial period. If you go over these usage limits and are no longer in the free trial period, you will be charged according to the pricing as described in the sections above.
| Resource | Monthly free usage limits |
|---|---|
| Dataplex Processing | 100 DCU-hr |
Other usage
Data organization features in Dataplex (lake / zone / asset setup) and security policy application / propagation, are provided free of charge.
In addition, some Dataplex functionalities (such as scheduled data quality and data ingestion tasks) will trigger job execution via Dataproc Serverless, BigQuery, Dataflow and Cloud Scheduler. Those usages will be charged according to the Dataproc, BigQuery, Dataflow, and Cloud Scheduler pricing models respectively, and charges will show up under Dataproc, BigQuery, and Dataflow instead of Dataplex.
Data Catalog pricing
Data Catalog charges apply to:
Metadata storage: Business metadata as well as any on-premises metadata ingested by Data Catalog. Metadata storage is measured in gibibytes (GiB), where 1 GiB is 1,073,741,824 bytes.
Data Catalog API calls: Data Catalog read, write, and search API calls.
Metadata storage and API calls charges accrue daily. You can view unbilled usage on the Google Cloud console.
Metadata storage
Data Catalog metadata storage includes:
- Business metadata:
- Data Catalog tag templates and tags
- On-premises metadata ingested by Data Catalog.
Data Catalog metadata storage does not include:
- Technical metadata stored by other services; for example, dataset table and column names stored by another Google Cloud service.
Metadata storage charges for a tag are billed to the project where the tag template was created.
Data Catalog measures the average amount of the stored metadata during a short time interval. For billing, these measurements are combined into a one-month average, which is multiplied by the monthly rate. You are not charged for the first one MiB of metadata storage, as shown in the Metadata storage pricing table, below.
Metadata storage pricing
| Monthly average storage | Price per month |
|---|---|
| Up to 1 MiB | No charge |
| Over 1 MiB | $100 per GiB per month |
If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.
API calls
Data Catalog API calls include Data Catalog read, write, and search API calls, including API calls issued from the Data Catalog UI.
Charges are billed to different projects depending on specific API 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 measures the number of API calls, then multiplies the count by the rate. You are not charged for the first 1 million API calls in a month, as shown in the Data Catalog API calls pricing table, below.
Data Catalog API calls pricing
| API calls | Price |
|---|---|
| 1 million in a month | No charge |
| Over 1 million in a month | $10 per 100,000 API calls |
If you pay in a currency other than USD, the prices listed in your currency on Cloud Platform SKUs apply.
Data Catalog pricing examples
User A creates and applies small tags (1024 bytes each). For $100/month, the user can store 1GiB of metadata, which corresponds approximately to 1M tags. If the user applies one tag to each table, the user will be able to apply tags to 1M tables.
User B creates 1M tags of 1K bytes each on the 10th of the month, and deletes the tags on 20th. The cost is $100 (1K * 1M = 1 GiB) / one-third month = $33.00.
User C creates and applies large tags (10K bytes each). For $100/month, the user can store 1GiB of metadata, which corresponds approximately to 100K tags. If the user applies one tag to each table, the user will be able to apply tags to 100K tables.
User D creates 10 templates, consisting of ETL, Data Governance, Data Quality, and other templates, and applies large tags (10K bytes each) using each of the 10 templates. For $100/month, the user can store 1GiB of metadata, which corresponds approximately to 100K tags. If the user applies 10 tags to each table, the user will be able to apply tags to 10K tables.
What's next
- Read the product documentation: Dataplex, Data Catalog.
- Get started with Dataplex.
- Try the Pricing calculator.
- Learn about Dataplex solutions and use cases.