Collibra Data Lineage Cost and Collibra Technical Lineage Limits by Source
Collibra sells lineage as add-on lines on a governance platform. We read the lines off three public price lists and the limits off Collibra's own documentation, so you can check a quote before you sign it, or map the same warehouse here with a read-only role.
Read-only connection. DataTrail never moves or mutates your data.
Collibra Data Lineage is a cloud-only add-on to the Collibra Platform, and it is priced per source type on top of the platform fee. On the US GSA schedule a Custom Technical Lineage integration lists at $10,861.42 a year and each BI integration at $27,153.61, over a Standard platform of $166,346.53. The Standard package bundles one technical lineage and one BI integration. Tracing two databases, dbt and two BI tools comes to about $231,500 a year at list. DataTrail maps the same warehouse, dbt project and dashboards for $2,148 a year.
Data lineage in Collibra is counted per source type
The unit that drives a Collibra lineage quote is the integration. A database family is one technical lineage. An ETL or transformation tool is one ETL integration. Each BI tool is one BI integration. A package includes a fixed count of each, and anything past the count is an annual add-on line.
The only place Collibra has published those counts is the pricing document it filed with the UK Digital Marketplace for G-Cloud 14. Standard includes one technical lineage and one BI integration. Premier adds one ETL integration and a second BI tool. Only Ultimate removes the counting. A modern stack with a warehouse, an operational database, dbt and two BI tools already exceeds Standard on three counts.
The full platform, seat and module price list is on our Collibra pricing page. This page stays on the lineage lines.
Dollar lines from the US GSA schedule, whose only lineage line is named Custom Technical Lineage. The UK filing prices a technical lineage add-on at £8,195, about $10,869, so the two agree. The ETL line has no US listing we could find and is the UK price of £20,487 converted at 1.3263.
Collibra technical lineage prices on the public US list
Collibra publishes no prices on its website, but its resellers file an itemized US dollar price list under the federal GSA schedule, and anyone can read it. These are the lines a lineage buyer needs. Where two contract holders list the same item we quote the lower price.
| Line item | SKU | Per year | What it is |
|---|---|---|---|
| Custom Technical Lineage integration, single | CTLI | $10,861.42 | Listing text says custom integrations "allow table-level and indirect lineage". The second contract holder lists it at $10,943.43 |
| BI integration, single | BI-INT-C | $27,153.61 | One BI tool. Listing text says it will "enhance data lineage diagrams, data dictionaries, and business glossaries" |
| Metadata Integration, one system | CAMU-OP | $9,874.02 | Registers the source in the catalog. Lineage objects are stitched to these assets |
| Metadata Integration, unlimited systems (Cloud) | CAMU-UNLIMITED-C | $38,508.82 | Pays for itself at four systems |
| Data Lineage Accelerator, program | PS-PRO-DLA | $5,924.43 | A services package that reviews prerequisites and configuration. Not software |
| Data Intelligence Platform, Standard (Cloud) | DIC-STANDARD-BUNDLE-C | $166,346.53 | The platform the lineage lines sit on top of |
GSA prices are ceilings for federal buyers, and commercial quotes are negotiated. They are still the only itemized US dollar list Collibra's channel publishes. The AWS Marketplace listing, re-read the same day, sells the platform at $170,000 for 12 months, $340,000 for 24 and $510,000 for 36, with no lineage dimension of its own.
How many lineage integrations each Collibra package includes
From Collibra's G-Cloud 14 pricing document, filed 25 April 2024, in pounds, converted at 1 GBP = 1.3263 USD on 7 October 2026.
| Package or add-on | UK list, per year | In US dollars | Lineage entitlement |
|---|---|---|---|
| Standard | £96,541 | $128,042 | 1 technical lineage, 1 BI integration, 3 metadata connectors, 20 Creators |
| Premier | £151,846 | $201,393 | 1 technical lineage, 1 ETL integration, 2 BI integrations, unlimited metadata connectors |
| Ultimate | £232,239 | $308,019 | Unlimited technical lineage, ETL and BI integrations, 30 Creators |
| Extra technical lineage | £8,195 | $10,869 | Per add-on. Matches the US schedule line of $10,861.42 to within 0.1 percent |
| Extra ETL integration | £20,487 | $27,172 | Per add-on |
| Extra BI integration | £20,487 | $27,172 | Per add-on. The US schedule line is $27,153.61 |
The worked quote, line by line
Take a team that wants lineage across Snowflake and SQL Server, through dbt, into Power BI and Tableau. On the Standard package one database family and one BI tool are bundled. The second database is a technical lineage add-on at $10,861.42. The second BI tool is $27,153.61. dbt sits under ETL tools in Collibra's documentation, and an ETL integration is £20,487 on the UK filing, about $27,172.
That is $166,346.53 plus $65,187 of lineage add-ons, about $231,534 a year, before any extra Creator seats at $6,142.16 each. Premier would bundle the ETL integration and the second BI tool for $261,641.73, so it only wins once you also need its unlimited metadata connectors. Nothing gets cheaper for committing longer: the AWS listing is exactly linear across 12, 24 and 36 months.
Collibra lineage limits by source, in Collibra's own words
Collibra's scanner coverage is broad, and it documents the edges plainly. These are the ones that change what a buyer sees on the graph. The quoted sentence on each card is verbatim from the supported data sources page.
"DirectQuery and live connections are not supported."
Import-mode datasets only. If your reports query the warehouse live, they will not appear in the graph.
"Lineage is generated only for objects and statements recorded in the Snowflake ACCESS_HISTORY view."
That is the SQL-API ingestion mode. ACCESS_HISTORY is a Snowflake Enterprise Edition feature, so the warehouse edition matters.
"Complex structures (tables or columns) are not supported."
Nested and repeated fields, which most event and analytics schemas in BigQuery rely on, fall outside the scanner.
"Column-level lineage is not generated for tables that are created by SQL statements, unless you provide the SQL statements by creating a shared storage connection."
CREATE TABLE AS SELECT is how most warehouses are built. Without the extra connection you get table-level edges for those tables.
"For dbt Core, you have to prepare the data source files with all data objects that you want to process."
dbt Cloud is read through its service. dbt Core projects need files staged for the scanner, which is a pipeline someone has to own.
"Technical lineage cannot be created for views and procedures if the SQL definitions are encrypted in the database."
Common in vendor-supplied databases and older finance systems.
"Technical lineage via Edge can only access Redshift and Snowflake projects."
Matillion jobs targeting BigQuery, Databricks or Synapse are not covered.
"Tableau Prep Builder is not supported."
Live connections and extracts are both supported, so Tableau itself is well covered. Prep flows are the gap.
"SQL based input without stored procedures."
Logic that lives in stored procedures on these engines does not produce lineage.
Three structural facts that sit above the per-source list
It is cloud-only. The documentation opens with "Collibra Data Lineage is a cloud-only product". The scanners run through Edge inside your network, but the lineage service and the graph live in Collibra's cloud. A team that bought Collibra on-premise for data residency reasons does not get lineage there.
The harvester is gone. "The CLI lineage harvester reached its end of life on July 31, 2026. New versions are no longer released." Every scheduled harvester job has to move to Edge, and the BI harvester paths are marked deprecated. If your quote or statement of work still mentions the harvester, it was written from an old template.
Databricks lineage is relayed, not parsed. For Unity Catalog, Collibra reads "lineage information from the lineage system tables". So what you see in Collibra is what Databricks recorded, with the same gaps and the same retention. We cover those in Unity Catalog lineage and its limits.
None of this makes Collibra's lineage weak. It supports Informatica PowerCenter, Informatica Cloud Data Integration, SSIS, IBM DataStage, SAP HANA calculation views, Teradata BTEQ scripts, MicroStrategy and SSRS, which is a list very few products can match, and business lineage ties each column to a governed asset with an owner. If your estate is twenty years of ETL feeding a regulated reporting stack, that breadth is what the money buys.
Collibra lineage compared with a lineage-first tool
Collibra wins several of these rows outright. The table is here so you can see which rows your team actually needs.
| Collibra Data Lineage | DataTrail | |
|---|---|---|
| What you buy | An add-on to the Collibra Platform, viewed on asset pages in Data Catalog | A lineage and observability product on its own |
| Published US price | $10,861.42 per custom lineage integration and $27,153.61 per BI tool, on a platform from $166,346.53 (GSA schedule) | $708 to $5,748 a year on the self-serve plans |
| How lineage is collected | Scanners run through Edge against each licensed source type | Read-only role on the warehouse, parsed from query history and dbt artifacts |
| Column-level lineage | Yes, with the exception for tables created by SQL statements | Yes, from the queries that actually ran |
| Legacy ETL (PowerCenter, SSIS, DataStage) | Yes, all three are supported sources | No |
| SAP HANA, Oracle, Teradata, Db2 | Yes | No. Snowflake, BigQuery, Redshift, Databricks and Postgres |
| BI tools | Tableau, Power BI (import mode), Looker, MicroStrategy, SSRS | Tableau, Power BI, Looker |
| Business glossary and stewardship | Yes, and business lineage is tied to governed assets | No. A catalog generated from lineage, without stewardship workflows |
| Freshness and schema-change alerts | Sold separately as Data Quality and Observability | Included in every plan |
| Time to first graph | After platform setup, Edge install and source registration | The same day the role is granted |
DataTrail prices are Starter $59, Team $179 and Scale $479 a month billed yearly. Collibra figures are the public list lines cited above.
You already run the Collibra Platform, you have legacy ETL or SAP in the path, and auditors need each report column tied to a governed business term with a named owner.
The question is what breaks if this column changes, the estate is a cloud warehouse with dbt and dashboards, and the budget is five figures or less. See impact analysis.
Governance owns Collibra and the platform team needs live lineage with freshness and schema alerts today. A read-only connection does not touch the governance program.
How to see your lineage before the Collibra contract is signed
On Snowflake, BigQuery, Redshift, Databricks or Postgres. Metadata and query history only. No agent to install and nothing written back.
Query history and dbt artifacts are parsed into table and column lineage, including tables built with CREATE TABLE AS SELECT.
Tableau, Looker and Power BI content is linked to the columns it reads, so the graph ends where people look at numbers.
Pick a column and see every model and dashboard downstream. Freshness and schema alerts carry the same list.
Even if you go on to buy Collibra, an hour with a working graph tells you how many source types you really need to license, which is the number that sets the size of the lineage lines on the quote.
Collibra data lineage questions buyers ask
How much does Collibra data lineage cost?
Collibra data lineage is priced as add-on lines on top of a platform package. On the US GSA schedule, read on 7 October 2026, a single Custom Technical Lineage integration is $10,861.42 a year and a single BI integration is $27,153.61, on a Standard platform of $166,346.53. A team covering two databases, dbt and two BI tools lands near $231,500 a year at list.
Is data lineage included in Collibra?
Partly. The package entitlements Collibra filed with the UK Digital Marketplace give Standard one technical lineage and one BI integration, Premier one technical lineage, one ETL integration and two BI integrations, and Ultimate unlimited lineage, ETL and BI. Every source type beyond the bundled count is a separately priced add-on, so the answer depends on how many systems you need to trace.
What is technical lineage in Collibra?
Technical lineage in Collibra is the detailed graph of tables, columns and transformations collected from your external data sources, including temporary tables and the source code of each transformation. Business lineage is the summary view that only shows relations between assets already registered in Data Catalog. Both are produced by the same process, and business lineage is created automatically from technical lineage.
Does Collibra support column-level lineage?
Yes, Collibra scanners extract lineage at column level for supported sources. The documented exception is that column-level lineage is not generated for tables created by SQL statements unless you supply those statements through a shared storage connection. Custom Technical Lineage, the option for unsupported sources, is described on its price listing as allowing table-level and indirect lineage.
Does Collibra lineage work with Power BI and Tableau?
Yes for both, with limits. Collibra documents that Power BI DirectQuery and live connections are not supported, so only import-mode content is traced. Tableau live connections and extracts are both supported, but Tableau Prep Builder is not. Each BI tool is a separate BI integration, listed at $27,153.61 a year on the US GSA schedule.
Does Collibra support dbt and Databricks lineage?
Yes. dbt 1.4 and newer is a supported source, read from dbt Cloud directly or from files you prepare for dbt Core. Databricks Unity Catalog lineage is read from the Unity Catalog lineage system tables rather than parsed by Collibra, so it carries the same coverage and retention as Unity Catalog itself.
What happened to the Collibra lineage harvester?
The CLI lineage harvester reached its end of life on July 31, 2026, and Collibra states that new versions are no longer released. Technical lineage is now created through Edge, the Collibra agent that runs in your own environment. Teams still running the harvester on a schedule have a migration to plan, and BI harvester paths are marked deprecated in the documentation.
Can you use Collibra Data Lineage without Collibra Data Catalog?
No public price list shows a standalone lineage product. Collibra describes Data Lineage as a cloud-only product, the technical lineage tab appears on asset pages in Data Catalog, and viewing it requires a global role with both the Catalog and Technical Lineage permissions. In practice you buy the platform first and lineage on top.
What is a cheaper alternative to Collibra for data lineage?
If lineage and impact analysis are the goal and the estate is a cloud warehouse with dbt and a BI tool, a lineage-first product costs a small fraction of a governance platform. DataTrail reads Snowflake, BigQuery, Redshift, Databricks or Postgres with a read-only role and costs $2,148 a year on the Team plan. It does not replace Collibra for glossary, stewardship or legacy ETL.
Where these numbers came from
The dollar lines come from GSA Advantage, the US federal government's ordering system, searched for Collibra lineage items on 7 October 2026. Two schedule holders list most items and their prices differ by under one percent; we quote the lower. The platform amount of $170,000 for 12 months comes from Collibra's AWS Marketplace listing, re-read the same day. Package entitlements and pound prices come from the pricing document Collibra filed for G-Cloud 14 on 25 April 2024. The US schedule does not state what each platform package includes, so the bundled counts on this page rest on the UK filing for packages of the same name.
The limits are quoted from two Collibra documentation pages, "About Collibra Data Lineage" and "Supported data sources for technical lineage", both showing July 29, 2026 as their date when we read them. Two inferences are ours. The US schedule names its lineage line Custom Technical Lineage, and we use it as the price of an extra technical lineage because the UK filing prices that add-on at the same amount to within 0.1 percent. And we treat dbt as an ETL integration, which follows from where Collibra's documentation lists it. Ask your account team to confirm both in writing. List prices are a starting point for negotiation, and a large account will pay less.
Related pages
Every platform, seat, module and service line on the US schedule, next to the AWS and UK lists.
What Collibra does well, where teams look elsewhere, and how the options compare.
The field of lineage products, from governance suites to warehouse-native tools.
The other enterprise lineage scanner, priced from IBM's own catalog.
Both public list prices and how each one handles lineage.
How DataTrail builds column lineage from query history with a read-only role.
Get column-level lineage without a platform fee
Connect your warehouse with a read-only role and see what feeds what, down to the dashboard, with freshness and schema-change alerts included. Plans start at $59 a month billed yearly.