Skip to content
DevUtils Online

Self-Hosted

NocoDB vs openGym

NocoDB leads by 4.2 · narrow

A · leads

NocoDB

92.6

65,557 stars · AGPL-3.0

B

openGym

88.4

22,439 stars · AGPL-3.0

NocoDB versus openGym is a Self-Hosted comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. NocoDB is written mainly in TypeScript; openGym is written mainly in JavaScript. The composite score is 92.6 for NocoDB and 88.4 for openGym.

NocoDB has 65,557 GitHub stars to openGym's 22,439, a gap of 43,118 (2.92×). Forks are 5,142 for NocoDB and 2,982 for openGym. On the log scale used inside this pair, adoption is 100 versus 90, and the fork community is 100 versus 94.

Push history: NocoDB was last pushed on 17 November 2026 (0 days ago), and openGym was last pushed on 17 November 2026 (0 days ago). Open issues stand at 526 for NocoDB (0.008 per star) and 324 for openGym (0.014 per star). Issue-health scores are 84 and 84; activity scores are 100 and 100.

Both NocoDB and openGym 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 openGym (22,439 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, openGym is open source.

NocoDB is ahead on every scored dimension that is not level. Level dimensions: recent activity, issue health, license flexibility, self-hosting. The widest gap is adoption at 10 points (100 vs 90), and the tightest is self-hosting at 0 points (100 vs 100).

NocoDB finishes ahead at 92.6 against openGym at 88.4, a 4.2 point narrow margin under the published weights.

Scores are computed inside this pair only. Method and weights.

Where they separate

The numbers

Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.

NocoDB versus openGym metrics
Signal NocoDB openGym
GitHub stars 65,557 22,439
Forks 5,142 2,982
Open issues 526 324
Adoption 100 90
Activity 100 100
Community 100 94
Issue health 84 84
License 52 52
Self-hosting 100 100
Composite 92.6 88.4

NocoDB

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.

Project site · GitHub · Full profile

openGym

Open-source gym & body-weight tracker, now in the App Store (iPhone + Apple Watch) and as an Android APK. Plan routines, log workouts, see which muscles are trained, import from Strong/Hevy/FitNotes. Self-host it or use it on the phone alone.

Project site · GitHub · Full profile

Questions this page answers

Which has more GitHub stars, NocoDB or openGym?

NocoDB has more GitHub stars: 65,557 versus 22,439 for openGym. The gap is 43,118 stars.

Which was updated more recently, NocoDB or openGym?

Both were last pushed on 17 November 2026.

Can I self-host both NocoDB and openGym?

Yes. This catalog marks both NocoDB and openGym as self-hostable. Confirm each project's deploy docs before you plan a migration.

Which license is easier to embed in a commercial product, NocoDB or openGym?

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. openGym 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.

Who wins the NocoDB vs openGym score?

NocoDB scores 92.6 and openGym scores 88.4. This page calls that a narrow lead for NocoDB.

Related comparisons