# frp vs trigger

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

| | frp | trigger |
|---|---|---|
| Score | 85/100 ✓ | 76/100 |
| Rank in category | #1 of 25 in Proxy | #7 of 32 in Workflow Automation |
| GitHub stars | 110 248 ✓ | 16 645 |
| Stars, last 30 days | +654 ✓ | +258 |
| Stable releases, 12 months | 10 | 49 ✓ |
| Latest release | v0.71.1 · 14 Oct 2026 | v4.8.1 · 23 Oct 2026 ✓ |
| Setup | Moderate ✓ | Advanced |
| Official Docker image | No | Yes ✓ |
| License | Apache-2.0 | Apache-2.0 |
| Main language | Go | Typescript |

## Which one should you pick?

frp scores 85/100 against 76/100 for trigger, so it is the safer default.

trigger ships more often: 49 stable releases in the past year, against 10 for frp.

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

frp is growing faster right now (+654 stars in 30 days).

## Details

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

---
Source: https://selfhost.directory/compare/frp-vs-trigger