Concept | Surfacing Dataiku items in the Govern node#

One out-of-the-box benefit of the Govern node is its ability to automatically synchronize and centralize items from connected Dataiku nodes. In other words, the Govern node enables you to track all your projects, models, bundles, and GenAI items across various Dataiku nodes in one place at any moment.

Governable items#

The Governable items (Governable items icon.) page surfaces all Dataiku items from connected nodes that isn’t yet governed. You can think of it as an inbox of Dataiku items eligible for governance.

On this page, you can:

  1. View governable Dataiku items by type (project, model, bundle, etc.).

  2. Hide items you don’t want to govern using the eye (View impact icon.) icon at the end of an item’s row.

  3. Design and save filters (Add filter icon.) to sift through ungoverned items.

  4. Review item metadata in the Source objects (Source objects icon.) tab of the right panel.

  5. For some types of items, the right panel also includes tabs for Deployments (Deployments icon.) and/or Model metrics (Model metrics icon.).

  6. Most importantly, add a governance layer to a Dataiku item. In other words, govern (Gavel icon.) the item.

Dataiku screenshot of the Governable items page.

Types of governable items#

If you’re familiar with the Dataiku platform, you’ll already know the categories of Dataiku items found on the Governable items page. Those new to Dataiku should review the table below:

Item type

Description

Projects

A Dataiku project is a container for all work on a specific activity. It organizes objects like datasets, processing logic, notebooks, analyses, models, agents, dashboards, etc. around one activity.

Bundles

A bundle is a versioned snapshot of a project’s configuration that you can deploy to a production environment. A bundle is a child item of a parent Dataiku project.

ML saved models

An ML saved model is the overall model entity represented by a diamond in the Flow. A model version is a child item of a parent Dataiku project.

ML saved model versions

An ML saved model version is the model package (or model artifact) for classic ML tasks like prediction, classification, forecasting, etc. A saved model version is a child item of a parent model version.

LLM & Agent items

Advanced license users may encounter GenAI items that respect a similar information hierarchy: LLMs and agents being child items of a parent Dataiku project; and LLM or agent versions belonging to a parent LLM or agent object. Learn more in the reference documentation on Generative AI and LLM Mesh and Agentic AI.

Item registries#

At times, you may want to view all your organization’s models, bundles, or GenAI items — whether they’re governed or not. Three different registries serve this need.

Model registry#

The Model registry (Model registry icon.) provides a complete list of models from your connected Dataiku nodes—regardless of governance status—organized by project.

  1. Nested within each project and saved model, you’ll find all saved model versions, including results for the focus metric of your choice.

  2. Saved model versions have additional views in the right Details panel, including for Model Metrics (Model metrics icon.) and Deployments (Deployments icon.).

  3. You can filter the page to include only deployed model versions.

Dataiku screenshot of the Details panel of a model version in the Model registry page.

Note

Most model metrics show the initial metric values drawn from the Design node or Automation node when building the model version. However, drift metrics come from the model evaluations stored in a model evaluation store (MES).

The MES must exist in the same project as the saved model of the model version being evaluated. You can configure the MES to opt out of the Govern sync if needed. Otherwise, metrics update anytime an evaluation runs.

GenAI registry#

Important

To take full advantage of governance of GenAI items, you’ll need an advanced license.

For a variety of reasons, including their associated costs, governance is a key obstacle to enterprise-wide deployment of Generative AI applications. Accordingly, governance of GenAI use cases is a motivating factor behind Dataiku’s LLM Mesh.

The Govern node plays a central role in this mission:

  1. All pages identify Dataiku items that include LLM usage in recipes or Answers webapps with a pink LLM tag.

  2. All pages include the ability to filter for items using LLMs.

  3. Most specifically, the Govern node includes a GenAI registry (AI icon with stars.) to manage the governance of GenAI items such as fine-tuned LLMs, agents, and augmented LLMs. It functions just like the Model and Bundle registry pages.

Dataiku screenshot of the GenAI registry.

Bundle registry#

The Bundle registry (Bundle icon.) provides a complete list of all bundles from connected Dataiku nodes, regardless of governance status.

  1. Nested within each project, you’ll find all bundles, including whether it’s deployed.

  2. For a deployed bundle, the Deployments tab of the right Details panel reports information such as the deployment infrastructure and Govern policy.

  3. You can filter the page to include only deployed bundles.

Dataiku screenshot of the Details panel of a bundle in the Bundle registry page.

Next steps#

Now that you know about centralization in Dataiku Govern, learn how to launch item governance in Concept | Adding a governance layer to Dataiku items.