A · leads
orm
93.7
47,675 stars · Apache-2.0
Databases
orm leads by 3.1 · narrow
A · leads
93.7
47,675 stars · Apache-2.0
B
90.6
25,194 stars · AGPL-3.0
orm versus TDengine is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. orm is written mainly in TypeScript; TDengine is written mainly in C. The composite score is 93.7 for orm and 90.6 for TDengine.
orm has 47,675 GitHub stars to TDengine's 25,194, a gap of 22,481 (1.89×). Forks are 2,635 for orm and 5,011 for TDengine. On the log scale used inside this pair, adoption is 100 versus 94, and the fork community is 92 versus 100.
Push history: orm was last pushed on 17 November 2026 (0 days ago), and TDengine was last pushed on 15 November 2026 (2 days ago). Open issues stand at 2,817 for orm (0.059 per star) and 454 for TDengine (0.018 per star). Issue-health scores are 52 and 84; activity scores are 100 and 100.
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. TDengine 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 orm and 52 for TDengine. This is a procurement signal, not legal advice.
In Databases, both orm (47,675 stars) and TDengine (25,194 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: orm is open source, TDengine is open source.
The lead is split. orm is furthest ahead on license flexibility (96 to 52), while TDengine is furthest ahead on issue health (84 to 52). Choose the dimension a rollout cannot compromise on.
orm finishes ahead at 93.7 against TDengine at 90.6, a 3.1 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 | orm | TDengine |
|---|---|---|
| GitHub stars | 47,675 | 25,194 |
| Forks | 2,635 | 5,011 |
| Open issues | 2,817 | 454 |
| Adoption | 100 | 94 |
| Activity | 100 | 100 |
| Community | 92 | 100 |
| Issue health | 52 | 84 |
| License | 96 | 52 |
| Self-hosting | 100 | 100 |
| Composite | 93.7 | 90.6 |
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.
High-performance, scalable time-series database designed for Industrial IoT (IIoT) scenarios
orm has more GitHub stars: 47,675 versus 25,194 for TDengine. The gap is 22,481 stars.
orm was pushed more recently: 17 November 2026 versus 15 November 2026 for TDengine. That is 2 days apart.
Yes. This catalog marks both orm and TDengine as self-hostable. Confirm each project's deploy docs before you plan a migration.
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. TDengine 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.
orm scores 93.7 and TDengine scores 90.6. This page calls that a narrow lead for orm.