harnessvsPipewright
Two self-hosted CI/CD projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| harness | Pipewright | |
|---|---|---|
| Score | 79/100 | 49/100 |
| Rank in category | #3 of 28 in CI/CD | #23 of 28 in CI/CD |
| GitHub stars | 38 919 | 160 |
| Stars, last 30 days | +391 | +33 |
| Stable releases, 12 months | 6 | 26 |
| Latest release | v2.28.2 · 20 Apr 2026 | v2.4.0 · 16 Nov 2026 |
| Setup | Easy | Moderate |
| Official Docker image | Yes | Yes |
| License | Apache-2.0 | MIT |
| Main language | Go | Go |
Which one should you pick?
harness scores 79/100 against 49/100 for Pipewright, so it is the safer default.
Pipewright ships more often: 26 stable releases in the past year, against 6 for harness.
If you want the quickest setup, harness is easier to run; Pipewright needs more configuration.
harness is growing faster right now (+391 stars in 30 days).
Key differences
- License: harness is Apache-2.0, Pipewright is MIT.
- Platforms only Pipewright lists: Build from Source, macOS, Windows.
- Features only harness lists: Artifact Registry, CI/CD Pipelines, CLI, Cloud development environments and 11 more.
- Features only Pipewright lists: AI-assisted failure diagnosis, Append-only audit log, Auto HTTPS with Caddy, Credential Vault and 11 more.
harness details →Pipewright details →All CI/CD projects →