# Gitness vs mkcertWeb

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

| | Gitness | mkcertWeb |
|---|---|---|
| Score | 80/100 ✓ | 48/100 |
| Rank in category | #2 of 14 in Code Hosting | #6 of 8 in Certificate Management |
| GitHub stars | 38 756 ✓ | 221 |
| Stars, last 30 days | +322 ✓ | +0 |
| Stable releases, 12 months | 6 | 13 ✓ |
| Latest release | v2.28.2 · 20 Apr 2026 | v4.4.2 · 15 Oct 2026 ✓ |
| Setup | Easy ✓ | Moderate |
| Official Docker image | Yes | Yes |
| License | Apache-2.0 | GPL-3.0 |
| Main language | Go | JavaScript |

## Which one should you pick?

Gitness scores 80/100 against 48/100 for mkcertWeb, so it is the safer default.

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

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

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

## Details

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

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