Databases · head to head
RisingWave vs SurrealDB

RisingWave
Databases
Streaming database that maintains incremental materialised views in SQL instead of Flink jobs
- From
- Free
- Rated
- -

SurrealDB
Databases
Multi-model database combining documents, graphs, vectors and time-series
- From
- Free
- Rated
- -
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.; SurrealDB the listed $0.192/node/hr Scale pricing lacks transparent higher-tier rates, requiring a sales conversation for full production sizing.
- They diverge on capability: RisingWave covers SQL materialised views, SurrealDB covers Multi-model engine.
- Prices and features above were last checked on 31 August 2026.
Where they differ
Only the attributes on which RisingWave and SurrealDB actually diverge.
| Attribute | RisingWave | SurrealDB |
|---|---|---|
| Pricing model | Per RisingWave Unit hour | usage-based |
| Platforms | Linux, Docker, Kubernetes, Cloud | web, api, windows, mac, linux |
| Founded | Unknown | 2022 |
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 SurrealDB
- Multi-model engine
- ACID transactions
- Hybrid retrieval
- Horizontal scaling
- Multi-region disaster recovery
- FIPS-compliant cryptography
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 SurrealDB
- A fraud or risk team maintaining rolling counters and joins across event streams expressed as SQL viewsnot SurrealDB
- A company doing Postgres CDC into a real-time denormalised view for search or servingnot SurrealDB
- An analytics group that wants streaming results landed directly into Apache Iceberg without a separate writer jobnot SurrealDB
SurrealDB
- AI agent memory and retrieval-augmented generationnot RisingWave
- Applications needing documents, graphs and vectors in one databasenot RisingWave
- Knowledge graph construction from unstructured datanot RisingWave
- Regulated workloads requiring SOC2/ISO27001/HIPAA-eligible hostingnot 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.
SurrealDB
- The listed $0.192/node/hr Scale pricing lacks transparent higher-tier rates, requiring a sales conversation for full production sizing.
- As a newer multi-model database, it has a smaller ecosystem of drivers, ORMs and community tooling than established single-model databases.
- HIPAA compliance is only available as an Enterprise add-on rather than included in standard paid tiers.
- Combining multiple data models in one engine can add query-planning complexity compared to purpose-built single-model databases.
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
SurrealDB
Free- StartFree
- 1 free instance, then from $0.021/hr
- 1GB storage free forever
- Vertical scaling to terabytes
- Scale$0.192/month
- $0.192/node/hr
- Production-grade fault tolerance
- Horizontal scaling to petabytes
- Enterprise$undefined/month
- Self-hosted, custom pricing
- Clustered fault-tolerant deployments
- FIPS-compliant cryptography
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.
Choose SurrealDB if
- You need multi-model engine.
- You want to start without paying.
- You work on web, api, windows, mac, linux.
- You also want acid transactions.
Questions people ask
- Is RisingWave or SurrealDB better?
- Neither clearly leads. RisingWave starts at Free and SurrealDB at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, RisingWave or SurrealDB?
- RisingWave starts at Free and SurrealDB at Free.
- Does RisingWave or SurrealDB run on more platforms?
- RisingWave runs on Linux, Docker, Kubernetes, Cloud. SurrealDB runs on web, api, windows, mac, linux.
- 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 SurrealDB is typically brought in for.
- What can RisingWave do that SurrealDB cannot?
- RisingWave covers SQL materialised views, Postgres wire compatibility, Object storage state, Source connectors. SurrealDB covers Multi-model engine, ACID transactions, Hybrid retrieval, Horizontal scaling.
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.
SurrealDB: What does SurrealDB cost?
SurrealDB Cloud's Start plan is free with one free instance (then from $0.021/hr), the Scale plan runs $0.192/node/hr for production workloads, and Enterprise self-hosted deployments use custom pricing.
SourceRisingWave: 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.
SurrealDB: Is there a free plan and what are its limits?
Yes, the Start plan includes one free instance with 1GB of storage free forever and 1GB of outbound data transfer per month, aimed at prototypes and development.
SourceRisingWave: Does it replace Flink?
For SQL-expressible transformations, often yes. For custom stateful processing and complex event handling, no.
SurrealDB: How is billing handled?
Customers are invoiced monthly based on actual usage in a pay-as-you-go model with no long-term commitments, though commitment-based discounts are available.
SourceRisingWave: Can I query it like Postgres?
Yes over the Postgres wire protocol, but it is an analytical streaming engine, not a transactional database.
Related pages
Other head to heads
- RisingWave vs Apache Flink
- RisingWave vs Materialize
- RisingWave vs Tinybird
- RisingWave vs Redpanda
- RisingWave vs Timeplus
- RisingWave vs Estuary
- RisingWave vs Instaclustr
- RisingWave vs Fivetran HVR
- RisingWave vs TiDB
- RisingWave vs Xata
- RisingWave vs Amazon Aurora
- RisingWave vs SQLite
- RisingWave vs StarRocks
- RisingWave vs Teradata
- RisingWave vs TIBCO Enterprise Message Service
- RisingWave vs Apache Kafka
- RisingWave vs Turso
- RisingWave vs MotherDuck
- RisingWave vs Vespa
- RisingWave vs Zilliz
- RisingWave vs ArangoDB
- RisingWave vs RavenDB
- RisingWave vs DuckDB
- RisingWave vs Oracle Database
- RisingWave vs TimescaleDB
- RisingWave vs QuestDB
- RisingWave vs CosmosDB
- RisingWave vs DataGrip
- RisingWave vs Firebolt
- RisingWave vs Google Cloud SQL
- RisingWave vs Microsoft SQL Server
- SurrealDB vs Apache Flink
- SurrealDB vs Materialize
- SurrealDB vs Tinybird
- SurrealDB vs Redpanda
- SurrealDB vs Timeplus
- SurrealDB vs Estuary
- SurrealDB vs Instaclustr
- SurrealDB vs Fivetran HVR
- SurrealDB vs TiDB
- SurrealDB vs Xata
- SurrealDB vs Amazon Aurora
- SurrealDB vs SQLite
- SurrealDB vs StarRocks
- SurrealDB vs Teradata
- SurrealDB vs TIBCO Enterprise Message Service
- SurrealDB vs Apache Kafka
- SurrealDB vs Turso
- SurrealDB vs MotherDuck
- SurrealDB vs Vespa
- SurrealDB vs Zilliz
- SurrealDB vs ArangoDB
- SurrealDB vs RavenDB
- SurrealDB vs DuckDB
- SurrealDB vs Oracle Database
- SurrealDB vs TimescaleDB
- SurrealDB vs QuestDB
- SurrealDB vs CosmosDB
- SurrealDB vs DataGrip
- SurrealDB vs Firebolt
- SurrealDB vs Google Cloud SQL
- SurrealDB vs Microsoft SQL Server
