A
eventql
45.7
1,176 stars · license n/a
Analytics
PostHog leads by 47.3 · decisive
A
45.7
1,176 stars · license n/a
B · leads
93.0
40,849 stars · MIT
eventql versus PostHog is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. eventql is written mainly in C++; PostHog is written mainly in Python. The composite score is 45.7 for eventql and 93.0 for PostHog.
PostHog has 40,849 GitHub stars to eventql's 1,176, a gap of 39,673 (34.74×). Forks are 104 for eventql and 3,696 for PostHog. On the log scale used inside this pair, adoption is 67 versus 100, and the fork community is 57 versus 100.
Push history: eventql was last pushed on 06 May 2017 (3487 days ago), and PostHog was last pushed on 17 November 2026 (5 days ago). Open issues stand at 113 for eventql (0.096 per star) and 4,463 for PostHog (0.109 per star). Issue-health scores are 52 and 52; activity scores are 16 and 92.
eventql 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 eventql 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). eventql is not (1,176 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: eventql is unpriced in this catalog, PostHog is freemium.
PostHog is ahead on every scored dimension that is not level. Level dimensions: issue health. The widest gap is recent activity at 76 points (16 vs 92), and the tightest is issue health at 0 points (52 vs 52).
PostHog finishes ahead at 93.0 against eventql at 45.7, a 47.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 | eventql | PostHog |
|---|---|---|
| GitHub stars | 1,176 | 40,849 |
| Forks | 104 | 3,696 |
| Open issues | 113 | 4,463 |
| Adoption | 67 | 100 |
| Activity | 16 | 92 |
| Community | 57 | 100 |
| Issue health | 52 | 52 |
| License | 30 | 96 |
| Self-hosting | 35 | 100 |
| Composite | 45.7 | 93.0 |
Distributed "massively parallel" SQL query engine
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 1,176 for eventql. The gap is 39,673 stars.
PostHog was pushed more recently: 17 November 2026 versus 06 May 2017 for eventql. That is 3482 days apart.
Only PostHog is marked self-hostable. eventql is not.
eventql 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 93.0 and eventql scores 45.7. This page calls that a decisive lead for PostHog.