# dagger/dagger

Automation engine to build, test and ship any codebase. Runs locally, in CI, or directly in the cloud

Repository: https://github.com/dagger/dagger
Canonical: https://ross.abutalabs.com/products/dagger
Homepage: https://dagger.io
Language: Go
License: Apache-2.0
License Family: permissive
Topics: ci-cd, containers, continuous-deployment, continuous-integration, devops, docker, agents, caching, graphql, workflows
Last push: 2026-08-26T23:54:00+00:00

## Health v2 (maintenance only)
Score: 95/100 (v2, computed 2026-09-03T02:39:23.370411+00:00)
- activity 99, release rhythm 87, longevity 100
- inputs: {"age_days": 2479, "days_push": 7, "days_rel": 7, "gap_med": 0.0, "n_releases_24m": 557}
- flags: none
- formula: round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10)

## Adoption (not part of the score)
Stars 16203, forks 914 (observed 2026-08-28T04:11:14.907062+00:00)

## What it is
Dagger is a programmable automation engine for building, testing, and shipping software, replacing YAML pipelines with real code via SDKs in 8 languages. It runs pipelines as cached, sandboxed containerized DAGs locally, in CI, or in the cloud, with built-in OpenTelemetry tracing.

## Use cases
- replace YAML CI pipelines with real code
- run the same build pipeline locally and in CI
- cache incremental builds and tests across runs
- run e2e tests with just-in-time service containers
- trace and debug CI pipeline failures with OpenTelemetry
- let AI agents run sandboxed checks in their dev loop
- orchestrate containers and secrets from Go, Python, or TypeScript

## When to choose
- you want pipeline logic as typed, testable code instead of vendor-specific YAML
- you need identical behavior for builds on a laptop, CI server, and cloud
- slow or flaky CI is hurting your team and you want incremental caching and end-to-end tracing
- you want reusable, shareable pipeline modules across projects

## When to avoid
- you need a fully managed turnkey CI with zero learning investment
- your team is small and happy with existing GitHub Actions/GitLab CI YAML
- you cannot rely on a Linux container runtime in your environment
- you need a stable 1.0 guarantee and cannot track a fast-moving beta API

## Facets
- artifact type: application
- maturity: active
- function: ci-cd, deployment, container-runtime, developer-tools, workflow-automation, caching, tracing, secrets-management
- domain: developer-tools, cloud-computing
- platform: windows, go, python, rust, jvm, dotnet, cli, cloud
- tags: ci-pipelines, dag-execution-engine, containerized-builds, opentelemetry, local-first-ci, sdks, reusable-modules, ai-agents, devops, containers, automation, linux, macos, docker, nodejs

## Member repositories
- dagger/dagger (main) score 95

## Provenance
- Observed fields: from GitHub, fetched 2026-08-28T04:11:14.907062+00:00.
- Health v2: computed from the inputs above; adoption is never an input.
- Inferred fields (summary, facets, guidance): AI-extracted, prompt v1, taxonomy v1, on 2026-08-29T17:05:11.987041+00:00, confidence not recorded.
  - readme: https://github.com/dagger/dagger (fetched 2026-08-28T04:11:14.907062+00:00, sha f6f9073b1553)
  - homepage: https://dagger.io (fetched 2026-08-29T08:02:51.204163+00:00, sha 5577e3650769)
  - site_page: https://docs.dagger.io (fetched 2026-08-29T08:02:51.208579+00:00, sha feb4a153c61f)
  - site_page: https://dagger.io/pricing (fetched 2026-08-29T08:02:51.206828+00:00, sha 119987b6c386)
  - site_page: https://dagger.io/changelog (fetched 2026-08-29T08:02:51.210447+00:00, sha 9dd82c8b05b6)
- Data as of 2026-08-30T08:39:29.467469+00:00.