# Gitness vs TraceRoot

> Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.

| | Gitness | TraceRoot |
|---|---|---|
| Score | 80/100 ✓ | 58/100 |
| Rank in category | #2 of 14 in Code Hosting | #11 of 51 in Monitoring & observability |
| GitHub stars | 38 759 ✓ | 1 138 |
| Stars, last 30 days | +325 ✓ | +26 |
| Stable releases, 12 months | 6 | 10 ✓ |
| Latest release | v2.28.2 · 20 Apr 2026 | v1.3.3 · 27 Oct 2026 ✓ |
| Setup | Easy ✓ | Advanced |
| Official Docker image | Yes ✓ | No |
| License | Apache-2.0 | Other |
| Main language | Go | Typescript |

## Which one should you pick?

Gitness scores 80/100 against 58/100 for TraceRoot, so it is the safer default.

TraceRoot ships more often: 10 stable releases in the past year, against 6 for Gitness.

If you want the quickest setup, Gitness is easier to run; TraceRoot needs more configuration.

Gitness is growing faster right now (+325 stars in 30 days).

## Details

- [Gitness](https://selfhost.directory/project/gitness) (markdown: https://selfhost.directory/project/gitness.md)
- [TraceRoot](https://selfhost.directory/project/traceroot) (markdown: https://selfhost.directory/project/traceroot.md)

---
Source: https://selfhost.directory/compare/gitness-vs-traceroot