Ross ROSS = Recommend OSS · open-source software intelligence for agents

fluvio-community/fluvio

🦀 event stream processing for developers to collect and transform data in motion to power responsive data intensive applications. observed · 2026-08-28

github.com/fluvio-community/fluvio · homepage · Rust · Apache-2.0 (permissive) observed · 2026-08-28

Health v2 · maintenance only

79/100

  • Activity 99
  • Release rhythm 40
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.

  • gap_med: 20.5
  • age_days: 2560
  • days_rel: 425
  • days_push: 8
  • n_releases_24m: 17

Full methodology

Adoption not part of the score

5247 stars · 531 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

Fluvio is a distributed data streaming engine written in Rust that combines a Kafka-like event streaming platform with the Stateful DataFlow (SDF) framework for stateful stream processing. It supports WASM-based SmartModule transformations, inbound/outbound connectors, and client SDKs for Rust, Python, and JavaScript.

Use cases

  • build real-time data pipelines that transform data in motion
  • replace Kafka plus Flink with a single lightweight streaming stack
  • collect events from sources like HTTP, MQTT, or Kafka and route them to sinks
  • run stateful stream processing with declarative YAML dataflow definitions
  • filter and transform streaming records with WASM SmartModules
  • stream data between microservices in a cloud-native deployment

When to choose

  • you want a lean, Rust-based alternative to Kafka + Flink with lower infrastructure overhead
  • you need real-time transformation and enrichment of event streams
  • you want declarative, composable dataflows defined in YAML
  • you prefer self-hosting a lightweight streaming platform or using a managed cloud

When to avoid

  • you need the mature ecosystem and broad tooling compatibility of Apache Kafka
  • your workloads are batch ETL rather than continuous streaming
  • you require Windows natively without WSL2
  • you depend on a large community of third-party connectors and clients

Facets

service · maturity active

streaming message-queue etl workflow-automation cli microservices big-data analytics developer-tools rust windows cloud self-hosted cli stream-processing event-streaming kafka-alternative wasm-transformations smartmodules connectors data-in-motion stateful-dataflows data-engineering real-time linux macos kubernetes docker

10 sources

Member repositories

RepositoryRoleHealth v2
fluvio-community/fluviomain79

For agents

markdown · JSON · MCP: product_card(name="fluvio-community/fluvio")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem