A
openobserve
92.6
23,090 stars · AGPL-3.0
Analytics
partytown leads by 1.1 · narrow
A
92.6
23,090 stars · AGPL-3.0
B · leads
93.7
13,817 stars · MIT
openobserve versus partytown 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 TypeScript. The composite score is 92.6 for openobserve and 93.7 for partytown.
openobserve has 23,090 GitHub stars to partytown's 13,817, a gap of 9,273 (1.67×). Forks are 1,203 for openobserve and 460 for partytown. On the log scale used inside this pair, adoption is 100 versus 95, and the fork community is 100 versus 86.
Push history: openobserve was last pushed on 17 November 2026 (0 days ago), and partytown was last pushed on 09 November 2026 (7 days ago). Open issues stand at 226 for openobserve (0.010 per star) and 1 for partytown (0.000 per star). Issue-health scores are 84 and 96; activity scores are 100 and 92.
openobserve is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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. License scores in this pair are 52 for openobserve and 96 for partytown. This is a procurement signal, not legal advice.
In Analytics, both openobserve (23,090 stars) and partytown (13,817 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: openobserve is open source, partytown is open source.
The lead is split. openobserve is furthest ahead on fork community (100 to 86), while partytown is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
partytown finishes ahead at 93.7 against openobserve at 92.6, a 1.1 point narrow 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 | openobserve | partytown |
|---|---|---|
| GitHub stars | 23,090 | 13,817 |
| Forks | 1,203 | 460 |
| Open issues | 226 | 1 |
| Adoption | 100 | 95 |
| Activity | 100 | 92 |
| Community | 100 | 86 |
| Issue health | 84 | 96 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.6 | 93.7 |
Open source observability platform for logs, metrics, traces, RUM (web, android, ios), Session replay, pipelines, SLO and LLM observability. A sophisticated, simple and highly performant alternative to Datadog, Splunk, and Elasticsearch with 140x lower storage costs and single binary deployment.
Relocate resource intensive third-party scripts off of the main thread and into a web worker. 🎉
openobserve has more GitHub stars: 23,090 versus 13,817 for partytown. The gap is 9,273 stars.
openobserve was pushed more recently: 17 November 2026 versus 09 November 2026 for partytown. That is 7 days apart.
Yes. This catalog marks both openobserve and partytown as self-hostable. Confirm each project's deploy docs before you plan a migration.
openobserve is listed as AGPL-3.0, which this catalog treats as a network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
partytown scores 93.7 and openobserve scores 92.6. This page calls that a narrow lead for partytown.