DataTrail
Blog / Pricing 6 min read

Dataplex Pricing for Lineage and Data Quality With a Worked Monthly Example

DataTrail

Lineage map
›Lineage mapped from query history. Read-only connection.
0

Read-only connection. DataTrail never moves or mutates your data.

Dataplex, now called Knowledge Catalog by Google, has no plans and no minimum. You pay $0.06 per DCU hour for standard processing, $0.089 per DCU hour for premium processing (used by data lineage, data quality scans and profiling), and about $2 per GiB per month for metadata storage. Catalog API calls, including lineage and search, are free. The bill is therefore a function of how many scans you run, not how many people use it.

That makes Dataplex cheap to switch on and awkward to forecast. This page lays out every price line we found on Google's pricing page, a worked example you can rescale with your own numbers, and the point where a flat-priced lineage tool becomes the simpler purchase.

Dataplex pricing at a glance

Price lineRate (USD)What it covers
Standard processing$0.06 per DCU hour ($0.054 with a 1-year BigQuery commitment, $0.048 with 3 years)Cloud Storage metadata harvesting
Premium processing$0.089 per DCU hour ($0.0801 with 1 year, $0.0712 with 3 years)Data lineage, data quality scans, data profiling
Metadata storage$0.002739726 per GiB hour, about $2 per GiB per monthCatalog entries, aspects, and anything you publish to the catalog
Catalog API callsFreeCreating and managing catalog and lineage resources, catalog search
Enrichment and data insights$3 per million input data tokens, $20 per million outputGemini-based metadata enrichment and insights

We read these on Google's Knowledge Catalog (formerly Dataplex) pricing page on 19 November 2026. Google kept the Dataplex name on the price lines after the rename, so a Dataplex invoice and a Knowledge Catalog invoice are the same thing. Data exploration is in preview and billing starts at general availability, so it is not priced yet.

How much does Dataplex cost per month?

There is no list price per month, only per unit. Google's own storage example is a useful anchor: $10 a month stores 5 GiB of metadata, roughly five million small aspects. Metadata storage is rarely the big line. Processing is, because lineage, quality scans and profiling all run on premium DCUs and scale with how often and how widely you run them.

A worked example you can rescale

These are assumptions, not measurements, so replace them with your own. A data team has a BigQuery project, publishes quality scan results to the catalog, and runs profiling and lineage jobs that consume 2,000 premium DCU hours in a month, with 5 GiB of metadata stored.

  • Premium processing: 2,000 hours x $0.089 = $178.
  • Metadata storage: 5 GiB x about $2 = about $10.
  • Catalog API calls: $0.
  • Total: about $188 a month, or about $2,256 a year.

Double the scan frequency and the processing line doubles. Halve it and it halves. With a 3-year BigQuery commitment the premium rate drops to $0.0712, which would take the same 2,000 hours to $142. The honest summary is that Dataplex is a few hundred dollars a month for a mid-size team, but the exact figure is something you learn from your own billing export. For comparison, DataTrail Team is $179 a month billed yearly, $2,148 a year, for up to five sources and unlimited team members, with no DCU meter.

What you get for that money, and what you do not

Dataplex is strong when your estate lives in Google Cloud. Lineage is captured for Google services, data quality and profiling run next to BigQuery, and access follows Google IAM. Three gaps send teams looking at an alternative:

  • Reach beyond Google. Other tools send OpenLineage events, which means integration work for a dbt project, a BI layer or a second warehouse.
  • Change workflow. The lineage API returns a graph. A check that tells a reviewer which dashboards break before a model change merges is something your engineers build.
  • Forecasting. A bill built from DCU hours is not a number you can put in a budget before the first month.

Our Dataplex alternative page compares the two feature by feature, and the BigQuery data observability page shows how DataTrail connects with a read-only role. Teams that want the wider catalog picture can also read how Microsoft Purview pricing meters scans in a similar way.

Who the pay as you go model suits

It suits a team that is almost all Google Cloud, runs scans on a schedule it controls, and has engineers to build workflow on the API. It suits agencies and analytics teams with a small BigQuery footprint, for example a marketing team that loads campaign and backlink reports from a vendor such as offsiteseo.com into a few tables and only needs basic cataloging. It is a worse fit when several tools feed the warehouse and you need one lineage graph with a fixed price.

Frequently asked questions

How much does Dataplex cost?

Dataplex, now Knowledge Catalog, is pay as you go. Standard processing is $0.06 per DCU hour, premium processing for lineage, data quality and profiling is $0.089 per DCU hour, and metadata storage is about $2 per GiB per month. Catalog API calls are free, so the total depends on how many scans you run.

Is Dataplex lineage free?

Calls to the lineage API are free, but Google lists data lineage under premium processing, which is billed at $0.089 per DCU hour, and the metadata you store is billed per GiB. Lineage is not a free feature, although small usage costs little.

Is Dataplex the same as Knowledge Catalog?

Yes. Google renamed Dataplex Universal Catalog to Knowledge Catalog and kept the Dataplex names on the pricing SKUs. Older articles, invoices and search results that say Dataplex describe the same product.

What is a cheaper alternative to Dataplex for lineage?

For column-level lineage and change impact across BigQuery, dbt and BI tools, DataTrail costs $59, $179 or $479 a month billed yearly with no DCU meter. It does not run Google native quality scans, so teams that need those often keep Dataplex alongside it.

Want a number before you commit to a metered bill? Compare plans on the pricing page and connect BigQuery read-only in minutes.

See how your data flows, end to end

Connect your warehouse read-only and map lineage, freshness, and downstream impact before a change breaks a dashboard. Transparent pricing, and a demo map without a card.