Softwr

Databases · head to head

Cockroach Labs vs RisingWave

Cockroach Labs logo

Cockroach Labs

Databases

The cloud-native distributed SQL database

From
Free
Rated
-
RisingWave logo

RisingWave

Databases

Streaming database that maintains incremental materialised views in SQL instead of Flink jobs

From
Free
Rated
-

The short version

  • Each has a real cost: Cockroach Labs basic and Standard tiers limited to AWS and GCP (select regions only); RisingWave anything that does not fit SQL, such as custom windowing, complex event processing or heavy stateful logic, still needs Flink, so RisingWave often adds a system rather than removing one.
  • They diverge on capability: Cockroach Labs covers Distributed SQL, RisingWave covers SQL materialised views.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Cockroach Labs and RisingWave actually diverge.

Attributes where Cockroach Labs and RisingWave differ
AttributeCockroach LabsRisingWave
Pricing modelfreemiumPer RisingWave Unit hour
PlatformsAWS, GCP, AzureLinux, Docker, Kubernetes, Cloud
Founded2015Unknown

Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Databases).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Cockroach Labs

  • Distributed SQL
  • Automatic Sharding
  • Multi-region Replication
  • Geo-partitioning
  • ACID Transactions
  • Horizontal Scaling
  • Survivability
  • PostgreSQL Compatibility

Only in RisingWave

  • SQL materialised views
  • Postgres wire compatibility
  • Object storage state
  • Source connectors
  • Sink connectors
  • Iceberg tables
  • Watermarks and windowing
  • User defined functions

What people use each for

The jobs each tool is most often brought in to do.

Cockroach Labs

  • Distributed SQL database for scalable applicationsnot RisingWave
  • Multi-region deployment and failovernot RisingWave

RisingWave

  • A team with Kafka topics that needs continuously fresh aggregates for a dashboard without standing up a Flink clusternot Cockroach Labs
  • A fraud or risk team maintaining rolling counters and joins across event streams expressed as SQL viewsnot Cockroach Labs
  • A company doing Postgres CDC into a real-time denormalised view for search or servingnot Cockroach Labs
  • An analytics group that wants streaming results landed directly into Apache Iceberg without a separate writer jobnot Cockroach Labs

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Cockroach Labs

  • Basic and Standard tiers limited to AWS and GCP (select regions only)
  • Azure support restricted to Advanced tier only
  • Basic tier limited to 50 million RUs and 10 GiB storage per month
  • Advanced tier starts at $0.60/hour for 4 vCPUs minimum
  • 3 TiB maximum storage on Basic and Standard tiers, 10 TiB per node on Advanced

RisingWave

  • Anything that does not fit SQL, such as custom windowing, complex event processing or heavy stateful logic, still needs Flink, so RisingWave often adds a system rather than removing one.
  • The Apache 2.0 community edition excludes premium features behind a licence key, and which capabilities sit on which side of that line moves between releases, so a self-hosted plan can be invalidated by an upgrade.
  • Long-running materialised views accumulate state in object storage, and cost and recovery time grow with retention in ways that are hard to forecast before you are in production.
  • The Postgres compatibility is protocol level; it is not a transactional Postgres and using it as a general purpose database, with point updates or high write concurrency, goes badly.
  • It is a comparatively young venture-funded project competing with Flink, Materialize and warehouse-native streaming, and the ecosystem of connectors, operators and third-party expertise is much thinner.

Pricing, plan by plan

Cockroach Labs

Free

No published plan breakdown. See the Cockroach Labs review.

RisingWave

Free
  • Community EditionFree
    • Apache 2.0 licence, self-hosted
    • Core streaming engine and connectors
    • Premium features excluded and require a licence key
  • Cloud Basic$0.227/hour
    • Billed per RisingWave Unit hour
    • Hosted on AWS, GCP or Azure
    • Capped at 64 cores
  • Cloud Pro$undefined/year
    • No core limit
    • Bring your own cloud option
    • Premium features included
  • Self-managed Enterprise$undefined/year
    • On premises or Kubernetes
    • Premium features unlocked by licence
    • Annual contract with SLA

Which should you pick?

Choose Cockroach Labs if

  • You need distributed sql.
  • You want to start without paying.
  • You work on AWS, GCP, Azure.
  • You also want automatic sharding.

Choose RisingWave if

  • You need sql materialised views.
  • You want to start without paying.
  • You work on Linux, Docker, Kubernetes, Cloud.
  • You also want postgres wire compatibility.

Questions people ask

Is Cockroach Labs or RisingWave better?
Neither clearly leads. Cockroach Labs starts at Free and RisingWave at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Cockroach Labs or RisingWave?
Cockroach Labs starts at Free and RisingWave at Free.
Does Cockroach Labs or RisingWave run on more platforms?
Cockroach Labs runs on AWS, GCP, Azure. RisingWave runs on Linux, Docker, Kubernetes, Cloud.
Can I use Cockroach Labs for free?
Both have a free tier, so you can try either at no cost before committing.
What is Cockroach Labs best used for?
Cockroach Labs is most often used for distributed sql database for scalable applications, multi-region deployment and failover. Of those, distributed sql database for scalable applications and multi-region deployment and failover are not what RisingWave is typically brought in for.
What can Cockroach Labs do that RisingWave cannot?
Cockroach Labs covers Distributed SQL, Automatic Sharding, Multi-region Replication, Geo-partitioning. RisingWave covers SQL materialised views, Postgres wire compatibility, Object storage state, Source connectors.

Answered from the vendors’ own pages

Cockroach Labs: What does the free Basic tier include?

The Basic tier is free and includes 50 million RUs and 10 GiB storage per month, with a maximum compute of 30K RU/sec. No credit card is required to start.

Source
RisingWave: Is RisingWave open source?

The community edition is Apache 2.0 and self-hostable, but a set of premium features requires a paid licence key.

Cockroach Labs: How much do the paid tiers cost?

Standard tier starts at $0.18 per hour for 2 vCPUs, and Advanced tier starts at $0.60 per hour for 4 vCPUs. Both tiers support additional resources with higher costs for increased compute and storage.

Source
RisingWave: What does the cloud cost?

It starts at 0.227 US dollars per RisingWave Unit hour on the Basic tier, which is capped at 64 cores.

Cockroach Labs: What are the storage limits for each tier?

Basic plan supports up to 3 TiB storage, Standard tier up to 3 TiB, and Advanced tier up to 10 TiB per node with unlimited total storage.

Source
RisingWave: Does it replace Flink?

For SQL-expressible transformations, often yes. For custom stateful processing and complex event handling, no.

Cockroach Labs: Can I get trial credits before paying?

Yes, new users can try CockroachDB free with $400 in credits. The Basic and Standard plans do not require a credit card to start.

Source
RisingWave: Can I query it like Postgres?

Yes over the Postgres wire protocol, but it is an analytical streaming engine, not a transactional database.

Cockroach Labs: Do legacy contracts have different pricing?

Customers with annual or multi-year contracts entered before December 1, 2024 can view legacy pricing terms on a separate page, which apply until their contract renewal date.

Source
Share

Related pages

Other head to heads