# nginx-proxy vs trigger

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

| | nginx-proxy | trigger |
|---|---|---|
| Score | 76/100 | 76/100 |
| Rank in category | #3 of 24 in Reverse Proxy | #7 of 32 in Workflow Automation |
| GitHub stars | 19 936 ✓ | 16 646 |
| Stars, last 30 days | +18 | +259 ✓ |
| Stable releases, 12 months | 11 | 49 ✓ |
| Latest release | 1.11.6 · 16 Jul 2026 | v4.8.1 · 23 Oct 2026 ✓ |
| Setup | Easy ✓ | Advanced |
| Official Docker image | Yes | Yes |
| License | MIT | Apache-2.0 |
| Main language | Python | Typescript |

## Which one should you pick?

nginx-proxy and trigger score the same (76/100), so the choice comes down to the details below.

trigger ships more often: 49 stable releases in the past year, against 11 for nginx-proxy.

If you want the quickest setup, nginx-proxy is easier to run; trigger needs more configuration.

trigger is growing faster right now (+259 stars in 30 days).

## Details

- [nginx-proxy](https://selfhost.directory/project/nginx-proxy) (markdown: https://selfhost.directory/project/nginx-proxy.md)
- [trigger](https://selfhost.directory/project/trigger) (markdown: https://selfhost.directory/project/trigger.md)

---
Source: https://selfhost.directory/compare/nginx-proxy-vs-trigger