A
lotus
82.4
1,844 stars · MIT
Analytics
PostHog leads by 12.3 · clear
A
82.4
1,844 stars · MIT
B · leads
94.7
40,849 stars · MIT
lotus versus PostHog 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 82.4 for lotus and 94.7 for PostHog.
PostHog has 40,849 GitHub stars to lotus's 1,844, a gap of 39,005 (22.15×). Forks are 138 for lotus and 3,696 for PostHog. On the log scale used inside this pair, adoption is 71 versus 100, and the fork community is 60 versus 100.
Push history: lotus was last pushed on 17 November 2026 (0 days ago), and PostHog was last pushed on 17 November 2026 (0 days ago). Open issues stand at 36 for lotus (0.020 per star) and 4,463 for PostHog (0.109 per star). Issue-health scores are 84 and 52; activity scores are 100 and 100.
Both lotus and PostHog are listed as MIT. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Analytics, both lotus (1,844 stars) and PostHog (40,849 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: lotus is open source, PostHog is freemium.
The lead is split. lotus is furthest ahead on issue health (84 to 52), while PostHog is furthest ahead on fork community (100 to 60). Choose the dimension a rollout cannot compromise on.
PostHog finishes ahead at 94.7 against lotus at 82.4, a 12.3 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 | lotus | PostHog |
|---|---|---|
| GitHub stars | 1,844 | 40,849 |
| Forks | 138 | 3,696 |
| Open issues | 36 | 4,463 |
| Adoption | 71 | 100 |
| Activity | 100 | 100 |
| Community | 60 | 100 |
| Issue health | 84 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 82.4 | 94.7 |
Open Source Pricing & Packaging Infrastructure
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,844 for lotus. The gap is 39,005 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both lotus and PostHog as self-hostable. Confirm each project's deploy docs before you plan a migration.
lotus 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. 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 lotus scores 82.4. This page calls that a clear lead for PostHog.