A
ahoy_email
73.1
1,194 stars · MIT
Analytics
langfuse leads by 13.7 · clear
A
73.1
1,194 stars · MIT
B · leads
86.8
37,546 stars · license n/a
ahoy_email versus langfuse is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. ahoy_email is written mainly in Ruby; langfuse is written mainly in TypeScript. The composite score is 73.1 for ahoy_email and 86.8 for langfuse.
langfuse has 37,546 GitHub stars to ahoy_email's 1,194, a gap of 36,352 (31.45×). Forks are 144 for ahoy_email and 4,243 for langfuse. On the log scale used inside this pair, adoption is 67 versus 100, and the fork community is 60 versus 100.
Push history: ahoy_email was last pushed on 21 September 2026 (61 days ago), and langfuse was last pushed on 17 November 2026 (5 days ago). Open issues stand at 1 for ahoy_email (0.001 per star) and 1,173 for langfuse (0.031 per star). Issue-health scores are 96 and 70; activity scores are 58 and 92.
ahoy_email is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. langfuse is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for ahoy_email and 30 for langfuse. This is a procurement signal, not legal advice.
In Analytics, both ahoy_email (1,194 stars) and langfuse (37,546 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: ahoy_email is open source, langfuse is unpriced in this catalog.
The lead is split. ahoy_email is furthest ahead on license flexibility (96 to 30), while langfuse is furthest ahead on fork community (100 to 60). Choose the dimension a rollout cannot compromise on.
langfuse finishes ahead at 86.8 against ahoy_email at 73.1, a 13.7 point clear margin under the published weights.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | ahoy_email | langfuse |
|---|---|---|
| GitHub stars | 1,194 | 37,546 |
| Forks | 144 | 4,243 |
| Open issues | 1 | 1,173 |
| Adoption | 67 | 100 |
| Activity | 58 | 92 |
| Community | 60 | 100 |
| Issue health | 96 | 70 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 73.1 | 86.8 |
First-party email analytics for Rails
🪢 Open source AI engineering platform: AI Gateway, agent observability, evals, and prompt/skill management, built on OpenTelemetry. One open platform for every AI call and every agent. Self-host or use Langfuse Cloud.
langfuse has more GitHub stars: 37,546 versus 1,194 for ahoy_email. The gap is 36,352 stars.
langfuse was pushed more recently: 17 November 2026 versus 21 September 2026 for ahoy_email. That is 56 days apart.
Yes. This catalog marks both ahoy_email and langfuse as self-hostable. Confirm each project's deploy docs before you plan a migration.
ahoy_email is listed as MIT, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. langfuse is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
langfuse scores 86.8 and ahoy_email scores 73.1. This page calls that a clear lead for langfuse.