issue-statusvsnocodb
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| issue-status | nocodb | |
|---|---|---|
| Score | 47/100 | 81/100 |
| Rank in category | #31 of 51 in Monitoring & observability | #1 of 4 in No-code Platforms |
| GitHub stars | 429 | 65 370 |
| Stars, last 30 days | — | +316 |
| Stable releases, 12 months | 0 | 15 |
| Latest release | — | 2026.10.0 · 23 Oct 2026 |
| Setup | Easy | Moderate |
| Official Docker image | No | Yes |
| License | MIT | Other |
| Main language | Typescript | Typescript |
Which one should you pick?
nocodb scores 81/100 against 47/100 for issue-status, so it is the safer default.
nocodb ships more often: 15 stable releases in the past year, against 0 for issue-status.
If you want the quickest setup, issue-status is easier to run; nocodb needs more configuration.
nocodb is growing faster right now (+316 stars in 30 days).
issue-status details →nocodb details →
Swap a project
Keep issue-status, compare it with
Keep nocodb, compare it with