A
bore
76.0
11,615 stars · MIT
Self-Hosted
NocoDB leads by 16.6 · decisive
A
76.0
11,615 stars · MIT
B · leads
92.6
65,557 stars · AGPL-3.0
bore versus NocoDB is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. bore is written mainly in Rust; NocoDB is written mainly in TypeScript. The composite score is 76.0 for bore and 92.6 for NocoDB.
NocoDB has 65,557 GitHub stars to bore's 11,615, a gap of 53,942 (5.64×). Forks are 531 for bore and 5,142 for NocoDB. On the log scale used inside this pair, adoption is 84 versus 100, and the fork community is 74 versus 100.
Push history: bore was last pushed on 04 February 2026 (286 days ago), and NocoDB was last pushed on 17 November 2026 (0 days ago). Open issues stand at 19 for bore (0.002 per star) and 526 for NocoDB (0.008 per star). Issue-health scores are 96 and 84; activity scores are 36 and 100.
bore 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. 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. License scores in this pair are 96 for bore and 52 for NocoDB. This is a procurement signal, not legal advice.
In Self-Hosted, both bore (11,615 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: bore is open source, NocoDB is freemium.
The lead is split. bore is furthest ahead on license flexibility (96 to 52), while NocoDB is furthest ahead on recent activity (100 to 36). Choose the dimension a rollout cannot compromise on.
NocoDB finishes ahead at 92.6 against bore at 76.0, a 16.6 point decisive 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 | bore | NocoDB |
|---|---|---|
| GitHub stars | 11,615 | 65,557 |
| Forks | 531 | 5,142 |
| Open issues | 19 | 526 |
| Adoption | 84 | 100 |
| Activity | 36 | 100 |
| Community | 74 | 100 |
| Issue health | 96 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 76.0 | 92.6 |
🕳 bore is a simple CLI tool for making tunnels to localhost
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 11,615 for bore. The gap is 53,942 stars.
NocoDB was pushed more recently: 17 November 2026 versus 04 February 2026 for bore. That is 286 days apart.
Yes. This catalog marks both bore and NocoDB as self-hostable. Confirm each project's deploy docs before you plan a migration.
bore 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. 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 bore scores 76.0. This page calls that a decisive lead for NocoDB.