dagster-io/dagster

An orchestration platform for the development, production, and observation of data assets.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 9 minutes ago
Added to GitGenius on September 3rd, 2026
Created on April 30th, 2018
Open Issues & Pull Requests: 2,585 (+0)
GitHub issues: Enabled
Number of forks: 2,281
Total Stargazers: 16,124 (+0)
Total Subscribers: 160 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.1 days
Mean response time: 111.0 days
90th percentile: 365.8 days
Tracked items: 1,708

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 69% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 2% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 791
New in 7 days: 4
Closed in 7 days: 4
Avg open age: 681 days
Stale 30+ days: 703
Stale 90+ days: 590

Recent activity

Opened in 7 days: 3
Closed in 7 days: 4
Comments in 7 days: 6
Events in 7 days: 24

Top labels

  • type: bug (1,148)
  • stale (726)
  • type: feature-request (651)
  • area: UI/UX (165)
  • area: docs (146)
  • integration: dbt (80)
  • area: partitions (74)
  • deployment: k8s (74)

Detailed Description

Dagster is an orchestration platform for the development, production, and observation of data assets.

Dagster addresses the challenge of building reliable data pipelines by treating data assets as first-class objects rather than focusing solely on tasks or jobs. The platform enables developers to define, test, and monitor data workflows through a Python-native approach. Assets are connected through dependencies, allowing Dagster to understand the full lineage of data and automatically orchestrate their computation. The system provides observability into asset health, data quality, and execution history, making it possible to understand what data exists, how it was produced, and whether it meets expectations.

Teams building data platforms, analytics infrastructure, or machine learning pipelines should consider Dagster when they need visibility into data lineage and asset dependencies. The tool suits projects where understanding data provenance matters as much as job execution, and where teams want to catch data quality issues early in development rather than in production. It works well for organizations moving beyond simple task scheduling toward asset-oriented data engineering practices.

The project maintains active development with regular updates to core functionality and integrations. The codebase shows consistent refinement of the asset-centric model and expansion of observability features. Development includes ongoing work on the execution engine and improvements to how the system tracks and reports on data asset state. The project demonstrates sustained investment in documentation and examples that help teams adopt the asset-first approach.