# Dagster

> A free tool to run pipelines. It plans the work around the tables it must build.

**Field:** Data Engineering  
**Category:** Orchestration

## Think of it like

Most planners list chores. This one lists the cakes you want, and works out the steps.

## Definition

Dagster is an open source orchestrator built around data assets. You declare the tables and files you want to exist, and how each is made from others. Dagster draws the graph from those links. It shows when each asset was last built and whether it is fresh. Tests and type checks run inside the pipeline. A paid cloud version runs it for you.

## Example

A team moves from Airflow to Dagster. Now their page shows each table, when it was last built, and which ones are stale.

## Example code

```python
import dagster as dg

@dg.asset
def raw_orders():
    return load_orders()

@dg.asset
def daily_sales(raw_orders):
    return raw_orders.groupby("day").sum()
```

Two assets. Naming raw_orders as an input is enough for Dagster to draw the arrow.

## Why it matters

People care about tables, not tasks. Planning around assets makes it easy to see what data is fresh and what broke it.

## Common mistake

Moving old task-based DAGs over one to one. You miss the main gain, which is modelling the tables themselves.

## Three principles

- **Assets first.** Declare the tables you want to exist.
- **Graph from inputs.** Links come from what each asset reads.
- **Freshness shown.** See when each table last updated.

## Related terms

- [Software-Defined Asset](https://learn.benibix.com/term/data/software-defined-asset)
- [Apache Airflow](https://learn.benibix.com/term/data/apache-airflow)
- [Prefect](https://learn.benibix.com/term/data/prefect)
- [Workflow Orchestration](https://learn.benibix.com/term/data/workflow-orchestration)
- [dbt (Data Build Tool)](https://learn.benibix.com/term/data/dbt)
- [Workflow as Code](https://learn.benibix.com/term/data/workflow-as-code)

## Told apart from

- [Dagster vs Prefect](https://learn.benibix.com/compare/dagster-vs-prefect): People think Dagster and Prefect are two names for one idea, but they start from different places and suit different teams. Dagster plans around the tables and files a pipeline builds. It shows which ones are fresh. Prefect plans around plain Python functions, and adds tracking and retries to them. Pick Dagster if you think in tables, and Prefect if you think in scripts.
- [Apache Airflow vs Dagster](https://learn.benibix.com/compare/apache-airflow-vs-dagster): People think Dagster is just another Airflow. Airflow plans the steps you run. Dagster plans the tables you want to exist, and works out the steps from them. So Dagster can tell you which table is stale. Airflow can tell you which task failed.

![Two graphs of the same pipeline. On the left, boxes are steps: extract, clean, sum up. On the right, boxes are tables: raw_orders, clean_orders, daily_sales, each with a last-updated time and a fresh or stale badge.](https://learn.benibix.com/diagrams/asset-graph.svg)

---

Source: https://learn.benibix.com/term/data/dagster
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-17
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
