Collibra’s Data Quality and Observability product is licensed in two forms. The cloud product is metered by a jobs allowance, and the on-prem software is licensed under a Data Quality Addendum. Collibra’s agreements page says the Collibra DQ Addendum “supplements the legacy Master Cloud Agreement for the purchase of Collibra Data Quality & Observability on-prem software”.[4] The documentation center lists publications for Data Quality and Observability, for Data Quality and Observability Classic (self-hosted) and for Collibra Platform Self-Hosted, which indicates that customer-operated deployments exist alongside the cloud service.[6] Catalog proof: The DQ Addendum supplements the legacy Master Cloud Agreement for on-prem Data Quality.
Editions
| Offering | Licence form | Catalog SKU |
|---|---|---|
| Data Quality and Observability (cloud) | Package jobs allowance plus bundles[1] | Collibra Data Quality & Observability (cloud), Collibra data quality job bundle |
| Data Quality and Observability (on-prem) | Licence under the DQ Addendum within a Scope of Use[2] | Collibra Data Quality & Observability (on-prem) |
| Collibra Platform Self-Hosted (CPSH) | Named by Collibra as outside the Collibra Units model[7] | Collibra Platform Self-Hosted (CPSH) |
| Collibra Platform for Government | Named by Collibra as outside the Collibra Units model;[7] U.S. public sector purchases go through Collibra Public Sector LLC[4] | Collibra Platform for Government |
The jobs documentation uses a “Premier license” with 500 jobs as its example, but the retrieved pages do not publish package contents otherwise.[1]
Metrics
Data quality job. The Data Quality Jobs page, in the Users and subscriptions section of Settings, gives “an overview of the entitled data quality jobs and current usage”. The total allowance combines the “Package allowance: The number of data quality jobs included in your package” and the “Additional allowance: Any extra data quality job bundles that you have purchased”.[1] The documentation points to the Monitoring Overview page and its ”+ Data Quality Job” button as where jobs are created.[1] Catalog proof: Data quality jobs allowance combines the package allowance and purchased bundles.
Scope of Use. For on-prem software the DQ Addendum defines Scope of Use as “the authorized scope of use for the On-Prem Software specified in the applicable Order, which may include any user, copy, instance, CPU, computer, field of use or other restrictions”.[2] The Addendum does not itself publish a metric; the Order does. Catalog proof: Scope of Use may include user, copy, instance, CPU, computer or field of use.
Counting / floors
Jobs buffer. The number of allocated data quality jobs “has a 20% buffer to help you manage consumption after exceeding the entitled amount”. When the total goes over 120% “for more than 10 consecutive weeks”, the customer can no longer manually run, schedule or trigger from external systems any new data quality jobs, and a message appears when creating a job.[1] The page’s worked example: a Premier licence of 500 jobs plus 50 purchased gives a 550-job allowance; 450 existing jobs plus 175 new jobs is 625, above the allowance but below the 660 critical limit (120% of 550), so the customer receives a warning banner and has time to buy more or reduce jobs.[1] The job usage history graph covers the last 12 months, with an orange line at 100% and a red line at 120%.[1] Catalog proof: Data quality jobs have a 20% buffer; beyond 120% for 10 weeks stops new jobs.
Edge sites. “Deleting an Edge site does not delete jobs associated with connections on the deleted Edge site. Though orphaned, those jobs continue to count against the job quota and are not visible in the Monitoring Overview.”[1] A job inventory that relies on the Monitoring Overview can therefore understate consumption. Catalog proof: Jobs orphaned by deleting an Edge site still count against the job quota.
On-prem verification. The DQ Addendum repeats the MCA verification right for on-prem software: on written request, no more than once annually except for repeated violations, the customer certifies compliance including the Scope of Use, and Collibra may use Usage Monitoring through the software. It adds that “Usage Monitoring shall be at the Customer account level and shall not include any personal data”. If the Scope of Use is exceeded the customer pays for past and ongoing excess use at Order rates.[2] Catalog proof: On-prem Data Quality Usage Monitoring is at account level and excludes personal data. The restrictions mirror the MCA: no third-party access, no use on behalf of third parties, no circumventing usage limits including the number of authorized Users through APIs, and no publishing of benchmarks.[2]
Virtualization & partitioning
The on-prem DQ licence is the one place where Collibra’s contract lists machine-type metrics. The Scope of Use can include a user, copy, instance, CPU, or computer limit, set in the Order.[2] The licence is “to install, copy and use the On-Prem Software on systems under Customer’s control only for its internal business purposes in accordance with the Documentation and the Scope of Use”.[2] The retrieved documents give no core factor, sub-capacity or hard-partitioning rule of the kind described in virtualization and partitioning; a licence manager should read the Order for the metric and counting method. Catalog proof: On-prem Data Quality is licensed for systems under Customer control within the Scope of Use.
Cloud / BYOL
Renewal and exit. Unlike the MCA, which auto-renews, each Subscription Term for on-prem Data Quality “will renew only upon mutual written agreement of the parties”.[2][5] On termination the licence ceases, and the customer must immediately stop using and delete (or, on request, return) all copies of the software.[2] Catalog proof: On-prem Data Quality terms renew only by mutual written agreement; On termination the customer must stop using and delete on-prem Data Quality copies.
Support and SLA. The SLA does not apply to on-prem software. The MCA’s limited warranty and Collibra’s indemnification do not apply to any unsupported release of the on-prem software. Support follows the Support Policy at the level in the Order, and Collibra has no support obligation for incidents arising from standalone open source software, beta software, software for testing or demonstration, temporary modules or software for which Collibra receives no licence fee.[2] The MCA also says the SLA does not apply to Software.[5] Catalog proof: Warranties and indemnity do not apply to unsupported on-prem releases.
Platform self-hosted and CU. Collibra Platform Self-Hosted and Collibra Platform for Government are outside the Collibra Units model, which applies to Cloud environments only.[7] See Collibra Units and AI features. For downloadable Software in general, the MCA grants a licence to install and use it on systems under the customer’s control, within Usage Limits.[5]
Programs
- Collibra data quality job bundle. Extra bundles increase the jobs allowance; the page says customers can “purchase additional job bundles to increase your allowance”.[1]
- U.S. public sector agreements. U.S. public sector customers buy through Collibra Public Sector LLC. The Master Cloud Agreement (FedRAMP/GSA) is “the underlying agreement that applies to all Collibra cloud service and offerings” they buy, and the On-Prem End User License Agreement (GSA) applies to software.[4] Catalog proof: U.S. public sector customers buy under separate Master Cloud Agreement and EULA through Collibra Public Sector LLC.
- GSA EULA restrictions. The GSA On-Prem EULA grants a non-transferable, non-sublicensable, non-exclusive licence during the Subscription Term to install, copy and use the Software on systems under the customer’s control within the Scope of Use. It adds that the customer must not deploy, use or provide access to the Software for the benefit of the operations of another group, entity, department or agency in a controlling, parallel or subordinate position, or that takes over operations in a government or academic reorganization.[3] Catalog proof: GSA on-prem EULA bars use for controlling, parallel or subordinate entities and Reorganization successors. Collibra may request a written compliance certification under the GSA EULA no more than once annually except for repeated violations, and excess use is paid for at Order rates.[3] Catalog proof: GSA on-prem EULA lets Collibra request a written certification, at most once annually.
- Premium Support. Premium Support is an annual subscription, with 24x5 support and 24x7 for Severity 1 Incidents.[8]
Out of scope
This article does not cover the text of the Master Cloud Agreement (FedRAMP/GSA), the data quality product’s technical limits such as Spark resources and concurrent job limits, or Collibra’s pricing. The retrieved pages do not say how many jobs a package includes, other than the documentation’s example, and they do not say how a “job” relates to an individual dataset or schedule.