A
duckdb-wasm
80.7
2,172 stars · MIT
Analytics
PostHog leads by 14.0 · clear
A
80.7
2,172 stars · MIT
B · leads
94.7
40,849 stars · MIT
duckdb-wasm versus PostHog is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. duckdb-wasm is written mainly in TypeScript; PostHog is written mainly in Python. The composite score is 80.7 for duckdb-wasm and 94.7 for PostHog.
PostHog has 40,849 GitHub stars to duckdb-wasm's 2,172, a gap of 38,677 (18.81×). Forks are 244 for duckdb-wasm and 3,696 for PostHog. On the log scale used inside this pair, adoption is 72 versus 100, and the fork community is 67 versus 100.
Push history: duckdb-wasm was last pushed on 16 November 2026 (1 day ago), and PostHog was last pushed on 17 November 2026 (0 days ago). Open issues stand at 218 for duckdb-wasm (0.100 per star) and 4,463 for PostHog (0.109 per star). Issue-health scores are 52 and 52; activity scores are 100 and 100.
Both duckdb-wasm 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 duckdb-wasm (2,172 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: duckdb-wasm is open source, PostHog is freemium.
PostHog is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is fork community at 33 points (67 vs 100), and the tightest is self-hosting at 0 points (100 vs 100).
PostHog finishes ahead at 94.7 against duckdb-wasm at 80.7, a 14.0 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 | duckdb-wasm | PostHog |
|---|---|---|
| GitHub stars | 2,172 | 40,849 |
| Forks | 244 | 3,696 |
| Open issues | 218 | 4,463 |
| Adoption | 72 | 100 |
| Activity | 100 | 100 |
| Community | 67 | 100 |
| Issue health | 52 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 80.7 | 94.7 |
WebAssembly version of DuckDB
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 2,172 for duckdb-wasm. The gap is 38,677 stars.
PostHog was pushed more recently: 17 November 2026 versus 16 November 2026 for duckdb-wasm. That is 1 days apart.
Yes. This catalog marks both duckdb-wasm and PostHog as self-hostable. Confirm each project's deploy docs before you plan a migration.
duckdb-wasm 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 duckdb-wasm scores 80.7. This page calls that a clear lead for PostHog.