# Data (/docs/data)



Data is the product domain for moving information from source systems into governed pipelines, workspaces, models, analytics, and AI experiences. It connects data engineering and data science without requiring users to operate the underlying platform components.

## Choose an outcome [#choose-an-outcome]

<Cards>
  <Card title="Build a data workflow" href="/docs/get-started/build-data-workflow" description="Follow the path from a source to an operated data or ML result." />

  <Card title="Open a Developer Workspace" href="/docs/data/developer-workspace" description="Use managed development environments, pipelines, and MLflow." />

  <Card title="Build and run pipelines" href="/docs/data/developer-workspace/pipelines" description="Upload, execute, schedule, and inspect pipeline runs." />

  <Card title="Work with data tools" href="/docs/use/data" description="Use the platform's data-facing interfaces and services." />
</Cards>

## Capability map [#capability-map]

### Integrate and move data [#integrate-and-move-data]

Data integration connects applications, databases, object stores, and external services to governed platform workflows. Connectors define the source and destination; orchestration controls when work runs; operational signals show whether transfers are healthy.

Use the [Airbyte component reference](/docs/data/components/airbyte) when diagnosing an existing connector implementation.

### Engineer and orchestrate data [#engineer-and-orchestrate-data]

Lakehouse and pipeline capabilities organize catalog-backed tables, processing jobs, artifacts, schedules, and dependencies. [Developer Workspace pipelines](/docs/data/developer-workspace/pipelines) provide the practical path for building and operating reusable workflows.

### Govern and discover data [#govern-and-discover-data]

Catalog and authorization capabilities describe schemas, ownership, permissions, lineage, and the tenant or team allowed to use an asset. [Multi-tenancy and tiered RBAC](/docs/data/multi-tenancy-and-tiered-rbac) explains how those boundaries apply across Data.

### Develop models and experiments [#develop-models-and-experiments]

Developer Workspace provides notebook-first and Python-first environments. MLflow records experiments, artifacts, and model registrations so that development work can move into governed AI serving without losing its history.

Start with [track experiments](/docs/data/developer-workspace/mlflow/track-experiments) and [register models](/docs/data/developer-workspace/mlflow/register-models).

### Stream and analyze [#stream-and-analyze]

Streaming moves events through Kafka-backed paths. Analytics and BI turn governed data into dashboards and operational views. These paths share catalog, access-control, observability, and storage responsibilities with batch workflows.

### Natural-language data access [#natural-language-data-access]

Natural-language experiences combine a governed semantic model, controlled query execution, citations, and permission-aware answers. They sit across Data and AI: Data protects the meaning and access boundary; AI provides the conversational experience.

## Typical data-to-production flow [#typical-data-to-production-flow]

1. Identify the source, owner, classification, and expected refresh behavior.
2. Choose a connector or approved ingestion path.
3. Develop transformations or models in a managed workspace.
4. Package the work as a repeatable pipeline with artifacts and parameters.
5. Track experiments and register models when machine learning is involved.
6. Apply tenant, team, catalog, and data-access policies before production use.
7. Monitor freshness, failures, consumption, and downstream impact.

## Architecture and implementation [#architecture-and-implementation]

<Cards>
  <Card title="Reference architecture" href="/docs/data/reference-architecture" />

  <Card title="How Data complements AI" href="/docs/data/how-data-complements-ai" />

  <Card title="Data component catalog" href="/docs/data/components" />

  <Card title="Explore the platform" href="/docs/platform" />
</Cards>