RisingWave

Overview

RisingWave is a SQL-based platform for processing and serving streaming data, best suited to teams that need continuously updated results from live event streams. Its PostgreSQL-compatible interface and choice of hosted or self-managed deployment make it a flexible option, though hosted Basic has a 64-core ceiling and premium capabilities sit on higher-tier plans.

Key features

SQL and incremental views

RisingWave works with PostgreSQL clients, drivers, and tools through its wire-compatible SQL interface, a practical fit for teams already using that ecosystem. Materialized views refresh incrementally as new events arrive, and the dbt-risingwave adapter supports continuously updated transformations through its materialized_view materialization.

Delivery, persistence, and connectors

Barrier-based checkpointing and consistent snapshots underpin its exactly-once processing guarantee. Data is persisted in S3-compatible object storage, with connector offsets checkpointed for durability and exactly-once delivery. The 31+ native connectors include Kafka, PostgreSQL, MySQL, Iceberg, Snowflake, BigQuery, S3, Redis, and Elasticsearch, giving teams several common sources and destinations without limiting the platform to Kafka alone.

Premium capabilities and security

Premium capabilities include SQL Server CDC, Snowflake and BigQuery sinks, time travel queries, automatic schema evolution, SSO, LDAP governance, and OTEL integration. Security guidance covers TLS/SSL in transit, S3 encryption at rest, certificate or password authentication, role-based grants, and SQL-based data masking. These controls and integrations make premium tiers more relevant to organizations with governance or operational requirements than to a small prototype.

Pricing

RisingWave has a free plan and a 7-day trial. Basic costs 0.23 USD per month on pay-as-you-go billing. It is fully hosted on AWS, GCP, or Azure, includes up to 64 cores and standard support, and is available only in select regions. That makes it the straightforward hosted entry point, but the core cap and regional availability may rule it out for larger or geographically constrained deployments.

Pro has custom pricing and can be billed pay-as-you-go or by 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 needing greater capacity or premium capabilities, but support uplift is an additional decision rather than an automatic inclusion.

Self-managed pricing is custom pricing under an annual contract. The plan supports on-premises or Kubernetes deployments, has no core limits, and includes premium features plus premium support and an SLA. It is aimed at organizations that need deployment control and service commitments, with the tradeoff of operating their own installation.

Local playground

The single-node playground runs in memory and stops automatically after 30 minutes of inactivity. It is useful for brief evaluation, not a persistent service or production deployment.

Platforms

RisingWave supports API access, Linux, macOS, web access, and self-hosted deployment. Self-managed installations can run with Docker, Kubernetes using Helm charts, cloud VMs, or on-premises bare-metal servers. Hosted Basic runs on AWS, GCP, or Azure; Pro also offers BYOC. Its hybrid deployment model gives infrastructure teams options, while the local in-memory playground remains intentionally temporary.

Who it's for

RisingWave fits data and application teams building streaming pipelines or services that need fresh queryable results from incoming events. PostgreSQL compatibility can ease client integration, while incremental views, dbt support, and connectors suit SQL-oriented transformation workflows. Teams needing unlimited cores, premium integrations, governance features, or an SLA should examine Pro or self-managed deployment. It is less suitable when a small, persistent local instance is the goal, since the playground stops after inactivity.

Pros and cons

• Pros: PostgreSQL wire compatibility lets existing PostgreSQL clients and tooling connect.
• Pros: Incrementally refreshed materialized views and dbt integration support continuously updated SQL transformations.
• Pros: Exactly-once processing, durable object-storage persistence, and checkpointed offsets address consistency and recovery needs.
• Pros: Hosted, BYOC, and self-managed options span cloud and on-premises deployment.
• Cons: Basic is capped at 64 cores and limited to select regions.
• Cons: Pro and self-managed use custom pricing, making cost comparison less immediate than Basic.
• Cons: The playground is in-memory and stops after 30 minutes without activity, so it cannot serve as an always-on local environment.

Alternatives

Aiven for Apache Kafka is worth considering when a freemium Kafka option with a stated free-tier throughput, retention, and topic limits better fits the need.

Apache Pulsar is a free, open-source alternative for readers who prefer a community-backed project and need its broader listed platform support, including Windows.

Confluent Cloud is another freemium choice for teams looking for a managed Kafka service with autoscaling resources and more than 80 fully managed connectors.

Redpanda is an alternative for teams seeking a Kafka API with serverless or bring-your-own-cloud deployment options.

Lightstreamer is a freemium alternative with support across web, desktop, and mobile platforms.

DataStax Astra Streaming offers a freemium option for readers considering usage-based paid plans.

Pravega is a free alternative for Linux deployments.

Solace PubSub+ Event Broker is another freemium option.

Browse more options in Event Streaming Platforms, Stream Processing Software, and Streaming Analytics Software.

Verdict

Choose RisingWave if your team wants SQL-driven streaming transformations and incrementally maintained views, with PostgreSQL-compatible clients and a deployment model that can range from hosted service to self-managed infrastructure. Its strongest case is combining those capabilities with exactly-once processing and broad connectors. Look elsewhere if you need a clearly bounded low-cost tier beyond Basic, a Basic region or capacity it does not offer, or a persistent local playground.