GOVERNATLAS / PRODUCT DOSSIER

Actian Data Intelligence Platform

Actian’s documentation describes catalog, glossary, lineage, stewardship and enterprise marketplace capabilities, with Studio for metadata management and Explorer for discovery. Its documentation also lists access-request and data-product workflows; supported connectors and permissions need detailed review.

Explore the product ↗Add to comparison ↗

01 / CONTEXT & SCOPE

Understand the proposition.
Define the boundary.

The decision to make

Distinguish the steward’s ability to change metadata from the consumer’s ability to access underlying data. Studio and Explorer support different users, and a marketplace transaction needs a clear operating boundary. Choose a product whose owner, documentation and actual source grant can all be inspected.

What this record does not establish

Current Actian documentation is used rather than treating older Zeenea naming as a second product. No universal connectivity, automatic data quality or marketplace entitlement is independently established. Confirm deployment, connector support, metadata access and native enforcement responsibilities.

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

In a proposed trial, curate an asset in Studio, discover it in Explorer and request the intended access. Reject a consumer suggestion, then approve a revised description with provenance. Check whether the final source permission changes as expected and export the history, including an unavailable connector.

GovernAtlas editorial proposal. We have not performed this test.

Evidence to bring back

A steward/discovery/request/source-permission chain with rejected suggestion history.
A connector and user-role matrix plus inspectable metadata/evidence export.

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

Source, dates & preserved provenance

Actian Data Intelligence Platform — current official product scope ↗

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

Artifact SHA-256: e8132a3de48f5b133c89488474c66cfe871b7e9e26f3671d8c4c8f6d9b6b0597

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

Source register

Actian Data Intelligence Platform — current official product scope ↗vendor owned · captured 2026-10-15

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.

Can you provide a steward/discovery/request/source-permission chain with rejected suggestion history for the selected configuration?

A connector and user-role matrix plus inspectable metadata/evidence export. Who owns and reviews this evidence?

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 ↗