Overview

RisingWave is a distributed SQL platform for processing and serving live data, best suited to teams that want streaming results through a PostgreSQL-compatible interface. Its incremental materialized views and exactly-once guarantee make it a strong fit for continuously updated data pipelines; hosted Basic’s regional availability and 64-core ceiling make it a less natural choice for deployments that need broader capacity or premium features.

Teams can use it as a hosted service or run the Apache 2.0 software themselves. That choice gives RisingWave unusual deployment flexibility, but also means buyers should distinguish the hosted plan limits from the unrestricted self-managed software.

Key features

SQL views and dbt

RisingWave accepts PostgreSQL-compatible clients, drivers, and tools, reducing the need to adopt a new query interface for teams already using that ecosystem. Materialized views are computed incrementally and refreshed as events arrive, which suits workloads that need current queryable results rather than periodic batch refreshes. The dbt-risingwave adapter adds a materialized_view materialization for continuously updated transformations.

Delivery, persistence, and connectors

Barrier-based checkpointing and consistent snapshots support the exactly-once processing guarantee. RisingWave stores data in S3-compatible object storage and checkpoints connector offsets, linking durability with exactly-once delivery. Its 31+ native connectors include Kafka, PostgreSQL, MySQL, Iceberg, Snowflake, BigQuery, S3, Redis, and Elasticsearch. That breadth can help teams connect common databases, warehouses, and storage systems, though the premium tier is required for some capabilities, including SQL Server CDC and Snowflake and BigQuery sinks.

Security and operations

Security guidance covers TLS/SSL in transit, S3 encryption at rest, certificate or password authentication, role-based grants, and SQL-based data masking. Premium capabilities add SSO, LDAP governance, automatic schema evolution, time travel queries, and OTEL integration. These options matter to organizations with governance or operational requirements, but they are not part of the low-cost hosted Basic offering.

Pricing

Basic: 0.23 USD per month, billed Pay-as-you-go. It is fully hosted on AWS, GCP, or Azure, supports up to 64 cores, and includes standard support. This is the clearest starting point for teams that want managed streaming without operating the infrastructure, but its core limit and select-region availability constrain larger or geographically specific deployments.

Pro: custom pricing, billed Pay-as-you-go or annual contract. It supports fully hosted or BYOC deployment, has no core limits, and includes premium features; premium 24x7 support is available for purchase. It suits teams that need greater hosted capacity or premium capabilities, but the support upgrade is an additional purchase.

Self-managed: custom pricing, billed Annual contract. On-premises or Kubernetes deployments have no core limits, feature gates, license fees, or usage restrictions under the Apache 2.0 open-source software. Premium features and support with an SLA are included, along with quarterly success reviews. This fits organizations that want deployment control and extensive capacity, although they take on running the software themselves.

The local playground is a separate, single-node in-memory option that stops automatically after 30 minutes of inactivity, so it is suited to short-lived exploration rather than persistent workloads.

Platforms

RisingWave supports API, Linux, macOS, self-hosted, and web environments, with a hybrid deployment model. Self-managed installations can use Docker, Kubernetes with Helm charts, cloud VMs, or on-premises bare-metal servers. Supported client languages include Python, Java, and Node.js.

Who it's for

RisingWave is a good fit for teams building streaming pipelines or applications that need queryable results to stay current as events arrive, especially when PostgreSQL tooling or dbt already features in their workflow. Hosted Basic suits smaller deployments in supported regions; Pro better matches teams that need hosted or BYOC capacity without a core ceiling. Self-managed is the stronger choice for organizations that require unrestricted usage, on-premises deployment, or premium support and SLA terms. Teams seeking a simple hosted service without a 64-core limit or premium-tier requirements should weigh other options.

Pros and cons

Pro: Incremental materialized views and PostgreSQL wire compatibility combine fresh streaming results with familiar client tooling.
Pro: Exactly-once processing, durable object-storage persistence, and 31+ connectors support a broad range of streaming data pipelines.
Pro: Apache 2.0 self-managed deployments have no license fees, feature gates, or usage restrictions, with multiple infrastructure choices.
Con: Hosted Basic is limited to 64 cores and select regions, which can rule it out for larger or location-constrained workloads.
Con: Several enterprise-oriented capabilities sit in premium plans, while Pro’s 24x7 support costs extra.

Alternatives

Choose Aiven for Apache Kafka if a managed Kafka service with a published free tier is a better fit: its Free plan includes 250 KiB/s throughput, three days of retention, five topics, and two partitions per topic. Apache Pulsar is a free alternative for readers seeking open-source event streaming software. Confluent Cloud offers a free Basic plan with serverless managed clusters, autoscaling Kafka resources, and 80+ managed connectors, making it worth considering when those Kafka-service features matter more than RisingWave’s SQL streaming model. Lightstreamer is another freemium option to compare.

Redpanda is an alternative with serverless usage-based billing, a Kafka API, and Redpanda Connect integration. DataStax Astra Streaming offers a free tier and usage-based paid plans. Pravega is a free Linux option, while Solace PubSub+ Event Broker is another freemium choice.

Readers comparing broader categories can also browse Event Streaming Platforms, Stream Processing Software, and Streaming Analytics Software.

Verdict

Choose RisingWave when your team needs SQL-accessible streaming data, incrementally maintained views, and exactly-once processing, particularly if PostgreSQL tooling or dbt is already part of the workflow. Its strongest case is the combination of familiar SQL access, broad connectors, and a genuinely unrestricted self-managed option. Look elsewhere if you need a hosted deployment beyond Basic’s 64-core limit without moving to custom-priced Pro, or if you want key premium capabilities included at the entry tier.

	Apache Pinot	RisingWave
Free plan	Yes	No
Free trial	No	Yes
Paid from	Free	$0.23/mo
Open source	No	No
Platforms	api, self-hosted, Web	api, Linux, macOS, self-hosted, Web
Deployment	self_hosted	—
Free plan	—	No

Apache Pinot vs RisingWave

Apache Pinot

RisingWave