Skip to content

Adoption & Ecosystem

Who uses it

The repository's ADOPTERS.md only links to the project testimonials page (source 7) and lists no specific names. The CNCF graduation announcement of 2019-04-11 names the organizations below (source 4).

OrganisationUse caseSource
AtlassianLog collection at scaleCNCF graduation announcement
Amazon Web ServicesLog collection at scaleCNCF graduation announcement
Change.orgLog collection at scaleCNCF graduation announcement
CyberAgentLog collection at scaleCNCF graduation announcement
LINE CorpLog collection at scaleCNCF graduation announcement
NintendoLog collection at scaleCNCF graduation announcement
MicrosoftLog collection at scaleCNCF graduation announcement

Adoption signals

At graduation in 2019 the project reported more than 5,000 community users (source 4). GitHub signals on 2026-06-22 (source 8):

  • Stars: 13,546
  • Forks: 1,392
  • Open issues: 136
  • Contributors: roughly 285 (GitHub contributors API, includes anonymous)

Ecosystem

Fluentd's main asset is its plugin catalog, with more than 500 community-built input, output, filter, parser, formatter, and buffer plugins managed through fluent-gem (source 1). Around the core are fluent-operator (a Kubernetes operator), Helm charts, and the C-based sister project Fluent Bit, all under the fluent GitHub organization (source 1).

Alternatives

Fluentd's real differentiation is the largest plugin ecosystem, vendor-neutral CNCF governance, and tag-based routing with a buffering abstraction. Its weakness is footprint: the Ruby core is heavier on memory and CPU than the C and Rust alternatives (source 6).

AlternativeDiffers by
Fluent BitC implementation, sub-megabyte footprint, aimed at edge and Kubernetes sidecars; same authors
LogstashJVM-based, strong grok/dissect transforms and ELK integration, the heaviest footprint
VectorRust, high throughput with the VRL transform language, a middling footprint