# Gitness vs StackRender

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

| | Gitness | StackRender |
|---|---|---|
| Score | 80/100 ✓ | 50/100 |
| Rank in category | #2 of 14 in Code Hosting | #34 of 40 in Database Management |
| GitHub stars | 38 748 ✓ | 555 |
| Stars, last 30 days | +321 | — |
| Stable releases, 12 months | 6 ✓ | 1 |
| Latest release | v2.28.2 · 20 Apr 2026 | v1.4.0 · 10 Jun 2026 ✓ |
| Setup | Easy ✓ | Moderate |
| Official Docker image | Yes ✓ | No |
| License | Apache-2.0 | AGPL-3.0 |
| Main language | Go | Typescript |

## Which one should you pick?

Gitness scores 80/100 against 50/100 for StackRender, so it is the safer default.

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

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

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

## Details

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

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