A · leads
Plausible
92.1
29,871 stars · AGPL-3.0
Analytics
Plausible leads by 25.5 · decisive
A · leads
92.1
29,871 stars · AGPL-3.0
B
66.6
1,148 stars · MIT
Plausible versus SwiftInfo is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Plausible is written mainly in Elixir; SwiftInfo is written mainly in Swift. The composite score is 92.1 for Plausible and 66.6 for SwiftInfo.
Plausible has 29,871 GitHub stars to SwiftInfo's 1,148, a gap of 28,723 (26.02×). Forks are 1,940 for Plausible and 58 for SwiftInfo. On the log scale used inside this pair, adoption is 100 versus 68, and the fork community is 100 versus 54.
Push history: Plausible was last pushed on 17 November 2026 (5 days ago), and SwiftInfo was last pushed on 18 December 2025 (339 days ago). Open issues stand at 58 for Plausible (0.002 per star) and 22 for SwiftInfo (0.019 per star). Issue-health scores are 96 and 84; activity scores are 92 and 36.
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. SwiftInfo 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. License scores in this pair are 52 for Plausible and 96 for SwiftInfo. This is a procurement signal, not legal advice.
In Analytics, both Plausible (29,871 stars) and SwiftInfo (1,148 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: Plausible is freemium, SwiftInfo is open source.
The lead is split. Plausible is furthest ahead on recent activity (92 to 36), while SwiftInfo is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
Plausible finishes ahead at 92.1 against SwiftInfo at 66.6, a 25.5 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 | Plausible | SwiftInfo |
|---|---|---|
| GitHub stars | 29,871 | 1,148 |
| Forks | 1,940 | 58 |
| Open issues | 58 | 22 |
| Adoption | 100 | 68 |
| Activity | 92 | 36 |
| Community | 100 | 54 |
| Issue health | 96 | 84 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.1 | 66.6 |
Plausible is a lightweight, cookie-less web analytics tool. The community edition can be self-hosted; the company also sells a managed service.
📊 Extract and analyze the evolution of an iOS app's code.
Plausible has more GitHub stars: 29,871 versus 1,148 for SwiftInfo. The gap is 28,723 stars.
Plausible was pushed more recently: 17 November 2026 versus 18 December 2025 for SwiftInfo. That is 334 days apart.
Yes. This catalog marks both Plausible and SwiftInfo as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. SwiftInfo 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.
Plausible scores 92.1 and SwiftInfo scores 66.6. This page calls that a decisive lead for Plausible.