A
chartdb
84.6
23,133 stars · AGPL-3.0
Databases
orm leads by 10.1 · clear
A
84.6
23,133 stars · AGPL-3.0
B · leads
94.7
47,675 stars · Apache-2.0
chartdb versus orm is a Databases 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 84.6 for chartdb and 94.7 for orm.
orm has 47,675 GitHub stars to chartdb's 23,133, a gap of 24,542 (2.06×). Forks are 1,527 for chartdb and 2,635 for orm. On the log scale used inside this pair, adoption is 93 versus 100, and the fork community is 93 versus 100.
Push history: chartdb was last pushed on 01 November 2026 (16 days ago), and orm was last pushed on 17 November 2026 (0 days ago). Open issues stand at 155 for chartdb (0.007 per star) and 2,817 for orm (0.059 per star). Issue-health scores are 84 and 52; activity scores are 78 and 100.
chartdb 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. orm is listed as Apache-2.0, 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. License scores in this pair are 52 for chartdb and 96 for orm. This is a procurement signal, not legal advice.
In Databases, both chartdb (23,133 stars) and orm (47,675 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: chartdb is open source, orm is open source.
The lead is split. chartdb is furthest ahead on issue health (84 to 52), while orm is furthest ahead on license flexibility (96 to 52). Choose the dimension a rollout cannot compromise on.
orm finishes ahead at 94.7 against chartdb at 84.6, a 10.1 point clear 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 | chartdb | orm |
|---|---|---|
| GitHub stars | 23,133 | 47,675 |
| Forks | 1,527 | 2,635 |
| Open issues | 155 | 2,817 |
| Adoption | 93 | 100 |
| Activity | 78 | 100 |
| Community | 93 | 100 |
| Issue health | 84 | 52 |
| License | 52 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 84.6 | 94.7 |
Database diagrams editor that allows you to visualize and design your DB with a single query.
The Prisma ORM: write your application in TypeScript with human-readable queries instead of SQL. Host your database on Prisma Postgres and your app on Prisma Compute.
orm has more GitHub stars: 47,675 versus 23,133 for chartdb. The gap is 24,542 stars.
orm was pushed more recently: 17 November 2026 versus 01 November 2026 for chartdb. That is 16 days apart.
Yes. This catalog marks both chartdb and orm as self-hostable. Confirm each project's deploy docs before you plan a migration.
chartdb 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. orm is listed as Apache-2.0, 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. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
orm scores 94.7 and chartdb scores 84.6. This page calls that a clear lead for orm.