risingwavelabs/risingwave

Event streaming platform for agentic AI. Continuously ingest, transform, and serve event streams in real time, at scale.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 35 minutes ago
Added to GitGenius on September 7th, 2026
Created on January 28th, 2022
Open Issues & Pull Requests: 1,625 (+0)
GitHub issues: Enabled
Number of forks: 835
Total Stargazers: 9,305 (+0)
Total Subscribers: 85 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1.0 hours
Mean response time: 22.3 days
90th percentile: 61.3 days
Tracked items: 2,376

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 95% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "no-issue-activity" is answered fastest, typically in about an hour, while "P-low" waits about 3 days. 38% of tracked open issues have had no activity in three months. Only 7% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 935
New in 7 days: 33
Closed in 7 days: 18
Avg open age: 518 days
Stale 30+ days: 817
Stale 90+ days: 696

Recent activity

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

Top labels

  • no-issue-activity (730)
  • type/feature (715)
  • type/bug (655)
  • cherry-pick (436)
  • type/flaky-test (95)
  • good first issue (79)
  • type/enhancement (64)
  • type/perf (57)

Detailed Description

RisingWave is a stream processing platform that ingests, transforms, and serves event data in real time using a unified SQL interface and materialized views.

The platform addresses the operational complexity of traditional real-time data pipelines by consolidating multiple specialized systems into a single engine. Rather than chaining together CDC tools, message brokers, stream processors, and serving databases, RisingWave handles ingestion, incremental processing, and low-latency querying within one system. It ingests from webhooks, database transaction logs, Kafka and other message brokers, and batch sources like S3. Data is processed through materialized views that update incrementally when upstream data changes, maintaining freshness under 100 milliseconds. Query results are served directly from an internal row store at 10-20 millisecond p99 latency, eliminating the need for separate caching layers or polling mechanisms.

The tool suits teams building real-time applications and agentic AI systems that require continuously fresh, queryable data without the operational burden of managing multiple infrastructure components. Organizations should consider it when they currently maintain separate Debezium, Kafka, Flink, and database systems and want to consolidate that stack.

The project shows active development with regular updates to its core stream processing engine and expanding source connectors. Work spans infrastructure improvements, new data source integrations, and performance optimization of the incremental computation model. The codebase is written in Rust and maintains comprehensive documentation including benchmarks and demonstration scenarios.