A · leads
influxdb
94.7
31,816 stars · Apache-2.0
Databases
influxdb leads by 10.5 · clear
A · leads
94.7
31,816 stars · Apache-2.0
B
84.2
23,335 stars · Apache-2.0
influxdb versus neon 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 Rust. The composite score is 94.7 for influxdb and 84.2 for neon.
influxdb has 31,816 GitHub stars to neon's 23,335, a gap of 8,481 (1.36×). Forks are 3,826 for influxdb and 1,139 for neon. On the log scale used inside this pair, adoption is 100 versus 97, and the fork community is 100 versus 85.
Push history: influxdb was last pushed on 17 November 2026 (0 days ago), and neon was last pushed on 31 August 2026 (78 days ago). Open issues stand at 2,175 for influxdb (0.068 per star) and 589 for neon (0.025 per star). Issue-health scores are 52 and 70; activity scores are 100 and 58.
Both influxdb and neon 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 neon (23,335 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, neon is open source.
The lead is split. influxdb is furthest ahead on recent activity (100 to 58), while neon is furthest ahead on issue health (70 to 52). Choose the dimension a rollout cannot compromise on.
influxdb finishes ahead at 94.7 against neon at 84.2, a 10.5 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 | influxdb | neon |
|---|---|---|
| GitHub stars | 31,816 | 23,335 |
| Forks | 3,826 | 1,139 |
| Open issues | 2,175 | 589 |
| Adoption | 100 | 97 |
| Activity | 100 | 58 |
| Community | 100 | 85 |
| Issue health | 52 | 70 |
| License | 96 | 96 |
| Self-hosting | 100 | 100 |
| Composite | 94.7 | 84.2 |
Scalable datastore for metrics, events, and real-time analytics
Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, code-like database branching, and scale to zero.
influxdb has more GitHub stars: 31,816 versus 23,335 for neon. The gap is 8,481 stars.
influxdb was pushed more recently: 17 November 2026 versus 31 August 2026 for neon. That is 78 days apart.
Yes. This catalog marks both influxdb and neon 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. neon 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.
influxdb scores 94.7 and neon scores 84.2. This page calls that a clear lead for influxdb.