Convoyvslaudspeaker
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Convoy | laudspeaker | |
|---|---|---|
| Score | 61/100 | 48/100 |
| Rank in category | #12 of 38 in API Gateway | #2 of 3 in Customer Engagement |
| GitHub stars | 2 891 | 2 635 |
| Stars, last 30 days | +13 | +7 |
| Stable releases, 12 months | 30 | 0 |
| Latest release | v26.9.5 · 12 Nov 2026 | — |
| Setup | Moderate | Advanced |
| Official Docker image | Yes | Yes |
| License | Elastic-2.0 | AGPL-3.0 |
| Main language | Go | Typescript |
Which one should you pick?
Convoy scores 61/100 against 48/100 for laudspeaker, so it is the safer default.
Convoy ships more often: 30 stable releases in the past year, against 0 for laudspeaker.
If you want the quickest setup, Convoy is easier to run; laudspeaker needs more configuration.
Key differences
- License: Convoy is Elastic-2.0, laudspeaker is AGPL-3.0.
- Language: Convoy is written mainly in Go, laudspeaker in Typescript.
- Platforms only Convoy lists: Kubernetes (Helm).
- Features only Convoy lists: Automatic Retries, Batch retries, Circuit Breaking, Dynamic endpoints and 11 more.
- Features only laudspeaker lists: A/B Testing, CSV user import, Event-triggered messaging, External API calls in journeys and 7 more.
Convoy details →laudspeaker details →