Dagger for GitHub

Dagger can now run your checks on every pull request, without GitHub Actions or one of its clones. Run the same pipelines before or after push, with shared caching and scalable compute. Pay for exact pipeline usage, not entire machines.

Try it now

Cut out the middleman

Dagger already ran your pipelines before push. Now it can also run them after push, directly from GitHub events, without third-party CI.

No more proprietary YAML and overpriced VMs: set up Dagger locally, install our GitHub app, and you’re done. Every pull request triggers the same Dagger checks you run locally, executed and cached by Dagger Cloud.

No more noisy logs: each check links to a high-resolution trace, so agents can debug accurately without wasting tokens.

Scale without wasting compute

Dagger Cloud runs your pipelines on managed engines. They scale automatically and share a distributed cache, so they skip repeat work. With remote execution, your agents can use the same compute and cache while they develop: run dagger --engine=cloud, and checks that passed before push are cache hits in CI. Execution is fully sandboxed, so this sharing is safe.

You pay for the exact resources each pipeline uses, not entire machines. Operations that could come from the cache cost 5× less, whether or not they actually do. Learn more about pricing.

Debug without wasting tokens

Each GitHub check links to its full Dagger trace. Agents can inspect each operation and see the full context of a failure, without parsing large CI logs.

Join us on Discord and tell us what you think.