RisingWave Cloud
RisingWave Cloud is a fully managed, serverless streaming database that processes real-time data with sub-second latency via an incremental compute engine.
Publisher review
RisingWave Cloud is a fully managed, serverless streaming database that processes real-time data with sub-second latency via an incremental compute engine. It exposes a PostgreSQL-compatible SQL interface, allowing teams to use standard queries and tools (e.g., psql, JDBC) without learning a new language. The service targets data engineers and developers who need to ingest, analyze, and serve streaming data—such as clickstreams, IoT sensor readings, or financial ticks—without provisioning servers or managing infrastructure. Its intuitive console provides a dashboard for deploying, monitoring, and scaling streaming pipelines, while built-in data serving capabilities let users query materialized views directly, eliminating the need for a separate serving layer. RisingWave Cloud is ideal for organizations that want a cloud-native stream processor that feels like a familiar relational database.
The platform works by connecting to diverse data sources—including Kafka, Pulsar, Kinesis, and PostgreSQL CDC—through extensive source and sync integrations. Once ingested, RisingWave's incremental compute engine updates materialized views continuously, guaranteeing data consistency and order with bounded correctness guarantees. Users define these views using standard SQL, and the system automatically handles state management, fault tolerance, and exactly-once semantics. The serverless architecture scales compute resources (measured in RisingWave Units, or RWUs) up to 64 cores on the Basic plan, with no core limits on Pro or Self-managed tiers. Storage is billed per GB-month, and network egress incurs data transfer charges. The platform supports PostgreSQL protocol natively, enabling integration with BI tools like Tableau, Metabase, and Grafana for visualization and delivery of results.
RisingWave Cloud competes directly with Materialize, another streaming database built on Rust and PostgreSQL compatibility. While both offer incremental computation and SQL-based stream processing, RisingWave differentiates itself with a distributed, cloud-native architecture from the start—Materialize's open-source version was originally single-node. RisingWave also provides a self-managed option for on-premises or Kubernetes environments, which Materialize does not offer as a first-class tier. The Basic plan's pay-as-you-go pricing ($0.227/RWU/hour) after a 7-day free trial makes it accessible for small-scale deployments, whereas Materialize's pricing is typically higher and less transparent. However, Materialize has a longer track record and more documented enterprise use cases, which may appeal to risk-averse buyers.
The honest trade-offs: RisingWave Cloud's documentation and community examples are less mature than Materialize's, making troubleshooting harder for niche patterns. The Basic plan's 64-core cap limits throughput for very high-volume pipelines (e.g., millions of events per second) without upgrading to Pro. The self-managed tier requires annual contracts and operational expertise in Kubernetes, which may offset cost savings for small teams. Additionally, while RisingWave supports PostgreSQL wire protocol, it does not implement all PostgreSQL features (e.g., full procedural language support), so some migrations may require query rewrites. The platform is best suited for teams that prioritize a serverless, pay-as-you-go model and are willing to trade some ecosystem maturity for lower initial cost and architectural flexibility.
How it works
-
PostgreSQL-compatible SQL interface
Supports standard SQL and PostgreSQL wire protocol, enabling use with existing tools like psql, JDBC, and BI platforms.
-
Incremental compute engine
Updates materialized views continuously with sub-second latency, avoiding full recomputation on each data arrival.
-
Serverless architecture
Eliminates manual server provisioning; compute scales automatically based on workload, measured in RisingWave Units (RWUs).
-
Extensive source and sync integrations
Ingests from Kafka, Pulsar, Kinesis, PostgreSQL CDC, and more, with built-in connectors for diverse streaming pipelines.
-
Built-in data serving capabilities
Queries materialized views directly without an external serving layer, reducing latency and operational complexity.
-
Informative deployment dashboard
Provides a console for deploying, monitoring, and scaling streaming services, with visual metrics on throughput and lag.
-
Bounded correctness guarantees
Ensures data consistency and order with exactly-once semantics, critical for financial and operational analytics.
Strengths and trade-offs
Strengths
- Simplifies stream processing with a PostgreSQL-compatible SQL interface, letting teams use standard queries and tools like psql and JDBC without learning new syntax.
- Incremental compute engine delivers sub-second latency on materialized views, enabling real-time dashboards and alerts without batch delays.
- Serverless Basic plan starts at $0.227/RWU/hour after a 7-day free trial, with no upfront commitment, lowering the barrier for small-scale streaming workloads.
- Supports self-managed deployment on Kubernetes via annual contract, offering full control over infrastructure for enterprises with compliance requirements.
Trade-offs
- Documentation and community examples are less extensive than Materialize's, making it harder to troubleshoot niche streaming patterns or complex SQL transformations.
- Basic plan caps compute at 64 cores, limiting throughput for high-volume pipelines (e.g., millions of events per second) without upgrading to the Pro tier.
- Self-managed tier requires an annual contract and Kubernetes operational expertise, which may negate cost savings for teams without dedicated DevOps support.
- Does not implement all PostgreSQL features (e.g., full PL/pgSQL support), so migrating existing PostgreSQL workloads may require query rewrites and feature workarounds.
Pricing context
Three tiers: Basic ($0.227/RWU/hour, up to 64 cores, pay-as-you-go after 7-day free trial); Pro (elastic scale, no core limits, pay-as-you-go or annual contract); Self-managed (on-prem/K8s, annual contract). Storage billed per GB-month; network egress charged separately.
Getting started with RisingWave Cloud
-
Sign up for RisingWave Cloud
Navigate to the RisingWave Cloud website and create an account. Provide your email and set a password, or use a social login. After verification, you will receive a 7-day free trial with access to the Basic plan.
-
Connect a data source
In the console, go to the Sources section and click Add Source. Choose your streaming source (e.g., Kafka, Kinesis, or PostgreSQL CDC). Enter the connection details such as broker URL, topic name, and credentials, then test the connection.
-
Define a materialized view
Use the SQL editor in the dashboard to write a CREATE MATERIALIZED VIEW statement. For example, create a view that aggregates clickstream events by user. The incremental compute engine will continuously update this view as new data arrives.
-
Query the materialized view
Connect to RisingWave Cloud using any PostgreSQL-compatible client like psql or a BI tool such as Tableau. Run SELECT queries against your materialized view to retrieve real-time results. No separate serving layer is needed.
-
Monitor and scale the pipeline
Open the Monitoring tab in the console to view throughput, lag, and compute usage metrics. Adjust the RisingWave Units (RWUs) in the Settings to scale compute resources up or down based on workload demands.
Frequently Asked Questions
What is RisingWave Cloud?
RisingWave Cloud is a fully managed, serverless streaming database that processes real-time data with sub-second latency. It uses an incremental compute engine and exposes a PostgreSQL-compatible SQL interface, letting teams use standard queries without provisioning servers or managing infrastructure.
How does RisingWave Cloud handle real-time data processing?
RisingWave Cloud connects to sources like Kafka, Pulsar, and Kinesis, then uses an incremental compute engine to update materialized views continuously. This ensures sub-second latency and data consistency with exactly-once semantics, all defined through standard SQL queries.
What are the pricing tiers for RisingWave Cloud?
RisingWave Cloud offers three tiers: Basic at $0.227 per RWU per hour with up to 64 cores after a 7-day free trial, Pro with elastic scale and no core limits, and Self-managed for on-premises or Kubernetes via annual contract. Storage and egress are billed separately.
How does RisingWave Cloud compare to Materialize?
RisingWave Cloud offers a distributed, cloud-native architecture from the start and a self-managed tier for on-premises use, which Materialize lacks. Its Basic plan has transparent pay-as-you-go pricing, while Materialize's pricing is typically higher. However, Materialize has more mature documentation and enterprise case studies.
What are the limitations of RisingWave Cloud?
RisingWave Cloud's documentation and community examples are less mature than Materialize's, making troubleshooting harder. The Basic plan caps compute at 64 cores, and the self-managed tier requires an annual contract and Kubernetes expertise. It also lacks full PostgreSQL procedural language support, requiring query rewrites for some migrations.
What are the key features of RisingWave Cloud?
Key features include a PostgreSQL-compatible SQL interface, an incremental compute engine for sub-second latency, serverless architecture with automatic scaling, extensive source integrations like Kafka and Kinesis, built-in data serving for direct querying of materialized views, and a deployment dashboard for monitoring and scaling.
Alternatives
How RisingWave Cloud compares
Direct head-to-head against 2 competitors. Picked by 7wData.
RisingWave Cloud
- Pricing
- Three tiers: Basic ($0.227/RWU/hour, up to 64 cores, pay-as-you-go after 7-day free trial); Pro (elastic scale, no core limits, pay-as-you-go or annual contract); Self-managed (on-prem/K8s, annual contract). Storage billed per GB-month; network egress charged separately.
- Target
- RisingWave Cloud is a fully managed, serverless streaming database that processes real-time data with sub-second latency via an incremental compute engine.
- Strength
- Simplifies stream processing with a PostgreSQL-compatible SQL interface, letting teams use standard queries and tools like psql and JDBC without learning new syntax.
- Watch for
- Documentation and community examples are less extensive than Materialize's, making it harder to troubleshoot niche streaming patterns or complex SQL transformations.
Materialize
- Pricing
- Custom/Contact sales
- Target
- Enterprise-grade live data layer
- Deployment
- Cloud, On-prem
- Strength
- Strong consistency guarantees
- Watch for
- Higher cost for smaller teams
Apache Flink
- Pricing
- Open source
- Target
- Complex stream processing
- Deployment
- Cloud, On-prem
- Strength
- Mature ecosystem
- Watch for
- Steep learning curve
User reviews
No user reviews yet. Be the first to write one.
Sources
Reporting on this tool draws on these publicly available sources.