Discover platforms/Google Cloud

GOVERNATLAS / PRODUCT DOSSIER

Google Cloud Knowledge Catalog

Google Cloud currently names the offering Knowledge Catalog, formerly Dataplex. Its page describes metadata/context aggregation, semantic enrichment, asset discovery and governance; it explicitly marks some source integrations as Preview.

01 / CONTEXT & SCOPE

Understand the proposition.
Define the boundary.

The decision to make

Evaluate which context is collected and which permissions govern its use. A useful catalog can connect business meaning to assets, but permission-aware discovery and access to the underlying data remain separate questions. Keep the Dataplex naming transition in architecture and procurement records without creating a second product identity.

What this record does not establish

Firestore/Looker Preview labels and other current release boundaries require explicit review. No sub-second latency, hallucination elimination, complete coverage or semantic accuracy is independently established. Confirm source, IAM, billing and region scope in the proposed configuration.

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

A test worth running

In a proposed trial, ingest a synthetic asset and business definition, then search as an authorized analyst and a restricted service identity. Change the definition and source permission, inspect update timing and test retrieval through the intended agent/API path. Preserve provenance for generated context and a human correction.

GovernAtlas editorial proposal. We have not performed this test.

B

Evidence to bring back

  1. An asset/context/permission change record with generated versus reviewed metadata.
  2. A dated integration-status and identity/data-flow matrix for agent retrieval.

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.

01
vendor asserted

Google Cloud currently names the offering Knowledge Catalog, formerly Dataplex. Its page describes metadata/context aggregation, semantic enrichment, asset discovery and governance; it explicitly marks some source integrations as Preview.

Source, dates & preserved provenanceGoogle Cloud Knowledge Catalog — current official product scope ↗

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

Artifact SHA-256: 1023b2ec9de353d2760a56032e7a50d886ddd783b1f9f6c2e19f402c4c791da3

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

Source register

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.

01

Can you provide an asset/context/permission change record with generated versus reviewed metadata for the selected configuration?

02

A dated integration-status and identity/data-flow matrix for agent retrieval. Who owns and reviews this evidence?

03

Which current version, edition, integrations and operating responsibilities are included?

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 ↗