A · leads
langfuse
88.6
37,546 stars · license n/a
Analytics
langfuse leads by 7.4 · clear
A · leads
88.6
37,546 stars · license n/a
B
81.2
23,865 stars · license n/a
langfuse versus timescaledb is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. langfuse is written mainly in TypeScript; timescaledb is written mainly in C. The composite score is 88.6 for langfuse and 81.2 for timescaledb.
langfuse has 37,546 GitHub stars to timescaledb's 23,865, a gap of 13,681 (1.57×). Forks are 4,243 for langfuse and 1,188 for timescaledb. On the log scale used inside this pair, adoption is 100 versus 96, and the fork community is 100 versus 85.
Push history: langfuse was last pushed on 17 November 2026 (0 days ago), and timescaledb was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,173 for langfuse (0.031 per star) and 476 for timescaledb (0.020 per star). Issue-health scores are 70 and 84; activity scores are 100 and 100.
langfuse 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. 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 30 for langfuse and 30 for timescaledb. This is a procurement signal, not legal advice.
Only langfuse is marked self-hostable here (37,546 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: langfuse is unpriced in this catalog, timescaledb is unpriced in this catalog.
The lead is split. langfuse is furthest ahead on self-hosting (100 to 35), while timescaledb is furthest ahead on issue health (84 to 70). Choose the dimension a rollout cannot compromise on.
langfuse finishes ahead at 88.6 against timescaledb at 81.2, a 7.4 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 | langfuse | timescaledb |
|---|---|---|
| GitHub stars | 37,546 | 23,865 |
| Forks | 4,243 | 1,188 |
| Open issues | 1,173 | 476 |
| Adoption | 100 | 96 |
| Activity | 100 | 100 |
| Community | 100 | 85 |
| Issue health | 70 | 84 |
| License | 30 | 30 |
| Self-hosting | 100 | 35 |
| Composite | 88.6 | 81.2 |
🪢 Open source AI engineering platform: AI Gateway, agent observability, evals, and prompt/skill management, built on OpenTelemetry. One open platform for every AI call and every agent. Self-host or use Langfuse Cloud.
A time-series database for high-performance real-time analytics packaged as a Postgres extension
langfuse has more GitHub stars: 37,546 versus 23,865 for timescaledb. The gap is 13,681 stars.
Both were last pushed on 17 November 2026.
Only langfuse is marked self-hostable. timescaledb is not.
langfuse 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. 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.
langfuse scores 88.6 and timescaledb scores 81.2. This page calls that a clear lead for langfuse.