A
NocoDB
92.6
65,557 stars · AGPL-3.0
Self-Hosted
reactive-resume leads by 5.4 · narrow
A
92.6
65,557 stars · AGPL-3.0
B · leads
98.0
45,854 stars · MIT
NocoDB versus reactive-resume is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 92.6 for NocoDB and 98.0 for reactive-resume.
NocoDB has 65,557 GitHub stars to reactive-resume's 45,854, a gap of 19,703 (1.43×). Forks are 5,142 for NocoDB and 4,959 for reactive-resume. On the log scale used inside this pair, adoption is 100 versus 97, and the fork community is 100 versus 100.
Push history: NocoDB was last pushed on 17 November 2026 (0 days ago), and reactive-resume was last pushed on 16 November 2026 (1 day ago). Open issues stand at 526 for NocoDB (0.008 per star) and 7 for reactive-resume (0.000 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
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. reactive-resume is listed as MIT, 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 NocoDB and 96 for reactive-resume. This is a procurement signal, not legal advice.
In Self-Hosted, both NocoDB (65,557 stars) and reactive-resume (45,854 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: NocoDB is freemium, reactive-resume is open source.
The lead is split. NocoDB is furthest ahead on adoption (100 to 97), while reactive-resume is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
reactive-resume finishes ahead at 98.0 against NocoDB at 92.6, a 5.4 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 | NocoDB | reactive-resume |
|---|---|---|
| GitHub stars | 65,557 | 45,854 |
| Forks | 5,142 | 4,959 |
| Open issues | 526 | 7 |
| Adoption | 100 | 97 |
| Activity | 100 | 100 |
| Community | 100 | 100 |
| Issue health | 84 | 96 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 92.6 | 98.0 |
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.
A one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!
NocoDB has more GitHub stars: 65,557 versus 45,854 for reactive-resume. The gap is 19,703 stars.
NocoDB was pushed more recently: 17 November 2026 versus 16 November 2026 for reactive-resume. That is 1 days apart.
Yes. This catalog marks both NocoDB and reactive-resume as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. reactive-resume is listed as MIT, 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.
reactive-resume scores 98.0 and NocoDB scores 92.6. This page calls that a narrow lead for reactive-resume.