A · level
influxdb
93.4
31,816 stars · Apache-2.0
Databases
Too close to call · 93.4 to 94.1
A · level
93.4
31,816 stars · Apache-2.0
B · level
94.1
47,675 stars · Apache-2.0
influxdb versus orm is a Databases comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. influxdb is written mainly in Rust; orm is written mainly in TypeScript. The composite score is 93.4 for influxdb and 94.1 for orm.
orm has 47,675 GitHub stars to influxdb's 31,816, a gap of 15,859 (1.50×). Forks are 3,826 for influxdb and 2,635 for orm. On the log scale used inside this pair, adoption is 96 versus 100, and the fork community is 100 versus 96.
Push history: influxdb was last pushed on 17 November 2026 (0 days ago), and orm was last pushed on 17 November 2026 (0 days ago). Open issues stand at 2,175 for influxdb (0.068 per star) and 2,817 for orm (0.059 per star). Issue-health scores are 52 and 52; activity scores are 100 and 100.
Both influxdb and orm are listed as Apache-2.0. 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. The license score is therefore level at 96 versus 96, and the decision moves to adoption, activity, and hosting. This is a procurement signal, not legal advice.
In Databases, both influxdb (31,816 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: influxdb is open source, orm is open source.
The lead is split. influxdb is furthest ahead on fork community (100 to 96), while orm is furthest ahead on adoption (100 to 96). Choose the dimension a rollout cannot compromise on.
Composite score: influxdb 93.4, orm 94.1. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
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 | influxdb | orm |
|---|---|---|
| GitHub stars | 31,816 | 47,675 |
| Forks | 3,826 | 2,635 |
| Open issues | 2,175 | 2,817 |
| Adoption | 96 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 96 |
| Issue health | 52 | 52 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 93.4 | 94.1 |
Scalable datastore for metrics, events, and real-time analytics
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 31,816 for influxdb. The gap is 15,859 stars.
Both were last pushed on 17 November 2026.
Yes. This catalog marks both influxdb and orm as self-hostable. Confirm each project's deploy docs before you plan a migration.
influxdb 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. 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.
Neither tool clears a one-point margin. influxdb scores 93.4 and orm scores 94.1.