A
metube
86.9
15,290 stars · AGPL-3.0
Self-Hosted
NocoDB leads by 5.7 · narrow
A
86.9
15,290 stars · AGPL-3.0
B · leads
92.6
65,557 stars · AGPL-3.0
metube versus NocoDB is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. metube is written mainly in Python; NocoDB is written mainly in TypeScript. The composite score is 86.9 for metube and 92.6 for NocoDB.
NocoDB has 65,557 GitHub stars to metube's 15,290, a gap of 50,267 (4.29×). Forks are 1,140 for metube and 5,142 for NocoDB. On the log scale used inside this pair, adoption is 87 versus 100, and the fork community is 82 versus 100.
Push history: metube was last pushed on 14 November 2026 (2 days ago), and NocoDB was last pushed on 17 November 2026 (0 days ago). Open issues stand at 5 for metube (0.000 per star) and 526 for NocoDB (0.008 per star). Issue-health scores are 96 and 84; activity scores are 100 and 100.
Both metube and NocoDB 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 Self-Hosted, both metube (15,290 stars) and NocoDB (65,557 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: metube is open source, NocoDB is freemium.
The lead is split. metube is furthest ahead on issue health (96 to 84), while NocoDB is furthest ahead on fork community (100 to 82). Choose the dimension a rollout cannot compromise on.
NocoDB finishes ahead at 92.6 against metube at 86.9, a 5.7 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 | metube | NocoDB |
|---|---|---|
| GitHub stars | 15,290 | 65,557 |
| Forks | 1,140 | 5,142 |
| Open issues | 5 | 526 |
| Adoption | 87 | 100 |
| Activity | 100 | 100 |
| Community | 82 | 100 |
| Issue health | 96 | 84 |
| License | 52 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 86.9 | 92.6 |
Self-hosted video downloader for YouTube and other sites (web UI for yt-dlp)
NocoDB turns a relational database into a spreadsheet-style workspace with views, forms, and an API. It is used when the system of record should stay in Postgres or MySQL.
NocoDB has more GitHub stars: 65,557 versus 15,290 for metube. The gap is 50,267 stars.
NocoDB was pushed more recently: 17 November 2026 versus 14 November 2026 for metube. That is 2 days apart.
Yes. This catalog marks both metube and NocoDB as self-hostable. Confirm each project's deploy docs before you plan a migration.
metube 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. NocoDB 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.
NocoDB scores 92.6 and metube scores 86.9. This page calls that a narrow lead for NocoDB.