A
ahoy_email
72.0
1,194 stars · MIT
Analytics
Metabase leads by 15.7 · decisive
A
72.0
1,194 stars · MIT
B · leads
87.7
50,382 stars · AGPL-3.0
ahoy_email versus Metabase 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; Metabase is written mainly in Clojure. The composite score is 72.0 for ahoy_email and 87.7 for Metabase.
Metabase has 50,382 GitHub stars to ahoy_email's 1,194, a gap of 49,188 (42.20×). Forks are 144 for ahoy_email and 7,016 for Metabase. On the log scale used inside this pair, adoption is 65 versus 100, and the fork community is 56 versus 100.
Push history: ahoy_email was last pushed on 21 September 2026 (61 days ago), and Metabase was last pushed on 17 November 2026 (5 days ago). Open issues stand at 1 for ahoy_email (0.001 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 96 and 52; 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. Metabase 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 Metabase. This is a procurement signal, not legal advice.
In Analytics, both ahoy_email (1,194 stars) and Metabase (50,382 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, Metabase is freemium.
The lead is split. ahoy_email is furthest ahead on issue health (96 to 52), while Metabase is furthest ahead on fork community (100 to 56). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 87.7 against ahoy_email at 72.0, a 15.7 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 | Metabase |
|---|---|---|
| GitHub stars | 1,194 | 50,382 |
| Forks | 144 | 7,016 |
| Open issues | 1 | 4,696 |
| Adoption | 65 | 100 |
| Activity | 58 | 92 |
| Community | 56 | 100 |
| Issue health | 96 | 52 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 72.0 | 87.7 |
First-party email analytics for Rails
Metabase is a business-intelligence tool that lets teams ask questions of a SQL database without writing a report from scratch. It is commonly self-hosted next to the warehouse it reads.
Metabase has more GitHub stars: 50,382 versus 1,194 for ahoy_email. The gap is 49,188 stars.
Metabase 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 Metabase 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. Metabase 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.
Metabase scores 87.7 and ahoy_email scores 72.0. This page calls that a decisive lead for Metabase.