Request TrackervsSRS
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Request Tracker | SRS | |
|---|---|---|
| Score | 65/100 | 78/100 |
| Rank in category | #3 of 9 in Helpdesk | #4 of 118 in Media Server |
| GitHub stars | 1 164 | 29 391 |
| Stars, last 30 days | +5 | +112 |
| Stable releases, 12 months | 2 | 13 |
| Latest release | rt-5.0.10 · 1 Jun 2026 | v7.0-a3 · 25 Oct 2026 |
| Setup | Advanced | Moderate |
| Official Docker image | No | Yes |
| License | GPL-2.0 | MIT |
| Main language | Perl | C |
Which one should you pick?
SRS scores 78/100 against 65/100 for Request Tracker, so it is the safer default.
SRS ships more often: 13 stable releases in the past year, against 2 for Request Tracker.
If you want the quickest setup, SRS is easier to run; Request Tracker needs more configuration.
SRS is growing faster right now (+112 stars in 30 days).
Request Tracker details →SRS details →
Swap a project
Keep Request Tracker, compare it with
Keep SRS, compare it with