Pipeline modeling with operational views
Apache Hamilton standardizes how teams express data, machine learning, and LLM pipelines, and the hosted UI adds catalog, observability, lineage, and versioning in one place.
Dagworks
Freemium
Open-source and hosted tools for reliable AI workflows with Apache Hamilton and Apache Burr
What is Dagworks?
DAGWorks builds open source and hosted tools for reliable AI workflows. Its main products are Apache Hamilton for data, machine learning, and LLM pipelines, and Apache Burr for stateful applications and agents.
The platform centers on adding observability, lineage, cataloging, tracing, and persistence with a small integration step rather than requiring teams to rebuild existing Python workflows. The site presents both self-hosted and cloud options, with hosted UIs for Hamilton and Burr and open source foundations underneath.
What can Dagworks do?
Stateful app and agent workflows
Apache Burr standardizes stateful applications and agents, with a focus on tracing and observability for application behavior.
Lineage and pipeline comparison
The Hamilton page says the UI can help resolve issues faster with lineage and pipeline comparison views that show how data, code, and models connect and change over time.
Execution and catalog views
The product presents self-populating lineage, code, catalog, and execution views to reduce onboarding time and make existing workflows easier to understand.
Telemetry and state handling
The Burr offering includes telemetry UI and pluggable persistence for self-hosted use, plus hosted execution, state management, persistence, and observability in the cloud version.
Python-first deployment flexibility
DAGWorks says Apache Hamilton runs wherever Python runs and can be used with current orchestration systems, data warehouses, notebooks, web and streaming services, and modeling libraries.
Use Cases
“Data and ML pipeline development”
Use Apache Hamilton when you need to define data, ML, or LLM pipelines in Python and want lineage, catalog, observability, and versioning to appear with minimal extra setup.
“Stateful AI applications and agents”
Use Apache Burr when you are building stateful applications, RAG systems, or agentic workflows and need hosted or self-hosted execution, state management, and observability.
“Debugging and change analysis”
Use the hosted Hamilton UI to trace how data, code, and models relate, compare pipeline versions, and understand changes over time during debugging or maintenance.
“Onboarding and collaboration”
Use the product to help new team members understand existing workflows through self-populating lineage, code, catalog, and execution views.
“Incremental adoption in existing stacks”
Use the open source frameworks with your current Python-based stack, including orchestration systems, notebooks, warehouses, web services, streaming services, and modeling libraries.
Frequently Asked Questions
Does DAGWorks offer a trial or paid plans?
DAGWorks offers hosted Apache Hamilton UI on DAGWorks and Apache Burr Cloud, alongside open source Apache Hamilton and Apache Burr options. The pricing page states that everybody gets a 14-day trial at the Team level, and that Apache Burr Cloud pricing is coming soon.
What is the difference between Apache Hamilton and Apache Burr?
Apache Hamilton standardizes how individuals and teams express data, machine learning, and LLM pipelines, with catalog, observability, lineage, and versioning available through the hosted UI. Apache Burr standardizes how stateful applications are written and executed, with tracing and observability through a single-line integration.
What kinds of workflows is DAGWorks built for?
The source describes Apache Hamilton as useful for data, machine learning, and LLM pipelines, and Apache Burr for stateful applications, agents, RAG, and agentic applications. The Hamilton page also mentions use with orchestration systems, data warehouses, notebooks, web and streaming services, and modeling libraries.
What integrations or platforms are supported?
The source does not list a complete integration catalog, but it does state that Apache Hamilton runs wherever Python does and can be used with current orchestration systems, data warehouses, notebooks, web and streaming services, and modeling libraries.
Can I self-host DAGWorks products?
The Hamilton and Burr pages both describe hosted and self-hosted/open source options. The hosted products add UI, execution, persistence, observability, and related workflow views on top of the open source frameworks.
Quick Facts
- Category
- Developer tool
- Primary products
- Apache Hamilton and Apache Burr
- Delivery model
- Open source plus hosted cloud/UI offerings
- Primary language
- Python
- Pricing signal
- 14-day Team trial; Burr Cloud pricing coming soon
- Source domain
- dagworks.io
Dagworks Traffic Analysis
Traffic data is for reference only.
- Domain Rating
- 52
Dagworks Alternatives
Sim
sim.ai
Sim is an open-source AI workspace for building, deploying, and managing AI agents with visual workflows, Chat, API access, integrations, and collaboration tools.
AgentConnect
www.agentconnect.md
AgentConnect lets teams bring ACP agents such as Claude Code, Codex, and Gemini CLI into Slack, Telegram, Discord, and GitHub, where they can take on work in the channels teams already use to collaborate. It’s open source and self-hostable, with roles, tools, memory, and configurable triggers for agent workflows.
OpenHands
openhands.dev
OpenHands is an open-source, model-agnostic platform for cloud coding agents that automates engineering workflows across local, cloud, and enterprise deployments via web, CLI, terminal UI, and SDK interfaces.
Trigger.dev
trigger.dev
Open source platform for TypeScript background jobs, AI workflows, and agents
Void
voideditor.com
Open source AI IDE based on VS Code with autocomplete, chat, agents, and local or hosted models.
Sparkco
sparkco.ai
Sparkco: open-source AI agent infrastructure, terminal tooling, prediction-market workflows, and usage-based voice-agent plans with free credit, SMS, transcripts, and integrations.