GOVERNATLAS / PRODUCT DOSSIER

DataHub

DataHub describes a platform for data discovery, governance, observability and lineage. Its current site distinguishes the Core and Cloud offerings; feature equivalence is not established.

Explore the product ↗Add to comparison ↗

01 / CONTEXT & SCOPE

Understand the proposition.
Define the boundary.

The decision to make

Decide whether you are evaluating Core, Cloud or a specific combination of services. A shared product family does not remove differences in operating responsibility, access controls, ingestion or support. Match your desired metadata workflow to the actual offering being tested.

What this record does not establish

The captured site distinguishes Core and Cloud. The profile does not establish feature parity, hosting responsibilities, licensing terms or commercial support across those offerings.

1 current source · 1 published assertion
Source coverage is a research boundary, not a quality score.

02 / YOUR EVALUATION

Turn interest into a useful trial.

Open the evaluation playbook ↗

A test worth running

Use the proposed offering to ingest a synthetic source, locate an asset and inspect its ownership and lineage. Introduce a schema change and a failed ingestion. Ask the operator to demonstrate recovery and export the relationships needed for downstream use.

GovernAtlas editorial proposal. We have not performed this test.

Evidence to bring back

Tie every evaluated capability to the named offering, release and deployment used in the trial.
Identify who notices, owns and resolves stale metadata after an ingestion failure.

THE OPERATING DETAIL

Test the context at the moment someone needs it.

GovernAtlas analysis: practical review considerations, not findings from a product test.

Follow one real decision path

Use a fictional revenue metric with a documented owner, definition and upstream dependency. Ask an analyst and an application team to locate the same meaning independently. Introduce a conflicting definition in a second domain. The trial should expose how the conflict is surfaced and resolved, rather than rewarding the number of metadata fields populated.

Make change visible

Change an upstream column in a disposable fixture and inspect the downstream impact record. Record when the change became visible, which relationships were represented and which were absent. Request a demonstration of ownership and freshness handling for the connectors you actually need. A broad connector list does not demonstrate completeness for a specific integration.

Confirm the edition and access model

Keep DataHub Core and Cloud requirements separate. Ask for the deployed edition, entitlement, operational responsibilities and export path relevant to the trial. If an agent consumes metadata through an API or MCP connection, use a restricted test identity and inspect whether the returned context respects its permissions. Treat that result as evidence for the tested configuration only.

03 / DOCUMENTED EVIDENCE

Read the claim. Inspect the basis.

Each statement retains its classification and preserved source. A vendor assertion is not an independent test result.

vendor asserted

DataHub describes a platform for data discovery, governance, observability and lineage. Its current site distinguishes the Core and Cloud offerings; feature equivalence is not established. Scope: vendor documentation only; edition and availability boundaries require confirmation.

Source, dates & preserved provenance

DataHub — official product or documentation page ↗

Authority: vendor owned
Observed 2026-10-14 · Reviewed 2026-10-15 · current until 2026-11-13

Artifact SHA-256: 4816d78fb1365e16f17bcfe544e3b615d1623e41ee4525e71d392e19a454bc66

The hash identifies the preserved capture. The live source may have changed.

Source register

DataHub — official product or documentation page ↗vendor owned · captured 2026-10-14

Brand asset provenance

Organization identity asset from its official website; inclusion does not imply endorsement.

Official website ↗ · Original asset ↗

04 / BEFORE YOU COMMIT

Better questions.
A clearer decision.

Resolve these with the provider and your own evaluation team.

What differs between DataHub Core and Cloud, including policy and operational responsibilities?

What deployment, retention and access-control evidence supports the intended use?

What underlying assurance documents are available, and which claims remain unverified?

Regulatory applicability requires a separate, current determination. Inclusion is not certification.

KEEP THE RECORD USEFUL

A dossier should stand up to scrutiny.

Have a source that changes this picture? Submit it for editorial review.

Raise an evidence issue ↗