A
DebugSwift
78.4
2,454 stars · MIT
Analytics
Umami leads by 20.7 · decisive
A
78.4
2,454 stars · MIT
B · leads
99.1
40,194 stars · MIT
DebugSwift versus Umami is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. DebugSwift is written mainly in Swift; Umami is written mainly in TypeScript. The composite score is 78.4 for DebugSwift and 99.1 for Umami.
Umami has 40,194 GitHub stars to DebugSwift's 2,454, a gap of 37,740 (16.38×). Forks are 218 for DebugSwift and 8,567 for Umami. On the log scale used inside this pair, adoption is 74 versus 100, and the fork community is 60 versus 100.
Push history: DebugSwift was last pushed on 20 October 2026 (28 days ago), and Umami was last pushed on 17 November 2026 (0 days ago). Open issues stand at 17 for DebugSwift (0.007 per star) and 136 for Umami (0.003 per star). Issue-health scores are 84 and 96; activity scores are 78 and 100.
Both DebugSwift and Umami are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Analytics, both DebugSwift (2,454 stars) and Umami (40,194 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: DebugSwift is open source, Umami is open source.
Umami is ahead on every scored dimension that is not level. Level dimensions: license flexibility, self-hosting. The widest gap is fork community at 40 points (60 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
Umami finishes ahead at 99.1 against DebugSwift at 78.4, a 20.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 | DebugSwift | Umami |
|---|---|---|
| GitHub stars | 2,454 | 40,194 |
| Forks | 218 | 8,567 |
| Open issues | 17 | 136 |
| Adoption | 74 | 100 |
| Activity | 78 | 100 |
| Community | 60 | 100 |
| Issue health | 84 | 96 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 78.4 | 99.1 |
A toolkit to make debugging iOS applications easier 🚀
Umami is a small web analytics product with a simple dashboard over page and event data. It is MIT-licensed and is usually chosen when a team wants a short self-hosted setup.
Umami has more GitHub stars: 40,194 versus 2,454 for DebugSwift. The gap is 37,740 stars.
Umami was pushed more recently: 17 November 2026 versus 20 October 2026 for DebugSwift. That is 28 days apart.
Yes. This catalog marks both DebugSwift and Umami as self-hostable. Confirm each project's deploy docs before you plan a migration.
DebugSwift 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. Umami 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Umami scores 99.1 and DebugSwift scores 78.4. This page calls that a decisive lead for Umami.