fluvio-community/fluvio

🦀 event stream processing for developers to collect and transform data in motion to power responsive data intensive applications.

View on GitHub ↗Jump to charts ↓Open shareable report →

Summary Information

Updated 37 minutes ago
Added to GitGenius on September 13th, 2026
Created on August 31st, 2019
Open Issues & Pull Requests: 139 (+0)
GitHub issues: Enabled
Number of forks: 530
Total Stargazers: 5,253 (+0)
Total Subscribers: 43 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 18.5 hours
Mean response time: 16.6 days
90th percentile: 53.5 days
Tracked items: 125

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Work labelled "no-issue-activity" is answered fastest, typically in about 5 hours, while "no-stale" waits about 2 weeks. Only 4% of issues opened in the past year have been closed. Three people close 92% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 18
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 633 days
Stale 30+ days: 18
Stale 90+ days: 18

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • no-issue-activity (57)
  • bug (41)
  • no-stale (25)
  • tracking (15)
  • help wanted (9)
  • technical debt (9)
  • good first issue (6)
  • enhancement (5)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Fluvio is a distributed data streaming engine written in Rust that combines stream processing with stateful dataflow capabilities for real-time event processing.

The tool addresses the need to collect, transform, and process data in motion at scale. It provides a unified, composable approach to streaming and stream processing through a distributed architecture. Developers work with topics to produce and consume data, and can build complex processing workflows using Stateful DataFlow, a framework that handles stateful transformations across multiple programming languages.

Fluvio suits teams building real-time, data-intensive applications that require both ingestion and transformation of streaming data. The project includes native connectors for HTTP, webhooks, MQTT, and Kafka on the inbound side, with outbound support for HTTP, SQL, Kafka, and experimental connectors to DuckDB, Redis, S3, and Graphite. A Connector Development Kit allows building custom integrations to arbitrary systems. The tool is designed to be lean and operates as a cloud-native, serverless system suitable for event-driven architectures.

Development activity shows consistent engagement with the codebase through regular commits and active issue management. The project maintains documentation across multiple areas including core Fluvio concepts, CLI usage, architecture details, and Stateful DataFlow specifics. Community examples and resources for building custom connectors are actively maintained, indicating ongoing investment in developer experience and extensibility.