A · leads
NocoDB
92.6
65,557 stars · AGPL-3.0
Self-Hosted
NocoDB leads by 5.3 · narrow
A · leads
92.6
65,557 stars · AGPL-3.0
B
87.3
15,696 stars · AGPL-3.0
NocoDB versus TREK 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 87.3 for TREK.
NocoDB has 65,557 GitHub stars to TREK's 15,696, a gap of 49,861 (4.18×). Forks are 5,142 for NocoDB and 1,342 for TREK. On the log scale used inside this pair, adoption is 100 versus 87, and the fork community is 100 versus 84.
Push history: NocoDB was last pushed on 17 November 2026 (0 days ago), and TREK was last pushed on 17 November 2026 (0 days ago). Open issues stand at 526 for NocoDB (0.008 per star) and 19 for TREK (0.001 per star). Issue-health scores are 84 and 96; activity scores are 100 and 100.
Both NocoDB and TREK 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 NocoDB (65,557 stars) and TREK (15,696 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, TREK is open source.
The lead is split. NocoDB is furthest ahead on fork community (100 to 84), while TREK is furthest ahead on issue health (96 to 84). Choose the dimension a rollout cannot compromise on.
NocoDB finishes ahead at 92.6 against TREK at 87.3, a 5.3 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 | TREK |
|---|---|---|
| GitHub stars | 65,557 | 15,696 |
| Forks | 5,142 | 1,342 |
| Open issues | 526 | 19 |
| Adoption | 100 | 87 |
| Activity | 100 | 100 |
| Community | 100 | 84 |
| Issue health | 84 | 96 |
| License | 52 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 92.6 | 87.3 |
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.
The most complete open-source travel planner: real-time collaboration, bookings, budgets, packing lists, journals, offline PWA, SSO and an AI-ready MCP server, with planet-wide place search and routing built in.
NocoDB has more GitHub stars: 65,557 versus 15,696 for TREK. The gap is 49,861 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both NocoDB and TREK 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. TREK 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 TREK scores 87.3. This page calls that a narrow lead for NocoDB.