Skip to content
DevUtils Online

Analytics

Metabase vs Sink

Metabase leads by 6.9 · narrow

A · leads

Metabase

89.4

50,382 stars · AGPL-3.0

B

Sink

82.5

7,285 stars · AGPL-3.0

Metabase versus Sink 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; Sink is written mainly in TypeScript. The composite score is 89.4 for Metabase and 82.5 for Sink.

Metabase has 50,382 GitHub stars to Sink's 7,285, a gap of 43,097 (6.92×). Forks are 7,016 for Metabase and 5,404 for Sink. On the log scale used inside this pair, adoption is 100 versus 82, and the fork community is 100 versus 97.

Push history: Metabase was last pushed on 17 November 2026 (0 days ago), and Sink was last pushed on 27 October 2026 (21 days ago). Open issues stand at 4,696 for Metabase (0.093 per star) and 34 for Sink (0.005 per star). Issue-health scores are 52 and 96; activity scores are 100 and 78.

Both Metabase and Sink are listed as AGPL-3.0. A network copyleft grant. Letting users interact with a modified copy over a network can trigger a duty to offer them the corresponding source. The license score is therefore level at 52 versus 52, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.

In Analytics, both Metabase (50,382 stars) and Sink (7,285 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, Sink is open source.

The lead is split. Metabase is furthest ahead on recent activity (100 to 78), while Sink is furthest ahead on issue health (96 to 52). Choose the dimension a rollout cannot compromise on.

Metabase finishes ahead at 89.4 against Sink at 82.5, a 6.9 point narrow margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

Metabase versus Sink metrics
Signal Metabase Sink
GitHub stars 50,382 7,285
Forks 7,016 5,404
Open issues 4,696 34
Adoption 100 82
Activity 100 78
Community 100 97
Issue health 52 96
License 52 52
Self-hosting 100 100
Composite 89.4 82.5

Metabase

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.

Project site · GitHub · Full profile

Sink

⚡ A Simple, Speedy, Secure, and Serverless Link Shortener with Analytics, Running Entirely on Cloudflare.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, Metabase or Sink?

Metabase has more GitHub stars: 50,382 versus 7,285 for Sink. The gap is 43,097 stars.

Which was updated more recently, Metabase or Sink?

Metabase was pushed more recently: 17 November 2026 versus 27 October 2026 for Sink. That is 21 days apart.

Can I self-host both Metabase and Sink?

Yes. This catalog marks both Metabase and Sink as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, Metabase or Sink?

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. Sink 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.

Who wins the Metabase vs Sink score?

Metabase scores 89.4 and Sink scores 82.5. This page calls that a narrow lead for Metabase.

Related comparisons