Softwr

Databases · head to head

CosmosDB vs RisingWave

CosmosDB logo

CosmosDB

Databases

Globally distributed, multi-model database service from Azure

From
Free
Rated
-
Full reviewWebsite
RisingWave logo

RisingWave

Databases

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

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: CosmosDB autoscale provisioned throughput enforces a minimum of 1,000 RU/s, billed hourly whether or not the database is used; 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: CosmosDB covers Global Distribution, RisingWave covers SQL materialised views.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which CosmosDB and RisingWave actually diverge.

Attributes where CosmosDB and RisingWave differ
AttributeCosmosDBRisingWave
Pricing modelusage-basedPer RisingWave Unit hour
PlatformsWeb, AzureLinux, Docker, Kubernetes, Cloud
Founded1975Unknown

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 CosmosDB

  • Global Distribution
  • Multi-model APIs
  • Elastic Scaling
  • Five Consistency Levels
  • SLA-backed Latency
  • Automatic Indexing
  • Serverless
  • Azure Functions

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.

CosmosDB

  • Running a globally distributed multi model database on Azurenot RisingWave
  • Serving low latency reads and writes from multiple Azure regionsnot RisingWave
  • Storing document, key value and graph data behind a managed servicenot RisingWave

RisingWave

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

Where each one falls short

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

CosmosDB

  • Autoscale provisioned throughput enforces a minimum of 1,000 RU/s, billed hourly whether or not the database is used
  • Provisioned throughput is charged in every region the account is replicated to, so multi region accounts multiply the RU bill
  • Storage charges cover data, indexes and backups in each replicated region
  • Egress out of Azure and between regions is charged, though ingress is free
  • The free allowance is one account per Azure subscription, limited to 1,000 RU/s and 25 GB
  • RU/s rates vary by region and are only shown through the pricing calculator rather than a flat published rate

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

CosmosDB

Free
  • Free TierFree
    • 1000 RU/s
    • 25GB storage
    • First 12 months
  • ServerlessFree
    • Pay per request
    • Auto-scaling
    • Event-driven workloads

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 CosmosDB if

  • You need global distribution.
  • You want to start without paying.
  • You work on Web, Azure.
  • You also want multi-model apis.
CosmosDB review

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.
RisingWave review

Questions people ask

Is CosmosDB or RisingWave better?
Neither clearly leads. CosmosDB 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, CosmosDB or RisingWave?
CosmosDB starts at Free and RisingWave at Free.
Does CosmosDB or RisingWave run on more platforms?
CosmosDB runs on Web, Azure. RisingWave runs on Linux, Docker, Kubernetes, Cloud.
Can I use CosmosDB for free?
Both have a free tier, so you can try either at no cost before committing.
What is CosmosDB best used for?
CosmosDB is most often used for running a globally distributed multi model database on azure, serving low latency reads and writes from multiple azure regions, storing document, key value and graph data behind a managed service. Of those, running a globally distributed multi model database on azure and serving low latency reads and writes from multiple azure regions are not what RisingWave is typically brought in for.
What can CosmosDB do that RisingWave cannot?
CosmosDB covers Global Distribution, Multi-model APIs, Elastic Scaling, Five Consistency Levels. RisingWave covers SQL materialised views, Postgres wire compatibility, Object storage state, Source connectors.

Answered from the vendors’ own pages

CosmosDB: Is there a free tier for Azure Cosmos DB?

Yes, Cosmos DB offers a free tier with 1,000 RU/s of throughput and 25 GB of storage per month for the lifetime of the account, available to new accounts.

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.

CosmosDB: How is Cosmos DB priced after the free tier?

Cosmos DB uses three billing models: provisioned throughput billed per request unit per second, vCore pricing for certain APIs, or serverless consumption pricing where you pay only for requests processed. Reserved capacity offers 20% discount for one year or 30% for three years.

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.

CosmosDB: Can I change my pricing model after choosing one?

No. Once you select a compute pricing model and API, they cannot be changed. This choice is permanent for that database.

Source
RisingWave: Does it replace Flink?

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

CosmosDB: Is there a trial period for Cosmos DB beyond the free tier?

Azure offers a 30-day free trial account for all Azure services. Additionally, Azure AI customers may be eligible for a 90-day free Cosmos DB subscription through the Azure AI Advantage program.

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.

Share

Related pages

More on CosmosDB

More on RisingWave

Keep looking

Other head to heads