A · leads
Metabase
89.4
50,382 stars · AGPL-3.0
Analytics
Metabase leads by 7.2 · clear
A · leads
89.4
50,382 stars · AGPL-3.0
B
82.2
3,123 stars · Apache-2.0
Metabase versus tianji is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Metabase is written mainly in Clojure; tianji is written mainly in TypeScript. The composite score is 89.4 for Metabase and 82.2 for tianji.
Metabase has 50,382 GitHub stars to tianji's 3,123, a gap of 47,259 (16.13×). Forks are 7,016 for Metabase and 200 for tianji. On the log scale used inside this pair, adoption is 100 versus 74, and the fork community is 100 versus 60.
Push history: Metabase was last pushed on 17 November 2026 (0 days ago), and tianji was last pushed on 16 November 2026 (1 day ago). Open issues stand at 4,696 for Metabase (0.093 per star) and 145 for tianji (0.046 per star). Issue-health scores are 52 and 70; activity scores are 100 and 100.
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. tianji is listed as Apache-2.0, 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 Metabase and 96 for tianji. This is a procurement signal, not legal advice.
In Analytics, both Metabase (50,382 stars) and tianji (3,123 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: Metabase is freemium, tianji is open source.
The lead is split. Metabase is furthest ahead on fork community (100 to 60), while tianji is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against tianji at 82.2, a 7.2 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 | Metabase | tianji |
|---|---|---|
| GitHub stars | 50,382 | 3,123 |
| Forks | 7,016 | 200 |
| Open issues | 4,696 | 145 |
| Adoption | 100 | 74 |
| Activity | 100 | 100 |
| Community | 100 | 60 |
| Issue health | 52 | 70 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 89.4 | 82.2 |
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.
Tianji: Insight into everything, Website Analytics + Uptime Monitor + Server Status. not only another GA alternatives
Metabase has more GitHub stars: 50,382 versus 3,123 for tianji. The gap is 47,259 stars.
Metabase was pushed more recently: 17 November 2026 versus 16 November 2026 for tianji. That is 1 days apart.
Yes. This catalog marks both Metabase and tianji as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. tianji is listed as Apache-2.0, 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.
Metabase scores 89.4 and tianji scores 82.2. This page calls that a clear lead for Metabase.