A
llama-gpt
70.7
10,923 stars · MIT
Self-Hosted
NocoDB leads by 21.9 · decisive
A
70.7
10,923 stars · MIT
B · leads
92.6
65,557 stars · AGPL-3.0
llama-gpt versus NocoDB 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 70.7 for llama-gpt and 92.6 for NocoDB.
NocoDB has 65,557 GitHub stars to llama-gpt's 10,923, a gap of 54,634 (6.00×). Forks are 701 for llama-gpt and 5,142 for NocoDB. On the log scale used inside this pair, adoption is 84 versus 100, and the fork community is 77 versus 100.
Push history: llama-gpt was last pushed on 23 April 2024 (938 days ago), and NocoDB was last pushed on 17 November 2026 (0 days ago). Open issues stand at 98 for llama-gpt (0.009 per star) and 526 for NocoDB (0.008 per star). Issue-health scores are 84 and 84; activity scores are 16 and 100.
llama-gpt 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 llama-gpt and 52 for NocoDB. This is a procurement signal, not legal advice.
In Self-Hosted, both llama-gpt (10,923 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: llama-gpt is open source, NocoDB is freemium.
The lead is split. llama-gpt is furthest ahead on license flexibility (96 to 52), while NocoDB is furthest ahead on recent activity (100 to 16). Choose the dimension a rollout cannot compromise on.
NocoDB finishes ahead at 92.6 against llama-gpt at 70.7, a 21.9 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 | llama-gpt | NocoDB |
|---|---|---|
| GitHub stars | 10,923 | 65,557 |
| Forks | 701 | 5,142 |
| Open issues | 98 | 526 |
| Adoption | 84 | 100 |
| Activity | 16 | 100 |
| Community | 77 | 100 |
| Issue health | 84 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 70.7 | 92.6 |
A self-hosted, offline, ChatGPT-like chatbot. Powered by Llama 2. 100% private, with no data leaving your device. New: Code Llama support!
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 10,923 for llama-gpt. The gap is 54,634 stars.
NocoDB was pushed more recently: 17 November 2026 versus 23 April 2024 for llama-gpt. That is 938 days apart.
Yes. This catalog marks both llama-gpt and NocoDB as self-hostable. Confirm each project's deploy docs before you plan a migration.
llama-gpt 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 llama-gpt scores 70.7. This page calls that a decisive lead for NocoDB.