influxdata/influxdb

Prefer this fork only if you need the old Go/Graphite-era InfluxDB implementation. For almost any production or modernization goal, upstream is the better choice because this fork is highly stale and far behind the current architecture and feature set.

Prefer this fork only if you specifically need a legacy, custom-maintained InfluxDB variant and are willing to own the technical debt. For new work, the upstream project is far more active and materially more capable.

Prefer this fork only if you specifically need its legacy sync-oriented customization and are willing to own maintenance. For most adopters, upstream is the better choice because it is active, far newer, and has the modern InfluxDB 3 feature set.

Prefer this fork only if you specifically want its edge-oriented changes and are prepared to maintain a large divergence. For most adopters, upstream is the better choice because it is far more current and actively maintained.

Choose the fork only if you are deliberately maintaining a legacy InfluxDB stack. For new deployments or active product work, upstream is the better choice by a wide margin.

Prefer this fork only if you need an older InfluxDB behavior surface and are prepared to own a stale codebase. If you want active development or InfluxDB 3 Core features, upstream is the better choice.

Prefer this fork only if you need an older, customized InfluxDB codebase and are willing to own the maintenance burden. If you want current features, active fixes, and the modern Rust-based architecture, upstream is the better choice.

Choose this fork only if you need legacy Go-based InfluxDB behavior and are willing to own a long-term maintenance burden. For new work, upstream is the better default: it is active, materially newer, and much more complete.

Prefer this fork only if you need the older InfluxDB/Chronograf/task ecosystem and are willing to own a very stale, highly divergent codebase. For most adopters, upstream is the better choice because it is active and has substantially newer storage, query, and operational features.