Softwr

Databases · head to head

RisingWave vs turbopuffer

RisingWave logo

RisingWave

Databases

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

From
Free
Rated
-
Full reviewWebsite
turbopuffer logo

turbopuffer

Databases

Closed-source vector and full-text search service built directly on object storage, with cold queries measured in seconds rather than milliseconds.

From
$16/month
Rated
-
Full reviewWebsite

The short version

  • Only RisingWave has a free tier, so it costs nothing to try first.
  • 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.; turbopuffer a cold namespace pays object storage latency on the first query, with a documented p90 around 1,214 ms on a million documents, so any interactive search box needs the data kept warm or the user waits about a second.
  • They diverge on capability: RisingWave covers SQL materialised views, turbopuffer covers Object storage architecture.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which RisingWave and turbopuffer actually diverge.

Attributes where RisingWave and turbopuffer differ
AttributeRisingWaveturbopuffer
Starting priceFree$16/month
Pricing modelPer RisingWave Unit hoursubscription
Free tierYesNo
PlatformsLinux, Docker, Kubernetes, CloudWeb

Identical on both: 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 turbopuffer

  • Object storage architecture
  • Namespaces
  • Vector search
  • Full-text search
  • Attribute filtering
  • Documented limits
  • Configurable consistency
  • Durable writes

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 turbopuffer
  • A fraud or risk team maintaining rolling counters and joins across event streams expressed as SQL viewsnot turbopuffer
  • A company doing Postgres CDC into a real-time denormalised view for search or servingnot turbopuffer
  • An analytics group that wants streaming results landed directly into Apache Iceberg without a separate writer jobnot turbopuffer

turbopuffer

  • A product with one search index per customer and thousands of customers, most of whose data is idle on any given daynot RisingWave
  • Very large corpora where holding every vector in memory is the dominant cost and occasional cold-query latency is acceptablenot RisingWave
  • Hybrid retrieval combining BM25 and vector search where running and synchronising two separate systems is the problem being solvednot RisingWave
  • Retrieval for agent and assistant products where indexes are created and destroyed frequently and per-index overhead must be near zeronot 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.

turbopuffer

  • A cold namespace pays object storage latency on the first query, with a documented p90 around 1,214 ms on a million documents, so any interactive search box needs the data kept warm or the user waits about a second.
  • Queries are eventually consistent by default, and after roughly 128 MiB of outstanding writes new data is invisible until indexed, which the vendor puts at tens of seconds for small namespaces and tens of minutes for large ones, so a bulk re-index is not immediately queryable.
  • It is closed source with no community edition, so single-tenant or bring-your-own-cloud deployment is a commercial negotiation rather than a deployment choice, and there is no path to running it yourself if the relationship ends.
  • Per-namespace ceilings, roughly 10,000 writes per second, 32 MB/s and 500 million documents per shard, mean a single enormous index has to be sharded across namespaces by your application rather than by the service.
  • It is a search engine, not a database: there are no joins, no cross-document transactions and no SQL, so it sits beside a primary datastore and keeping the two in step is work that belongs to you.

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

turbopuffer

$16/month
  • Launch$16/month
    • All database features
    • Multi-tenancy deployment
    • SOC2 & GDPR-ready DPA
  • Scale$256/month
    • Everything in Launch
    • HIPAA-ready BAA
    • Single Sign-On (SSO)
  • Enterprise$4096/month
    • Everything in Scale
    • Single-tenancy & BYOC deployment options
    • Private networking

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

  • You need object storage architecture.
  • You also want namespaces.
turbopuffer review

Questions people ask

Is RisingWave or turbopuffer better?
Neither clearly leads. RisingWave starts at Free and turbopuffer at $16/month, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, RisingWave or turbopuffer?
RisingWave has a free tier; the other does not. Paid plans start at Free for RisingWave and $16/month for turbopuffer.
Does RisingWave or turbopuffer run on more platforms?
RisingWave runs on Linux, Docker, Kubernetes, Cloud. turbopuffer runs on Web.
Can I use RisingWave for free?
Yes. RisingWave has a free tier, so you can try it without paying. turbopuffer starts at $16/month.
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 turbopuffer is typically brought in for.
What can RisingWave do that turbopuffer cannot?
RisingWave covers SQL materialised views, Postgres wire compatibility, Object storage state, Source connectors. turbopuffer covers Object storage architecture, Namespaces, Vector search, Full-text search.

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.

turbopuffer: Can I self-host turbopuffer?

There is no open source or community edition. Single-tenant and bring-your-own-cloud deployments exist as commercial arrangements, but there is no way to run it independently of the vendor.

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.

turbopuffer: How fast is it really?

Warm queries perform comparably to in-memory search engines. Cold queries, where data is not cached, have a documented p90 around 1,214 ms on a million documents. Write p90 is around 248 ms for a 512 KB upsert because writes go straight to object storage.

RisingWave: Does it replace Flink?

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

turbopuffer: Is it consistent?

Eventually consistent by default, with the vendor reporting that over 99.8% of queries return consistent data. Strong consistency can be requested per query at a latency cost. Large write bursts have a longer visibility delay while indexing catches up.

RisingWave: Can I query it like Postgres?

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

turbopuffer: What is it best at?

Large numbers of namespaces where most are idle. The architecture makes cold data cheap to keep, which is exactly the shape of a multi-tenant product with a long tail of inactive customers.

turbopuffer: What are the hard limits?

Up to 128 billion documents and 256 TB per namespace, 500 million documents per shard, 64 MiB per document, 10,752 dense vector dimensions, roughly 10,000 writes per second per namespace and a maximum result set of 10,000.

Share

Related pages

More on RisingWave

More on turbopuffer

Keep looking

Other head to heads