A
ahoy_email
74.5
1,194 stars · MIT
Analytics
Plausible leads by 17.6 · decisive
A
74.5
1,194 stars · MIT
B · leads
92.1
29,871 stars · AGPL-3.0
ahoy_email versus Plausible 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; Plausible is written mainly in Elixir. The composite score is 74.5 for ahoy_email and 92.1 for Plausible.
Plausible has 29,871 GitHub stars to ahoy_email's 1,194, a gap of 28,677 (25.02×). Forks are 144 for ahoy_email and 1,940 for Plausible. On the log scale used inside this pair, adoption is 69 versus 100, and the fork community is 66 versus 100.
Push history: ahoy_email was last pushed on 21 September 2026 (61 days ago), and Plausible was last pushed on 17 November 2026 (5 days ago). Open issues stand at 1 for ahoy_email (0.001 per star) and 58 for Plausible (0.002 per star). Issue-health scores are 96 and 96; 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. Plausible is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. License scores in this pair are 96 for ahoy_email and 52 for Plausible. This is a procurement signal, not legal advice.
In Analytics, both ahoy_email (1,194 stars) and Plausible (29,871 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, Plausible is freemium.
The lead is split. ahoy_email is furthest ahead on license flexibility (96 to 52), while Plausible is furthest ahead on fork community (100 to 66). Choose the dimension a rollout cannot compromise on.
Plausible finishes ahead at 92.1 against ahoy_email at 74.5, a 17.6 point decisive 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 | Plausible |
|---|---|---|
| GitHub stars | 1,194 | 29,871 |
| Forks | 144 | 1,940 |
| Open issues | 1 | 58 |
| Adoption | 69 | 100 |
| Activity | 58 | 92 |
| Community | 66 | 100 |
| Issue health | 96 | 96 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 74.5 | 92.1 |
First-party email analytics for Rails
Plausible is a lightweight, cookie-less web analytics tool. The community edition can be self-hosted; the company also sells a managed service.
Plausible has more GitHub stars: 29,871 versus 1,194 for ahoy_email. The gap is 28,677 stars.
Plausible 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 Plausible 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. Plausible is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Plausible scores 92.1 and ahoy_email scores 74.5. This page calls that a decisive lead for Plausible.