A · leads
PostHog
94.7
40,849 stars · MIT
Analytics
PostHog leads by 15.3 · decisive
A · leads
94.7
40,849 stars · MIT
B
79.4
4,093 stars · AGPL-3.0
PostHog versus rotki is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in Python. The composite score is 94.7 for PostHog and 79.4 for rotki.
PostHog has 40,849 GitHub stars to rotki's 4,093, a gap of 36,756 (9.98×). Forks are 3,696 for PostHog and 791 for rotki. On the log scale used inside this pair, adoption is 100 versus 78, and the fork community is 100 versus 81.
Push history: PostHog was last pushed on 17 November 2026 (0 days ago), and rotki was last pushed on 17 November 2026 (0 days ago). Open issues stand at 4,463 for PostHog (0.109 per star) and 353 for rotki (0.086 per star). Issue-health scores are 52 and 52; activity scores are 100 and 100.
PostHog 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. rotki 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 PostHog and 52 for rotki. This is a procurement signal, not legal advice.
In Analytics, both PostHog (40,849 stars) and rotki (4,093 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: PostHog is freemium, rotki is open source.
PostHog is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, self-hosting. The widest gap is license flexibility at 44 points (96 vs 52), and the tightest is self-hosting at 0 points (100 vs 100).
PostHog finishes ahead at 94.7 against rotki at 79.4, a 15.3 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 | PostHog | rotki |
|---|---|---|
| GitHub stars | 40,849 | 4,093 |
| Forks | 3,696 | 791 |
| Open issues | 4,463 | 353 |
| Adoption | 100 | 78 |
| Activity | 100 | 100 |
| Community | 100 | 81 |
| Issue health | 52 | 52 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 79.4 |
PostHog is a product-analytics suite: events, funnels, session replay, and feature flags. The core is open source and most teams choose between self-hosting and PostHog Cloud.
A portfolio tracking, analytics, accounting and management application that protects your privacy
PostHog has more GitHub stars: 40,849 versus 4,093 for rotki. The gap is 36,756 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both PostHog and rotki as self-hostable. Confirm each project's deploy docs before you plan a migration.
PostHog 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. rotki 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.
PostHog scores 94.7 and rotki scores 79.4. This page calls that a decisive lead for PostHog.