# CloakBrowser vs trigger

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

| | CloakBrowser | trigger |
|---|---|---|
| Score | 75/100 | 76/100 ✓ |
| Rank in category | #2 of 11 in Browser Automation | #7 of 32 in Workflow Automation |
| GitHub stars | 32 560 ✓ | 16 646 |
| Stars, last 30 days | +202 | +259 ✓ |
| Stable releases, 12 months | 5 | 49 ✓ |
| Latest release | chromium-v155.0.8059.39.2-pro · 27 Oct 2026 ✓ | v4.8.1 · 23 Oct 2026 |
| Setup | Moderate ✓ | Advanced |
| Official Docker image | Yes | Yes |
| License | MIT | Apache-2.0 |
| Main language | Python | Typescript |

## Which one should you pick?

trigger scores 76/100 against 75/100 for CloakBrowser, so it is the safer default.

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

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

## Details

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

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