Prefect Bought Dagster. Airflow Still Has More Stars Than Both Combined.

Prefect acquired Dagster this week in a deal Prefect founder and CEO Jeremiah Lowin framed as proof that "the modern orchestration category has a new center of gravity." Run the numbers before accepting the framing. Add Dagster's GitHub stars to Prefect's and the combined total still trails Apache Airflow, a nine-year-old project neither company managed to out-adopt alone, and now cannot out-adopt together either.

This is not the story the press release wants told. It's the more useful one.

The deal, in the terms Prefect chose

The mechanics are straightforward. Prefect is acquiring Dagster in a deal that has not yet formally closed, with no financial terms disclosed. Dagster and its managed cloud product, Dagster+, keep their existing names, pricing, and roadmaps. Roughly 40 people from the Dagster team move to Prefect. The combined company itself is expected to begin operating under the Prefect name starting August 2026, once the transaction closes. Nothing about the announced structure looks like a shutdown. It looks like an acqui-consolidation: buy the team and the technology, keep the brand running long enough to retain its customers.

Prefect's public case for why Dagster's community should trust that commitment rests on its own profitability, cited directly in the official announcement as the reason it can make long-term maintenance promises. Prefect is privately held with no disclosed financials. The claim functions as reassurance, not as something a reader can independently verify.

Lowin's own explanation leans on a framing that has nothing to do with data pipelines. He describes AI agents as needing two things: clearly defined goals, and the flexibility to improvise when their own decisions lead somewhere nobody scripted. In his telling, Dagster now handles the goal-setting side by defining and tracking outcomes, Prefect runs the improvising by executing the work, and FastMCP, Prefect's tool for connecting agents to outside systems, governs what those agents are allowed to touch. That's a coherent pitch for agent infrastructure. It is not a pitch about who wins data orchestration.

The clearest signal about what this deal actually means for the people who built Dagster sits in the gap between two documents published the same day. Both the official Prefect announcement and Dagster's own company blog describe Nick Schrock, who moved from CEO to CTO in 2022 to make way for Pete Hunt, as providing "stewardship" and staying available in an advisory capacity. Schrock's own personal blog post reads differently: "I want to share that I'll be moving on from the project and company" after eight years building it. One version was written by two communications teams managing the exit of the person who built the thing being sold. The other was written by that person.

The official announcement calls it a strategic advisory role. The founder's own post calls it moving on. Both were published the same day, and only one of them was written by the person actually leaving.

What the numbers actually say about Airflow

Set the press release language aside and look at adoption directly. As of this week, Apache Airflow's GitHub repository carries 46,286 stars. Prefect carries 23,505. Dagster carries 15,909. Add Prefect and Dagster together and the combined total is 39,414, still nearly 7,000 short of Airflow alone.

Downloads tell the same story with more weight behind it, since stars measure attention and downloads measure actual use. Apache Airflow pulls 21.56 million downloads a month from PyPI. Prefect pulls 11.75 million. Dagster pulls 8.84 million. Combined, Prefect and Dagster reach 20.59 million, still below Airflow running on its own.

Astronomer's State of Airflow 2026 survey, run across 5,800 respondents in 122 countries, adds the qualitative layer to the raw adoption numbers: 88% of respondents would recommend Airflow, and 94% believe Airflow skills will benefit their careers. That is not a community bracing for disruption. It is a community that has not registered the acquisition as relevant to its own tool choice.

The comparison guide I published in April ran Airflow, Prefect, and Dagster through real production migrations and treated all three as separate, competing bets. That framing missed something the numbers above make obvious in hindsight: two of the three were never going to out-adopt Airflow independently, and the honest response to that ceiling was to stop trying separately.

Why merging two challengers isn't the same as beating the incumbent

Adoption numbers understate a second problem: Airflow, Dagster, and Prefect were never fighting for the same buyer. Airflow holds the enterprise and Fortune 500 default position, the tool a data engineer is handed on day one at a company that already has infrastructure to run it. Dagster wins greenfield teams built around dbt, where asset-centric lineage tracking pays for the learning curve. Prefect wins small data teams, roughly 20 to 100 people, who need orchestration without the operational overhead of running Airflow themselves.

Combine two products that each hold a minority position in a different segment and the result is not automatically a majority position in either. A Fortune 500 team running Airflow on Astronomer or Cloud Composer has no reason to migrate because Prefect now owns Dagster. The dbt-heavy analytics team that chose Dagster for its asset model has no reason to prefer Prefect's execution engine just because the two share a parent company now. The merger changes who owns the roadmap. It does not change which buyer was already choosing which tool, and why.

The real battlefield is agent orchestration, not data pipelines

The part of this deal that actually makes strategic sense sits outside data orchestration entirely. FastMCP, Prefect's framework for connecting AI agents to external tools, shipped the same month Anthropic released the Model Context Protocol in late 2024. Anthropic later adopted FastMCP as the official Python SDK for MCP. As of this week, FastMCP's own repository carries 26,897 GitHub stars, more than Dagster's entire orchestrator and closing in on Prefect's own core project.

Downloads make the same point with more force. FastMCP pulled 82.3 million downloads from PyPI last month, more than Airflow, Prefect, and Dagster's orchestrators combined (42.15 million). The framework built to let AI agents call outside tools already moves more software than the entire data-pipeline stack Prefect just spent an acquisition consolidating.

That is the market where this acquisition actually matters. There is no incumbent in AI agent orchestration with Airflow's nine-year head start. Both companies had already been repositioning toward it: Prefect 3.0 shipped an explicit agentic-workflow focus in 2024, Dagster followed with YAML-based Components in 2025, then a natural-language query tool called Compass. FastMCP and its adoption by Anthropic gave Prefect the widest distribution of the three moves. Buying Dagster adds outcome-tracking and lineage capability to that stack, on a category where nobody, including Airflow, has built a nine-year lead yet.

There's a cost buried in that pitch that the acquisition announcement does not name. Teams that adopted Dagster specifically for its declarative @asset framework, the software-defined-assets approach that made lineage and governance easier, are now several architectural decisions deep into a stack owned by a company that competed against that exact approach for seven years. Whether Dagster's roadmap stays independent under a "strategic advisor" arrangement or gets quietly folded into Prefect's execution model over the next two years is not something this week's announcement actually answers. Some reporting on the deal, sourced to unverified accounts published the same day, claims Dagster's cloud platform and open-source project have an unresolved future, and that senior Dagster leadership has already left for other companies. None of that appears in the official announcement or is independently confirmed, and it should be treated as rumor rather than fact until it is. But the underlying lock-in question, whether a framework choice made in 2023 is safe from its vendor's next acquisition, is exactly the risk that shows up whenever two competitors stop competing.

The acquisition doesn't answer whether Dagster's roadmap survives contact with the company that spent seven years competing against it. It just moves the question from "which tool should we pick" to "which tool did we already commit to."

Airflow did not lose market share this week. The two companies that spent seven years failing to out-adopt it separately ran out of reasons to keep trying on that battlefield, and bet the combined company on one where the scoreboard hasn't started yet.

Sources

1. GitHub - apache/airflow repository stats (accessed 2026-07-28) - live stargazer and fork counts for Apache Airflow
2. GitHub - PrefectHQ/prefect repository stats (accessed 2026-07-28) - live stargazer and fork counts for Prefect
3. GitHub - dagster-io/dagster repository stats (accessed 2026-07-28) - live stargazer and fork counts for Dagster
4. GitHub - PrefectHQ/fastmcp repository stats (accessed 2026-07-28) - live stargazer count for FastMCP
5. PyPI Stats - apache-airflow download statistics (accessed 2026-07-28) - monthly download volume
6. PyPI Stats - prefect download statistics (accessed 2026-07-28) - monthly download volume
7. PyPI Stats - dagster download statistics (accessed 2026-07-28) - monthly download volume
8. PyPI Stats - fastmcp download statistics (accessed 2026-07-28) - monthly download volume
9. The New Stack - Paul Sawers, "Prefect just bought Dagster" (2026-07-13) - primary reporting on deal structure, executive quotes, and Schrock's departure
10. Businesswire - "Prefect Acquires Dagster: Uniting the Two Leading Modern Orchestrators" (2026-07-13) - official acquisition announcement
11. Prefect - "Prefect acquires Dagster Labs" (2026-07-13) - official company announcement and stewardship rationale
12. Dagster - "Prefect is Acquiring Dagster" (2026-07-13) - official Dagster company blog on the acquisition and Schrock's departure
13. Astronomer - "State of Airflow 2026" (2026) - 5,800 respondents across 122 countries; adoption and sentiment data
14. Hugo Lu - "The End of Dagster: Prefect Dagster Acquisition" (2026-07-13) - community reaction and the vendor lock-in argument; leadership/status claims in this source are self-described as unverified
15. Andrei Nita - "Airflow vs Prefect vs Dagster: The Production Migration Guide" (2026-04-01) - prior production migration analysis referenced in this article

Working through the challenges in this post? I help engineering leaders and CTOs navigate complex technical decisions and scale high-performing teams. Schedule a consultation →