A
goatcounter
65.2
6,171 stars · license n/a
Analytics
PostHog leads by 29.5 · decisive
A
65.2
6,171 stars · license n/a
B · leads
94.7
40,849 stars · MIT
goatcounter versus PostHog is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. goatcounter is written mainly in Go; PostHog is written mainly in Python. The composite score is 65.2 for goatcounter and 94.7 for PostHog.
PostHog has 40,849 GitHub stars to goatcounter's 6,171, a gap of 34,678 (6.62×). Forks are 288 for goatcounter and 3,696 for PostHog. On the log scale used inside this pair, adoption is 82 versus 100, and the fork community is 69 versus 100.
Push history: goatcounter was last pushed on 27 September 2026 (50 days ago), and PostHog was last pushed on 17 November 2026 (0 days ago). Open issues stand at 60 for goatcounter (0.010 per star) and 4,463 for PostHog (0.109 per star). Issue-health scores are 84 and 52; activity scores are 58 and 100.
goatcounter is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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. License scores in this pair are 30 for goatcounter and 96 for PostHog. This is a procurement signal, not legal advice.
Only PostHog is marked self-hostable here (40,849 stars, deploy score 100). goatcounter is not (6,171 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: goatcounter is unpriced in this catalog, PostHog is freemium.
The lead is split. goatcounter is furthest ahead on issue health (84 to 52), while PostHog is furthest ahead on license flexibility (96 to 30). Choose the dimension a rollout cannot compromise on.
PostHog finishes ahead at 94.7 against goatcounter at 65.2, a 29.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 | goatcounter | PostHog |
|---|---|---|
| GitHub stars | 6,171 | 40,849 |
| Forks | 288 | 3,696 |
| Open issues | 60 | 4,463 |
| Adoption | 82 | 100 |
| Activity | 58 | 100 |
| Community | 69 | 100 |
| Issue health | 84 | 52 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 65.2 | 94.7 |
Easy web analytics. No tracking of personal data.
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.
PostHog has more GitHub stars: 40,849 versus 6,171 for goatcounter. The gap is 34,678 stars.
PostHog was pushed more recently: 17 November 2026 versus 27 September 2026 for goatcounter. That is 50 days apart.
Only PostHog is marked self-hostable. goatcounter is not.
goatcounter is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
PostHog scores 94.7 and goatcounter scores 65.2. This page calls that a decisive lead for PostHog.