A · leads
PostHog
94.7
40,849 stars · MIT
Analytics
PostHog leads by 12.9 · clear
A · leads
94.7
40,849 stars · MIT
B
81.8
2,389 stars · Apache-2.0
PostHog versus quary is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. PostHog is written mainly in Python; quary is written mainly in Rust. The composite score is 94.7 for PostHog and 81.8 for quary.
PostHog has 40,849 GitHub stars to quary's 2,389, a gap of 38,460 (17.10×). Forks are 3,696 for PostHog and 58 for quary. On the log scale used inside this pair, adoption is 100 versus 73, and the fork community is 100 versus 50.
Push history: PostHog was last pushed on 17 November 2026 (0 days ago), and quary was last pushed on 16 November 2026 (1 day ago). Open issues stand at 4,463 for PostHog (0.109 per star) and 45 for quary (0.019 per star). Issue-health scores are 52 and 84; 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. quary is listed as Apache-2.0, 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 96 for PostHog and 96 for quary. This is a procurement signal, not legal advice.
In Analytics, both PostHog (40,849 stars) and quary (2,389 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, quary is open source.
The lead is split. PostHog is furthest ahead on fork community (100 to 50), while quary is furthest ahead on issue health (84 to 52). Choose the dimension a rollout cannot compromise on.
PostHog finishes ahead at 94.7 against quary at 81.8, a 12.9 point clear 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 | quary |
|---|---|---|
| GitHub stars | 40,849 | 2,389 |
| Forks | 3,696 | 58 |
| Open issues | 4,463 | 45 |
| Adoption | 100 | 73 |
| Activity | 100 | 100 |
| Community | 100 | 50 |
| Issue health | 52 | 84 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 81.8 |
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.
Open-source BI for engineers
PostHog has more GitHub stars: 40,849 versus 2,389 for quary. The gap is 38,460 stars.
PostHog was pushed more recently: 17 November 2026 versus 16 November 2026 for quary. That is 1 days apart.
Yes. This catalog marks both PostHog and quary 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. quary is listed as Apache-2.0, 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 quary scores 81.8. This page calls that a clear lead for PostHog.