A
langfuse
86.9
37,546 stars · license n/a
Analytics
Metabase leads by 2.5 · narrow
A
86.9
37,546 stars · license n/a
B · leads
89.4
50,382 stars · AGPL-3.0
langfuse versus Metabase 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; Metabase is written mainly in Clojure. The composite score is 86.9 for langfuse and 89.4 for Metabase.
Metabase has 50,382 GitHub stars to langfuse's 37,546, a gap of 12,836 (1.34×). Forks are 4,243 for langfuse and 7,016 for Metabase. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 94 versus 100.
Push history: langfuse was last pushed on 17 November 2026 (0 days ago), and Metabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 1,173 for langfuse (0.031 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 70 and 52; 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. Metabase 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. License scores in this pair are 30 for langfuse and 52 for Metabase. This is a procurement signal, not legal advice.
In Analytics, both langfuse (37,546 stars) and Metabase (50,382 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: langfuse is unpriced in this catalog, Metabase is freemium.
The lead is split. langfuse is furthest ahead on issue health (70 to 52), while Metabase is furthest ahead on license flexibility (52 to 30). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against langfuse at 86.9, a 2.5 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 | langfuse | Metabase |
|---|---|---|
| GitHub stars | 37,546 | 50,382 |
| Forks | 4,243 | 7,016 |
| Open issues | 1,173 | 4,696 |
| Adoption | 97 | 100 |
| Activity | 100 | 100 |
| Community | 94 | 100 |
| Issue health | 70 | 52 |
| License | 30 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 86.9 | 89.4 |
🪢 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.
Metabase is a business-intelligence tool that lets teams ask questions of a SQL database without writing a report from scratch. It is commonly self-hosted next to the warehouse it reads.
Metabase has more GitHub stars: 50,382 versus 37,546 for langfuse. The gap is 12,836 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both langfuse and Metabase as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. Metabase 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Metabase scores 89.4 and langfuse scores 86.9. This page calls that a narrow lead for Metabase.