A · leads
partytown
93.6
13,817 stars · MIT
Analytics
partytown leads by 8.8 · clear
A · leads
93.6
13,817 stars · MIT
B
84.8
23,865 stars · license n/a
partytown versus timescaledb is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. partytown is written mainly in TypeScript; timescaledb is written mainly in C. The composite score is 93.6 for partytown and 84.8 for timescaledb.
timescaledb has 23,865 GitHub stars to partytown's 13,817, a gap of 10,048 (1.73×). Forks are 460 for partytown and 1,188 for timescaledb. On the log scale used inside this pair, adoption is 95 versus 100, and the fork community is 87 versus 100.
Push history: partytown was last pushed on 09 November 2026 (7 days ago), and timescaledb was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1 for partytown (0.000 per star) and 476 for timescaledb (0.020 per star). Issue-health scores are 96 and 84; activity scores are 92 and 100.
partytown 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. timescaledb 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. License scores in this pair are 96 for partytown and 30 for timescaledb. This is a procurement signal, not legal advice.
Only partytown is marked self-hostable here (13,817 stars, deploy score 100). timescaledb is not (23,865 stars, deploy score 35). For a team with a data-residency rule, that gap can outweigh a star-count lead. Pricing labels on file: partytown is open source, timescaledb is unpriced in this catalog.
The lead is split. partytown is furthest ahead on license flexibility (96 to 30), while timescaledb is furthest ahead on fork community (100 to 87). Choose the dimension a rollout cannot compromise on.
partytown finishes ahead at 93.6 against timescaledb at 84.8, a 8.8 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 | partytown | timescaledb |
|---|---|---|
| GitHub stars | 13,817 | 23,865 |
| Forks | 460 | 1,188 |
| Open issues | 1 | 476 |
| Adoption | 95 | 100 |
| Activity | 92 | 100 |
| Community | 87 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 93.6 | 84.8 |
Relocate resource intensive third-party scripts off of the main thread and into a web worker. 🎉
A time-series database for high-performance real-time analytics packaged as a Postgres extension
timescaledb has more GitHub stars: 23,865 versus 13,817 for partytown. The gap is 10,048 stars.
timescaledb was pushed more recently: 17 November 2026 versus 09 November 2026 for partytown. That is 7 days apart.
Only partytown is marked self-hostable. timescaledb is not.
partytown 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. timescaledb 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
partytown scores 93.6 and timescaledb scores 84.8. This page calls that a clear lead for partytown.