Automation Integration · head to head
Orkes vs RisingWave

Orkes
Automation Integration
Commercial Conductor, now the maintainer of the workflow engine Netflix archived
- From
- Free
- Free plan
- Yes

RisingWave
Databases
Streaming database that maintains incremental materialised views in SQL instead of Flink jobs
- From
- Free
- Free plan
- Yes
The short version
- Orkes is free; RisingWave starts at $0.227/mo.
- Only Orkes lists JSON workflow definitions; only RisingWave lists SQL materialised views.
- Prices and features on this page were last checked on 31 August 2026.
How do Orkes and RisingWave differ?
Orkes and RisingWave differ on pricing model and category. Only the attributes on which Orkes and RisingWave actually diverge.
| Attribute | Orkes | RisingWave |
|---|---|---|
| Pricing model | Quote | Per RisingWave Unit hour |
| Category | Automation Integration | Databases |
Identical on both: starting price (Free), free tier (Yes), platforms (Linux, Self-hosted, Web).
Which features does each one have?
They share no listed features; 8 appear only for Orkes and 8 only for RisingWave. 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 Orkes
- JSON workflow definitions
- Polyglot workers
- Visual workflow builder
- AI and LLM tasks
- Human tasks
- Event handlers
- RBAC and secrets
- Hosted or self-hosted
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 is each one used for?
The jobs each tool is most often brought in to do.
Orkes
- A microservices estate that needs orchestration across services written in different languages without a shared SDKnot RisingWave
- A team already running Conductor OSS that wants a supported distribution now that Netflix has stopped maintaining itnot RisingWave
- An AI platform composing agent steps, model calls and vector lookups as versioned workflow definitionsnot RisingWave
- A business process needing human approval steps interleaved with automated service callsnot RisingWave
RisingWave
- A team with Kafka topics that needs continuously fresh aggregates for a dashboard without standing up a Flink clusternot Orkes
- A fraud or risk team maintaining rolling counters and joins across event streams expressed as SQL viewsnot Orkes
- A company doing Postgres CDC into a real-time denormalised view for search or servingnot Orkes
- An analytics group that wants streaming results landed directly into Apache Iceberg without a separate writer jobnot Orkes
Where do Orkes and RisingWave fall short?
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Orkes
- Netflix archived the Conductor repository in December 2023 and Orkes took over maintenance, so the large-company backing that justified many original adoptions no longer exists
- Enterprise pricing is entirely unpublished, and the only free option is explicitly a prototyping sandbox whose limits can change at any time, so there is no supported low-cost entry point
- Self-hosting Conductor OSS in production means operating the engine plus its persistence and indexing dependencies, typically Postgres or Cassandra with Elasticsearch, which is a substantial platform commitment
- JSON workflow definitions are language agnostic but verbose and awkward to test, and teams accustomed to defining workflows in code find them a step backwards in developer experience
- Orkes is a small company whose commercial future is tied to a single open source project it also maintains, which concentrates both vendor and project risk in the same place
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
How much do Orkes and RisingWave cost?
Orkes is free to use; RisingWave has a free plan, with paid plans from $0.227/mo. Plan by plan below, from each vendor's own pricing page.
Orkes
Free- Developer EditionFree
- All Conductor OSS features plus enterprise capabilities
- Sandbox for prototyping only
- Rate limits and resources may change without notice
- EnterpriseOn request
- Availability SLA up to 99.99%
- Orkes-hosted or customer-hosted deployment
- Dedicated technical account manager
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 ProOn request
- No core limit
- Bring your own cloud option
- Premium features included
- Self-managed EnterpriseOn request
- On premises or Kubernetes
- Premium features unlocked by licence
- Annual contract with SLA
Which should you pick?
Choose Orkes if
- You need json workflow definitions.
- You want to start without paying.
- You work on Linux, Self-hosted, Web.
- You also want polyglot workers.
Choose RisingWave if
- You need sql materialised views.
- You want to start without paying.
- You work on Linux, Self-hosted, Web.
- You also want postgres wire compatibility.
Questions people ask
- Is Orkes or RisingWave better?
- Neither clearly leads. Orkes 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, Orkes or RisingWave?
- Orkes starts at Free and RisingWave at Free.
- Does Orkes or RisingWave run on more platforms?
- Both run on Linux, Self-hosted, Web, so platform support will not decide this one for you.
- Can I use Orkes for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is Orkes best used for?
- Orkes is most often used for a microservices estate that needs orchestration across services written in different languages without a shared sdk, a team already running conductor oss that wants a supported distribution now that netflix has stopped maintaining it, an ai platform composing agent steps, model calls and vector lookups as versioned workflow definitions, a business process needing human approval steps interleaved with automated service calls. Of those, a microservices estate that needs orchestration across services written in different languages without a shared sdk and a team already running conductor oss that wants a supported distribution now that netflix has stopped maintaining it are not what RisingWave is typically brought in for.
- What can Orkes do that RisingWave cannot?
- Orkes covers JSON workflow definitions, Polyglot workers, Visual workflow builder, AI and LLM tasks. RisingWave covers SQL materialised views, Postgres wire compatibility, Object storage state, Source connectors.
Answered from the vendors’ own pages
Orkes: Does Netflix still maintain Conductor?
No. Netflix archived its repository in December 2023. The open source project continues at conductor-oss under Apache 2.0, maintained by Orkes.
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.
Orkes: Is there a free production tier?
No. The Developer Edition is a sandbox that the vendor states is unsuitable for production. Self-hosting Conductor OSS is the free production route.
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.
Orkes: What does Enterprise cost?
Nothing is published; it is quoted by deployment and support requirements.
RisingWave: Does it replace Flink?
For SQL-expressible transformations, often yes. For custom stateful processing and complex event handling, no.
Orkes: How does it compare with Temporal?
Conductor uses declarative JSON workflow definitions and external workers; Temporal defines workflows in code. Temporal has the larger community.
RisingWave: 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
- Orkes vs Temporal
- Orkes vs n8n
- Orkes vs Hatchet
- Orkes vs Autonoly
- Orkes vs Meltano
- Orkes vs Camunda
- Orkes vs Flowable
- Orkes vs Nango
- Orkes vs Airbyte
- Orkes vs Windmill
- Orkes vs Activiti
- Orkes vs jBPM
- Orkes vs Kogito
- Orkes vs Letta
- Orkes vs Lytics
- Orkes vs Polytomic
- Orkes vs Relevance AI
- Orkes vs Salesforce Flows
- Orkes vs Apache Flink
- Orkes vs Materialize
- Orkes vs Tinybird
- Orkes vs Redpanda
- Orkes vs Timeplus
- Orkes vs Estuary
- Orkes vs Instaclustr
- Orkes vs Fivetran HVR
- Orkes vs Trino
- Orkes vs TiDB
- Orkes vs Xata
- Orkes vs Airtable
- Orkes vs Cockroach Labs
- Orkes vs PostgreSQL
- Orkes vs RabbitMQ
- Orkes vs Amazon Aurora
- Orkes vs ClickHouse
- Orkes vs Apache Kafka
- RisingWave vs Temporal
- RisingWave vs n8n
- RisingWave vs Hatchet
- RisingWave vs Autonoly
- RisingWave vs Meltano
- RisingWave vs Camunda
- RisingWave vs Flowable
- RisingWave vs Nango
- RisingWave vs Airbyte
- RisingWave vs Windmill
- RisingWave vs Activiti
- RisingWave vs jBPM
- RisingWave vs Kogito
- RisingWave vs Letta
- RisingWave vs Lytics
- RisingWave vs Polytomic
- RisingWave vs Relevance AI
- RisingWave vs Salesforce Flows
- 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 Trino
- RisingWave vs TiDB
- RisingWave vs Xata
- RisingWave vs Airtable
- RisingWave vs Cockroach Labs
- RisingWave vs PostgreSQL
- RisingWave vs RabbitMQ
- RisingWave vs Amazon Aurora
- RisingWave vs ClickHouse
- RisingWave vs Apache Kafka
