Softwr
Dagger logo

Dagger

Programmable CI/CD engine that runs your pipeline as containers on any runner

As of 20 November 2026, Dagger has a free plan and paid plans start at $50/month. An open source engine, from the founders of Docker, that lets you write CI pipelines as code in Go, Python or TypeScript and run the identical pipeline locally and on any CI provider. Softwr lists it under Developer Tools. Dagger is made by Dagger, Inc., available on Linux, macOS, Windows, Self-hosted.

Overview

What is Dagger?

Dagger takes the pipeline out of YAML and puts it into a general-purpose programming language. You define build, test and deploy steps as functions using an SDK in Go, Python, TypeScript, PHP or Java; Dagger compiles them into a directed acyclic graph of containerised operations and executes them through a BuildKit-based engine with aggressive content-addressed caching. The same code runs on a developer laptop and inside GitHub Actions, GitLab CI or Jenkins. The distinguishing property is that it is deliberately not a CI provider. Dagger has no hosted runners, no repository triggers and no build queue. It is a portable execution layer you invoke from whatever CI you already pay for, which means the pipeline stops being coupled to that vendor. That is the commercial argument: you can change CI provider without rewriting pipelines, and you can reproduce a failing CI run on your own machine instead of pushing commits to debug. The paid product, Dagger Cloud, sells observability over those runs rather than compute. Buyers are platform and DevOps teams at companies large enough to feel YAML sprawl across many repositories, and teams who have been burned by CI runs that cannot be reproduced locally. The trade-off is that you are adding a layer, not removing one: you still pay your CI provider, you still maintain runners, and your engineers must learn a container-graph model plus an SDK before they can debug the thing that builds everything.

What people use it for

  • A platform team maintaining near-identical build YAML across forty repositories that wants one versioned module every repository calls instead
  • An engineering organisation migrating off a CI provider that does not want to rewrite every pipeline as part of the migration
  • A team whose engineers waste hours pushing commits to debug CI-only failures and needs to reproduce the exact run locally
  • A monorepo where most commits touch a small subset of services and cache-accurate step skipping cuts build minutes materially

The honest half

Where does Dagger fall short?

Each is concrete and checkable: the half of a review a vendor will not write.

  • Dagger is not a CI provider, so you keep paying for GitHub Actions or GitLab runners underneath it; the Dagger Cloud subscription is an addition to your CI bill, not a replacement for it.
  • Writing pipelines in Go or TypeScript raises the barrier to entry: a release engineer who could edit a YAML step now needs to read code, and the people who can fix a broken build shrink to those comfortable with the SDK.
  • The engine runs as a container on the runner and needs a persistent cache volume to deliver its main benefit, so ephemeral CI runners give you correctness without the speed, and provisioning durable cache storage is extra platform work.
  • The Team plan caps at ten users and ten million events per month; an organisation of any size crosses that quickly and moves to Enterprise pricing that is not published, so cost at scale is unknowable up front.
  • The module ecosystem is young and thinly maintained relative to the marketplace of a mature CI provider, so integrations that exist as a one-line Action often have to be written yourself as a Dagger function.

Cross-shopped

What are the alternatives to Dagger?

The closest alternatives to Dagger are Earthly, GitHub Actions and Buildkite. Each is a tool buyers genuinely weigh against it, with the reason why.

  • Dagger vs Earthly

    Earthly: If you want repeatable containerised builds with a Makefile-like syntax rather than a general-purpose programming language

  • Dagger vs GitHub Actions

    GitHub Actions: If you want triggers, hosted runners and a large marketplace in one product and can accept YAML and vendor coupling

  • Dagger vs Buildkite

    Buildkite: If you want to keep your own compute but let a hosted control plane handle orchestration and pipeline visibility

  • Dagger vs CircleCI

    CircleCI: Hosted CI/CD service, an alternative for teams that want managed pipelines rather than portable ones.

Pricing

How much does Dagger cost?

Dagger has a free plan, and paid plans start at $50/mo, across 3 plans. Taken from the vendor's own pricing page; prices move, so check before you buy.

Individual

Free

  • One user
  • One million events per month
  • Workflow logs and function call traces
  • Cache visibility
  • GitHub Checks integration
  • One month run history

Team

$50 /mo

  • Up to ten users
  • Ten million events per month
  • Module insights and module catalogue
  • One year run history
  • Email support
  • Two week trial

Enterprise

On request

  • Custom user and event limits
  • SSO
  • Managed single-tenant deployment
  • 24/7 premium support

Capabilities

What can Dagger do?

Dagger lists 8 features, including pipelines as code; local and CI parity; and content-addressed caching.

  • Pipelines as code

    Define steps as functions in Go, Python, TypeScript, PHP or Java rather than YAML

  • Local and CI parity

    The same pipeline code runs identically on a laptop and in any CI provider

  • Content-addressed caching

    BuildKit-backed cache that skips any step whose inputs have not changed

  • Dagger Functions and modules

    Reusable, versioned pipeline components shared across repositories

  • CI-provider agnostic

    Runs inside GitHub Actions, GitLab CI, Jenkins, CircleCI or a bare shell

  • Dagger Cloud traces

    Per-function call traces, logs and cache visibility for every run

  • GitHub Checks integration

    Pipeline results surfaced against pull requests

  • Container-native execution

    Every step is a container, so the toolchain is pinned by image rather than by runner state

Answered, with sources

Questions people ask

Each answer names the page it came from, so you can check it rather than take our word for it.

Does Dagger replace GitHub Actions?

No. Dagger runs inside GitHub Actions or any other CI. It replaces the YAML that describes your pipeline steps, not the trigger and runner layer.

Is the engine open source?

Yes, the Dagger engine and SDKs are open source and free. Dagger Cloud, the observability product, is what costs money.

What is an event in the pricing?

Dagger Cloud meters pipeline telemetry events. One million per month is free; the Team plan at 50 USD per month allows ten million.

Can I run the same pipeline on my laptop?

Yes, that is the main reason teams adopt it. The dagger CLI executes the identical graph locally, so CI-only failures become reproducible.

Share

Keep looking

Where to go from Dagger

Best Developer Tools software for

Compare Dagger with

Other Developer Tools software

  • Engineering guardrails for the AI era

    Free plan13 researched notes
  • CI/CD pipelines that run on your own compute

    Free, then $30/mo12 researched notes
  • Automatically build, test, deploy, and monitor your applications with GitLab CI/CD

    Free plan12 researched notes
  • Local Kubernetes development loop that rebuilds and live-updates containers on save

    Open source15 researched notes
  • Build system that turns a source directory into an OCI image, now in maintenance mode

    Open source13 researched notes
  • Cloud-based builds and CI runs 55x faster with less cost

    Free, then $20/mo13 researched notes
  • A self-hosted automation server that can build almost anything, through a plugin ecosystem that is also its main liability.

    Free plan16 researched notes
  • 2x faster GitHub Actions with 60% cost savings

    Free, then $0.004/minute11 researched notes
  • Specification and tooling that turns source code into OCI images without Dockerfiles

    Open source14 researched notes
  • 2x faster, 50% cheaper GitHub Actions runners

    From $0.002/minute13 researched notes
  • JetBrains IDE for developing applications in Go

    From $24/mo13 researched notes
  • Open source build automation tool for Java, Kotlin and Android projects

    Free plan13 researched notes
  • AI-powered memory layer that captures and organizes developer work

    Free, then $18.99/mo13 researched notes
  • Accelerate how you build, share, and run applications

    Free, then $11/mo10 researched notes
  • Production-grade container orchestration

    Free plan12 researched notes
  • JetBrains IDE for PHP web development

    From $24/mo9 researched notes
  • JetBrains IDE for Ruby and Ruby on Rails development

    From $24/mo10 researched notes

Softwr does not host reviews and shows no star rating for Dagger, because a rating we did not collect is not ours to publish. What is here is the pricing and platform detail from the vendor’s own pages, limitations we could state concretely, and alternatives a reviewer confirmed people weigh against it. Tell us if any of it is wrong.

More on Dagger

Best Developer Tools software alternatives

Cloud hosted development environments configured by dev container files

usage-based

TypeScript toolkit from Vercel for building AI applications and agents

open-source

Metalinter that runs and manages linters, formatters and security scanners

freemium

Free graphical Git client from Atlassian for Windows and macOS

free

Open source build automation tool for Java, Kotlin and Android projects

open-source

Git GUI client and developer tool suite with a free Community plan and paid team plans

freemium

Self-hosted, open source Git service with issues, CI/CD and package hosting

open-source

Minimal container base images from Google that hold only an app and its runtime

open-source

Compare Dagger with alternatives