Softwr

Databases · head to head

RisingWave vs Timeplus

RisingWave logo

RisingWave

Databases

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

From
Free
Rated
-
Full reviewWebsite
Timeplus logo

Timeplus

Databases

Streaming SQL engine built on ClickHouse internals, shipping as one small binary

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: 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.; Timeplus proton, the free version, is single-node by design, so any requirement for high availability or horizontal scale forces the commercial licence; the open source edition is a trial in practical terms.
  • They diverge on capability: RisingWave covers SQL materialised views, Timeplus covers Streaming SQL.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which RisingWave and Timeplus actually diverge.

Attributes where RisingWave and Timeplus differ
AttributeRisingWaveTimeplus
Pricing modelPer RisingWave Unit hourPer month for cloud, quoted for self-hosted
PlatformsLinux, Docker, Kubernetes, CloudLinux, macOS, Docker, Kubernetes, Web

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 RisingWave

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

Only in Timeplus

  • Streaming SQL
  • Unified streaming and historical
  • ClickHouse-based engine
  • Single binary deployment
  • External streams
  • Materialised views

What people use each for

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

RisingWave

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

Timeplus

  • Real-time alerting on Kafka topics where standing up a Flink cluster is more work than the use case justifiesnot RisingWave
  • Fraud or anomaly detection that must join a live event stream against recent history in one querynot RisingWave
  • Streaming ETL from Kafka or MySQL change data capture into ClickHouse without writing Javanot RisingWave
  • A small data team that needs continuous aggregation but has no platform engineers to operate JVM infrastructurenot RisingWave

Where each one falls short

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

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.

Timeplus

  • Proton, the free version, is single-node by design, so any requirement for high availability or horizontal scale forces the commercial licence; the open source edition is a trial in practical terms.
  • It is a young project against Apache Flink’s decade of production history, so the hiring pool, the connector library and the body of known failure modes are all much smaller.
  • Inheriting ClickHouse internals also inherits ClickHouse constraints: memory-hungry queries, awkward updates and a SQL dialect that is not portable to other engines.
  • Exactly-once semantics and state recovery guarantees are less battle-tested than Flink checkpointing, which matters if the pipeline moves money.
  • Cloud pricing is by provisioned instance size rather than usage, so a bursty workload pays for peak capacity around the clock or has to be resized by hand.

Pricing, plan by plan

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

Timeplus

Free
  • Timeplus ProtonFree
    • Apache 2.0 licence
    • Single node only
    • Full streaming SQL engine
  • Timeplus Cloud$199/month
    • One to thirty-two CPUs
    • 4 GB to 128 GB memory
    • From 250 GB SSD storage
  • Self-hosted or BYOC$undefined/year
    • Multi-node clustering
    • Kubernetes or bare metal
    • Customisable compute and storage

Which should you pick?

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

Choose Timeplus if

  • You need streaming sql.
  • You want to start without paying.
  • You work on Linux, macOS, Docker, Kubernetes, Web.
  • You also want unified streaming and historical.
Timeplus review

Questions people ask

Is RisingWave or Timeplus better?
Neither clearly leads. RisingWave starts at Free and Timeplus at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, RisingWave or Timeplus?
RisingWave starts at Free and Timeplus at Free.
Does RisingWave or Timeplus run on more platforms?
RisingWave runs on Linux, Docker, Kubernetes, Cloud. Timeplus runs on Linux, macOS, Docker, Kubernetes, Web.
Can I use RisingWave for free?
Both have a free tier, so you can try either at no cost before committing.
What is RisingWave best used for?
RisingWave is most often used for a team with kafka topics that needs continuously fresh aggregates for a dashboard without standing up a flink cluster, a fraud or risk team maintaining rolling counters and joins across event streams expressed as sql views, a company doing postgres cdc into a real-time denormalised view for search or serving, an analytics group that wants streaming results landed directly into apache iceberg without a separate writer job. Of those, a team with kafka topics that needs continuously fresh aggregates for a dashboard without standing up a flink cluster and a fraud or risk team maintaining rolling counters and joins across event streams expressed as sql views are not what Timeplus is typically brought in for.
What can RisingWave do that Timeplus cannot?
RisingWave covers SQL materialised views, Postgres wire compatibility, Object storage state, Source connectors. Timeplus covers Streaming SQL, Unified streaming and historical, ClickHouse-based engine, Single binary deployment.

Answered from the vendors’ own pages

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.

Timeplus: Is Timeplus open source?

The core engine, Timeplus Proton, is Apache 2.0. Timeplus Enterprise and Cloud are commercial.

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.

Timeplus: What is the difference from Flink?

Timeplus is one binary with SQL as the only interface; Flink is a JVM cluster with a Java and SQL API and far more operational surface.

RisingWave: Does it replace Flink?

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

Timeplus: Can Proton run in production?

It can, but it is single-node only, so there is no high availability without the commercial edition.

RisingWave: Can I query it like Postgres?

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

Timeplus: How much is the cloud?

From 199 US dollars a month, sized by CPU and memory, with a fourteen day trial.

Share

Related pages

More on RisingWave

More on Timeplus

Keep looking

Other head to heads