# PostgREST vs trigger

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

| | PostgREST | trigger |
|---|---|---|
| Score | 79/100 ✓ | 76/100 |
| Rank in category | #2 of 13 in API | #7 of 32 in Workflow Automation |
| GitHub stars | 27 737 ✓ | 16 648 |
| Stars, last 30 days | +60 | +249 ✓ |
| Stable releases, 12 months | 20 | 51 ✓ |
| Latest release | v16.5 · 18 Oct 2026 | v4.8.2 · 29 Oct 2026 ✓ |
| Setup | Easy ✓ | Advanced |
| Official Docker image | Yes | Yes |
| License | MIT | Apache-2.0 |
| Main language | Haskell | Typescript |

## Which one should you pick?

PostgREST scores 79/100 against 76/100 for trigger, so it is the safer default.

trigger ships more often: 51 stable releases in the past year, against 20 for PostgREST.

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

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

## Details

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

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