# issue-status vs qdrant

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

| | issue-status | qdrant |
|---|---|---|
| Score | 47/100 | 82/100 ✓ |
| Rank in category | #31 of 51 in Monitoring & observability | #1 of 5 in Vector Database |
| GitHub stars | 429 | 35 300 ✓ |
| Stars, last 30 days | — | +529 |
| Stable releases, 12 months | 0 | 14 ✓ |
| Latest release | — | v1.20.0 · 21 Oct 2026 |
| Setup | Easy ✓ | Moderate |
| Official Docker image | No | Yes ✓ |
| License | MIT | Apache-2.0 |
| Main language | Typescript | Rust |

## Which one should you pick?

qdrant scores 82/100 against 47/100 for issue-status, so it is the safer default.

qdrant ships more often: 14 stable releases in the past year, against 0 for issue-status.

If you want the quickest setup, issue-status is easier to run; qdrant needs more configuration.

qdrant is growing faster right now (+529 stars in 30 days).

## Details

- [issue-status](https://selfhost.directory/project/issue-status) (markdown: https://selfhost.directory/project/issue-status.md)
- [qdrant](https://selfhost.directory/project/qdrant) (markdown: https://selfhost.directory/project/qdrant.md)

---
Source: https://selfhost.directory/compare/issue-status-vs-qdrant