Back to all companies
Sign in
Back to all companies
DAGWorks Inc. logo

DAGWorks Inc.

Winter 2023Acquired

Open source tools & services for reliable AI Agents & AI Applications

Save
DAGWorks Inc. logo

DAGWorks Inc.

Winter 2023Acquired

Open source tools & services for reliable AI Agents & AI Applications

Save
Company details

We’re on a mission to enable everyone to build reliable AI agents & AI applications. We're fully open source, and provide a unique integrated development & observability experience for those building anything in the AI space. This is the first step towards laying the foundations for Composable AI Systems; all AI systems need observability and introspection to be first class for them to be reliable.

How? We're standardizing how people write python to express data, ML, LLM, & agent workflows/pipelines/applications with lightweight frameworks. So that no matter the author, it'll be easy to collaborate, connect, and importantly in one line integrate observability and datastore needs. This speeds up time to production and reduces TCO because code remains easy to maintain and your data flywheel stays manageable. So you can increase the top line & bottom line of your business by delivering on AI that is reliable.

We've got two open source projects:

one focused on AI applications, called Burr (https://github.com/dagworks-inc/burr). one focused on AI pipelines/workflows, called Hamilton (https://github.com/dagworks-inc/hamilton) see https://www.tryhamilton.dev

Both Hamilton & Burr come with self-hostable UIs (+ enterprise & SaaS offerings). With a one-line code change, you get versioning, lineage / tracing, cataloging, and observability out of the box with Hamilton. With Burr you get tracing, observability and persistence in a single line addition.

Location
San Francisco, CA, USA; Remote
Founded
2022
Category
AIOps
YC Directory Pagewww.dagworks.io
Founders
  • SK
    Stefan Krawczyk
    Founder
    X / TwitterLinkedIn
  • EI
    Elijah ben Izzy
    Founder
    X / TwitterLinkedIn

We’re on a mission to enable everyone to build reliable AI agents & AI applications. We're fully open source, and provide a unique integrated development & observability experience for those building anything in the AI space. This is the first step towards laying the foundations for Composable AI Systems; all AI systems need observability and introspection to be first class for them to be reliable.

How? We're standardizing how people write python to express data, ML, LLM, & agent workflows/pipelines/applications with lightweight frameworks. So that no matter the author, it'll be easy to collaborate, connect, and importantly in one line integrate observability and datastore needs. This speeds up time to production and reduces TCO because code remains easy to maintain and your data flywheel stays manageable. So you can increase the top line & bottom line of your business by delivering on AI that is reliable.

We've got two open source projects:

one focused on AI applications, called Burr (https://github.com/dagworks-inc/burr). one focused on AI pipelines/workflows, called Hamilton (https://github.com/dagworks-inc/hamilton) see https://www.tryhamilton.dev

Both Hamilton & Burr come with self-hostable UIs (+ enterprise & SaaS offerings). With a one-line code change, you get versioning, lineage / tracing, cataloging, and observability out of the box with Hamilton. With Burr you get tracing, observability and persistence in a single line addition.

Location
San Francisco, CA, USA; Remote
Founded
2022
Category
AIOps
YC Directory Pagewww.dagworks.io
Founders
  • SK
    Stefan Krawczyk
    Founder
    X / TwitterLinkedIn
  • EI
    Elijah ben Izzy
    Founder
    X / TwitterLinkedIn

Pressure-test this opportunity

Turn this teardown into a decision-ready prompt for ChatGPT, Claude, or your agent.

On this page
  • Overview
  • Founding Story
  • Timeline
  • What They Built
  • Market Position
  • Target Customers
  • Market Size
  • Competition
  • Business Model
  • Traction
  • Post-Mortem
  • Open source proved the architecture, but not the control-plane business
  • Burr improved strategic relevance and multiplied category risk
  • Acquisition was a talent-and-technology outcome, not evidence of an independent platform winner
  • Apache preserved the commons while weakening proprietary differentiation
  • Key Lessons
  • Sources

This report was generated by our Deep Research agent and may contain mistakes.

Did we get something wrong? DM @oscrhong and we'll fix it ASAP!

Startups.RIP — Dead startups, alive ideas
PricingContactPrivacyGot feedback? DM @oscrhong
Exec Briefing

Actionable insights

If you only have a few minutes to spare, here’s what investors, operators, and founders should know about DAGWorks Inc. (W23).

  1. Portability spreads faster than it captures. Hamilton fit beside existing orchestrators, which lowered adoption friction but left commercial budget with the surrounding platforms.
  2. One engineering belief crossed two markets. Explicit graphs made both dataflows and agent state inspectable. The coherence was real, but serving two ecosystems multiplied integration and positioning work for a two-person team.
  3. Open source can outlive the vendor. Apache incubation preserved Hamilton and Burr while Salesforce absorbed relevant agent expertise. Project continuity and standalone company scale are separate outcomes.
  4. Acquisition narratives need hard edges. The buyer, timing, and Agentforce role are public; price, close date, transaction rationale, and investor return are not. Good analysis stops where disclosure stops.

Overview

DAGWorks was a two-person YC W23 company built around a sharp engineering idea: ordinary Python functions could declare a dataflow graph, making machine-learning and data pipelines easier to test, inspect, and move between execution systems. Hamilton supplied that open-source foundation; Burr later applied explicit state machines, persistence, and telemetry to AI agents. The commercial layer sold hosted observability and collaboration around both projects.[1][2]

This is an acquisition story, not a conventional failure. Salesforce acquired DAGWorks in early 2025, and co-founder Elijah ben Izzy moved into Agentforce work on Agent Script and determinism.[3] The more instructive tension is that DAGWorks created credible open-source primitives, but had to commercialize a broad platform while its underlying categories were still shifting. Salesforce could capture the team’s expertise; Apache could steward the code. Public evidence does not establish that the hosted business achieved independent scale.

Founding Story

Stefan Krawczyk and Elijah ben Izzy founded DAGWorks in 2022 and joined YC’s Winter 2023 batch. The available primary sources identify them and the product, but do not establish how they met, their precise division of responsibilities, or a detailed financing history. No reliable founder interview surfaced with the two verbatim origin quotes requested by the canonical format, so this report does not manufacture them.

Their initial thesis came from a familiar problem in production machine learning: teams wrote pipelines as procedural scripts, then accumulated hidden dependencies, brittle orchestration code, and debugging work. Hamilton inverted the model. Developers wrote small Python functions whose names, inputs, and outputs described a graph. That graph could be visualized, tested, and executed without binding the business logic to Airflow, Dagster, or another orchestrator.[4]

The company paired the open-source library with a proprietary control plane. The platform tracked executions, catalogued artifacts, exposed lineage, and helped teams debug failures. In its YC launch, DAGWorks positioned Hamilton as the expression layer rather than another scheduler, and invited teams into a private beta for the commercial product.[2]

Burr expanded the ambition. Instead of data assets, Burr modeled an application as actions and transitions over explicit state. Persistence, replay, human intervention, and telemetry made it relevant to chatbots, RAG systems, simulations, and agents.[5] The move was technically coherent: both products turned implicit Python behavior into inspectable graphs. Commercially, however, it widened the market story from data and ML workflows into a fast-changing agent framework category.

Timeline

  • 2022: Krawczyk and ben Izzy founded DAGWorks.
  • Winter 2023: DAGWorks joined Y Combinator and launched Hamilton to the Hacker News community.[1][2]
  • 2023: The company reported 58 Hamilton releases, 1,100 GitHub stars on the fork, three or more Hacker News front-page appearances, 125% Slack-community growth, and its first paying customers. These figures are company-reported, not audited.[6]
  • January 2025: DAGWorks’ public archive still carried product posts.[7]
  • April 12, 2025: Hamilton entered Apache incubation.[13]
  • May 24, 2025: Burr entered Apache incubation.[14]
  • May 28, 2025: Krawczyk publicly announced that DAGWorks had joined Salesforce. The transaction’s exact close date and terms were not disclosed.[8]
  • 2026: Apache project notices continued moving Burr documentation and attribution away from DAGWorks-owned locations.[9]

What They Built

Hamilton treated a Python function as a node and its parameters as upstream dependencies. A developer could write transformation logic as plain functions, ask Hamilton to assemble the graph, and run only the outputs needed for a job. This made lineage visible and unit testing natural. It also separated computation from orchestration: teams could keep their Python model while changing where or how it ran.[4]

The commercial platform added execution history, a data catalog, observability, debugging, and integrations. The pitch resembled “dbt for Python,” but covered ML features and application logic that lived outside SQL. A browser playground lowered the trial cost, while the open-source package made adoption possible without a platform purchase.[2]

Unlock the full DAGWorks Inc. teardown

Read the complete post-mortem, the rebuild playbook, and the exact reasons DAGWorks Inc. is still worth studying now.

See Pro plans