# Reactive Resume vs trigger

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

| | Reactive Resume | trigger |
|---|---|---|
| Score | 87/100 ✓ | 76/100 |
| Rank in category | #1 of 46 in Document Management | #7 of 32 in Workflow Automation |
| GitHub stars | 44 998 ✓ | 16 644 |
| Stars, last 30 days | +1 625 ✓ | +257 |
| Stable releases, 12 months | 34 | 49 ✓ |
| Latest release | v6.0.7 · 26 Oct 2026 ✓ | v4.8.1 · 23 Oct 2026 |
| Setup | Moderate ✓ | Advanced |
| Official Docker image | Yes | Yes |
| License | MIT | Apache-2.0 |
| Main language | Typescript | Typescript |

## Which one should you pick?

Reactive Resume scores 87/100 against 76/100 for trigger, so it is the safer default.

trigger ships more often: 49 stable releases in the past year, against 34 for Reactive Resume.

If you want the quickest setup, Reactive Resume is easier to run; trigger needs more configuration.

Reactive Resume is growing faster right now (+1 625 stars in 30 days).

## Details

- [Reactive Resume](https://selfhost.directory/project/reactive-resume) (markdown: https://selfhost.directory/project/reactive-resume.md)
- [trigger](https://selfhost.directory/project/trigger) (markdown: https://selfhost.directory/project/trigger.md)

---
Source: https://selfhost.directory/compare/reactive-resume-vs-trigger