DataHub OSS

Open-source data catalog and metadata platform for discovery, lineage and governance.

10 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

DataHub v1.9.1 OpenJDK security rebuild

DataHub v1.9.1 rebuilds service images on OpenJDK 25.0.5.1 for CVE-2026-114938 and removes cached Wolfi layers retaining the older JDK.

Scope: DataHub OSS GMS, frontend, MAE/MCE consumer, upgrade and actions images; fixes were also cherry-picked to the v1.9.0 hotfix branch.

Affected image and CPU/JDK behavior determine exposure.

Action: Deploy fixed images for every DataHub service and restart them while retaining the v1.9.0 upgrade prerequisites.

Primary source · Reviewed 2026-11-19

What lands where

  1. Supplied by

    Vendor or project

    Official Helm deployment on EKS, AKS or GKE

  2. Operated by

    Your team

    Customer manages Kubernetes, stateful dependencies, networking, secrets, backups, scaling, ingestion, and upgrades, including search-backend compatibility and per-version breaking-change actions.

Deployment boundaries by provider
  • AWS: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    DataHub on Amazon EKS ↗ · Source checked 2026-11-14

  • Azure: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    DataHub on Azure Kubernetes Service ↗ · Source checked 2026-11-14

  • Google Cloud: Customer cloud account · Customer-operated

    Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.

    DataHub on Google Kubernetes Engine ↗ · Source checked 2026-11-14

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodOfficial Helm deployment on EKS, AKS or GKE
InfrastructureServers / containers
DataHub uses persistent application services and stateful database, search and event-stream components. Provider-managed dependencies do not remove application operations. DataHub v1.9.0 supports Elasticsearch 8.x or OpenSearch 2.x/3.x; GMS will not start with Elasticsearch 7.x or OpenSearch compatibility mode reporting 7.10.2.
Licensing modelOpen Source / Open Core
DataHub OSS is Apache-2.0 licensed. DataHub Cloud and associated enterprise services use separate commercial terms.
LicenseApache License 2.0.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

6 of 12 fields researched (50%) · 6 documented · 0 unresolved. Evidence coverage is not a feature score.

Single sign-on
AvailableEvidence and scope for Single sign-on

The self-managed React application supports OIDC identity providers such as Okta, Google and Keycloak through its authentication configuration. This is separate from DataHub Cloud login setup.

DataHub self-managed frontend OIDC configuration · Source ↗ · Reviewed 2026-11-14

Documented · Editor reviewed.

Security controls
DocumentedEvidence and scope for Security controls

v1.9.1 rebuilds GMS, frontend, MAE/MCE consumer, upgrade and actions images on OpenJDK 25.0.5.1 to address CVE-2026-114938, and removes cached Wolfi layers that could retain the prior JDK. Upgrade every service image and restart.

DataHub OSS service images from the v1.9.1 release and its v1.9.0 hotfix branch · Source ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The official Helm repository provides separate DataHub and prerequisite charts, including external database, search and Kafka dependencies. The deployment guide includes example credentials that must be replaced. Pin compatible chart and application versions, and review whether to use managed or separately operated dependencies.

Official Kubernetes Helm deployment · Source ↗ · Deployment artifact ↗ (Select compatible chart and application releases) · Reviewed 2026-11-20

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The Kubernetes guide requires more than 7 GB RAM for a local Minikube deployment including dependencies. This is not a production minimum: application services, database, Kafka, search and any graph service require separate resource and availability sizing.

Local all-component deployment floor; production/HA capacity excluded · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

The reviewed upstream core is Apache-2.0 licensed. Optional services, bundled dependencies, commercial distributions and support can have separate terms. This records the source licence, not an infrastructure or operating-cost estimate.

Upstream core licence; commercial features, support and hosting priced separately · Source ↗ · Reviewed 2026-11-20

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

DataHub v1.9.1 was published November 19, 2026. It rebuilds service images on OpenJDK 25.0.5.1 for CVE-2026-114938 and fixes OpenSearch 2.x semantic search with multiple OR groups. Retain the v1.9.0 Elasticsearch/OpenSearch, CLI, Helm and breaking-change requirements.

Upstream DataHub OSS service images and hotfix branch; commercial editions and provider packages may differ · Source ↗ · Prior reviewed release context ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Show all fields (6 not researched)
Marketplace delivery
Not researched Supply a public source.
Cloud commitment eligibility
Not researched Supply a public source.
SCIM provisioning
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Air-gapped operation
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

This entry covers DataHub OSS, not DataHub Cloud. Production deployments require careful operation of the metadata database, search index, event streaming and upgrade jobs; managed provider services can replace some in-cluster dependencies. DataHub v1.9.0 removes Elasticsearch 7.x support and requires Elasticsearch 8.x or OpenSearch 2.x/3.x. Metrics are enabled by default; set METRICS_ENABLED=false to disable them. The release requires CLI/Python SDK 1.7.0.19 and Helm chart 1.1.10, and operators should review all documented breaking changes before rollout. DataHub v1.9.1 rebuilds service images on OpenJDK 25.0.5.1 for CVE-2026-114938 and removes cached Wolfi layers that retained the earlier JDK. It also fixes OpenSearch 2.x semantic search with multiple OR groups. Preserve the v1.9.0 breaking-change, search-backend, CLI and Helm upgrade requirements when applying the patch.

Community & maintenance

The project community profiles identify Zynga running a customized DataHub fork and Farm Credit Canada hardening a Kubernetes deployment. Public contributor history shows sustained work by multiple participants, and release 1.9.0 on November 16, 2026 documents active maintenance, security updates, and significant upgrade requirements. These profiles establish project use without treating DataHub Cloud customers as proof of OSS deployment.

Category fit

Data & analytics
Provides a metadata catalog, lineage graph, discovery and governance layer for connected data systems.

Compare within Data & analytics

  • ActivityInfo (Self-Managed Server)Commercial self-managed data collection, relational records and program-reporting platform.
    • Azure
    Customer-operated · Commercial Only
  • Airbyte Self-ManagedSelf-managed data movement and ELT platform with customer-operated connectors and job execution.
    • AWS
    • Azure
    • Google Cloud
    • DigitalOcean
    Customer-operated · Source Available
  • Apache Doris Self-HostedApache-licensed analytical database with upstream AWS EKS/Alibaba ACK/ACS guides and a separately packaged cloudimg Azure VM path.
    • AWS
    • Azure
    • Alibaba Cloud
    Customer-operated · Open Source / Open Core
  • Apache DruidColumn-oriented analytics database for interactive queries over streaming and historical event data.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • Apache SupersetBusiness intelligence and data exploration platform for SQL analysis, visualizations and shared dashboards.
    • AWS
    Customer-operated · Open Source / Open Core
  • AVEVA PI System (BYOL)Commercial industrial data collection, historian and visualization system with an AWS architecture.
    • AWS
    Customer-operated · Commercial Only
  • Azure Trusted Research EnvironmentOpen-source reference platform for isolated research workspaces and controlled data movement.
    • Azure
    Customer-operated · Open Source / Open Core
  • Cloud Carbon FootprintOpen-source cloud-usage, energy and carbon-estimation application.
    • Google Cloud
    Customer-operated · Open Source / Open Core

Showing 8 of 43 other listings in Data & analytics. These products address related workflows; read their category-fit notes before comparing scope. See all of Data & analytics →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • DataHub on Amazon EKS ↗ · AWS

      Vendor / upstream documentation · Reviewed 2026-11-14. Vendor support commitment: not assessed; confirm the selected release and contract.

      The official guide deploys DataHub to a customer EKS cluster and describes optional AWS managed services for stateful dependencies.

    • DataHub on Azure Kubernetes Service ↗ · Azure

      Vendor / upstream documentation · Reviewed 2026-11-14. Vendor support commitment: not assessed; confirm the selected release and contract.

      The official guide deploys DataHub to a customer AKS cluster and documents the required infrastructure and Helm installation.

    • DataHub on Google Kubernetes Engine ↗ · Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-14. Vendor support commitment: not assessed; confirm the selected release and contract.

      The official guide deploys DataHub to a customer GKE cluster with Helm and provider-managed dependency options.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked
  5. Community & maintenance evidenceChecked

Suggest a correction · Back to directory