A
maestro
83.2
3,852 stars · Apache-2.0
Analytics
Metabase leads by 6.2 · narrow
A
83.2
3,852 stars · Apache-2.0
B · leads
89.4
50,382 stars · AGPL-3.0
maestro versus Metabase is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. maestro is written mainly in Java; Metabase is written mainly in Clojure. The composite score is 83.2 for maestro and 89.4 for Metabase.
Metabase has 50,382 GitHub stars to maestro's 3,852, a gap of 46,530 (13.08×). Forks are 311 for maestro and 7,016 for Metabase. On the log scale used inside this pair, adoption is 76 versus 100, and the fork community is 65 versus 100.
Push history: maestro was last pushed on 06 November 2026 (10 days ago), and Metabase was last pushed on 17 November 2026 (0 days ago). Open issues stand at 37 for maestro (0.010 per star) and 4,696 for Metabase (0.093 per star). Issue-health scores are 84 and 52; activity scores are 92 and 100.
maestro 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. 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 96 for maestro and 52 for Metabase. This is a procurement signal, not legal advice.
In Analytics, both maestro (3,852 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: maestro is open source, Metabase is freemium.
The lead is split. maestro is furthest ahead on license flexibility (96 to 52), while Metabase is furthest ahead on fork community (100 to 65). Choose the dimension a rollout cannot compromise on.
Metabase finishes ahead at 89.4 against maestro at 83.2, a 6.2 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 | maestro | Metabase |
|---|---|---|
| GitHub stars | 3,852 | 50,382 |
| Forks | 311 | 7,016 |
| Open issues | 37 | 4,696 |
| Adoption | 76 | 100 |
| Activity | 92 | 100 |
| Community | 65 | 100 |
| Issue health | 84 | 52 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 83.2 | 89.4 |
Maestro: Netflix’s Workflow Orchestrator
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 3,852 for maestro. The gap is 46,530 stars.
Metabase was pushed more recently: 17 November 2026 versus 06 November 2026 for maestro. That is 10 days apart.
Yes. This catalog marks both maestro and Metabase as self-hostable. Confirm each project's deploy docs before you plan a migration.
maestro 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. 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 maestro scores 83.2. This page calls that a narrow lead for Metabase.