Softwr

Databases · head to head

Dgraph vs Orkes

Dgraph logo

Dgraph

Databases

Apache 2.0 distributed graph database written in Go, maintained by Hypermode, queried through GraphQL or its own DQL language.

From
Free
Free plan
Yes
Orkes logo

Orkes

Automation Integration

Commercial Conductor, now the maintainer of the workflow engine Netflix archived

From
Free
Free plan
Yes

The short version

  • Orkes is free; Dgraph starts at $39/mo.
  • Only Dgraph lists apache 2.0 licence; only Orkes lists JSON workflow definitions.
  • Prices and features on this page were last checked on 13 November 2026.

How do Dgraph and Orkes differ?

Dgraph and Orkes differ on pricing model (Freemium against Quote), platforms and category. Only the attributes on which Dgraph and Orkes actually diverge.

Attributes where Dgraph and Orkes differ
AttributeDgraphOrkes
Pricing modelFreemiumQuote
PlatformsLinux, macOS, Self-hosted, WebLinux, Self-hosted, Web
CategoryDatabasesAutomation Integration

Identical on both: starting price (Free), free tier (Yes).

Not yet recorded: founded for Orkes.

Which features does each one have?

They share no listed features; 10 appear only for Dgraph and 8 only for Orkes. 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 Dgraph

  • Apache 2.0 licence
  • Generated GraphQL API
  • DQL query language
  • Predicate sharding
  • Raft replication
  • Distributed ACID transactions
  • Written in Go
  • Full-text and geo indexing

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

What is each one used for?

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

Dgraph

  • An application whose core data is a graph, such as permissions, social connections or product relationships, where the frontend already consumes GraphQLnot Orkes
  • A knowledge graph that outgrew a single machine and needs storage distributed across nodes without a per-core licence negotiationnot Orkes
  • Recommendation or fraud-detection features that traverse several hops at request time, where a relational join chain has become the bottlenecknot Orkes
  • Teams that want a graph database they can read, fork and self-host under a permissive licence rather than a source-available onenot Orkes

Orkes

  • A microservices estate that needs orchestration across services written in different languages without a shared SDKnot Dgraph
  • A team already running Conductor OSS that wants a supported distribution now that Netflix has stopped maintaining itnot Dgraph
  • An AI platform composing agent steps, model calls and vector lookups as versioned workflow definitionsnot Dgraph
  • A business process needing human approval steps interleaved with automated service callsnot Dgraph

Where do Dgraph and Orkes fall short?

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

Dgraph

  • Sharding is by predicate, so a single very hot predicate lives entirely in one Raft group and cannot be split further; adding nodes does not relieve it and the fix is a data model change
  • Stewardship passed from Dgraph Labs to Hypermode after the original company stopped operating independently, so anyone building on it is betting on a second custodian rather than on the original team's roadmap
  • The GraphQL layer is generated and opinionated, so anything it does not express drops you into DQL, which is a second language your team must learn and which no other database speaks
  • The community is a fraction of Neo4j's, so operational answers, tuning experience, hiring and third-party tooling are all thinner, and unusual failure modes in a Zero and Alpha cluster leave you reading source rather than a forum
  • There is no portable graph standard to migrate to; Cypher, Gremlin and SPARQL are all different query models, so the schema and every query is a rewrite if you later leave, and that cost grows with the application

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

How much do Dgraph and Orkes cost?

Dgraph has a free plan, with paid plans from $39/mo; Orkes is free to use. Plan by plan below, from each vendor's own pricing page.

Dgraph

Free
  • CommunityFree
    • Native GraphQL
    • Graph queries
    • Full-text search
  • Cloud$39/mo
    • Managed service
    • Auto-scaling
    • Enterprise support

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

Which should you pick?

Choose Dgraph if

  • You need apache 2.0 licence.
  • You want to start without paying.
  • You work on Linux, macOS, Self-hosted, Web.
  • You also want generated graphql api.

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.

Questions people ask

Is Dgraph or Orkes better?
Neither clearly leads. Dgraph starts at Free and Orkes at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Dgraph or Orkes?
Dgraph starts at Free and Orkes at Free.
Does Dgraph or Orkes run on more platforms?
Dgraph runs on Linux, macOS, Self-hosted, Web. Orkes runs on Linux, Self-hosted, Web.
Can I use Dgraph for free?
Both have a free tier, so you can try either at no cost before committing.
What is Dgraph best used for?
Dgraph is most often used for an application whose core data is a graph, such as permissions, social connections or product relationships, where the frontend already consumes graphql, a knowledge graph that outgrew a single machine and needs storage distributed across nodes without a per-core licence negotiation, recommendation or fraud-detection features that traverse several hops at request time, where a relational join chain has become the bottleneck, teams that want a graph database they can read, fork and self-host under a permissive licence rather than a source-available one. Of those, an application whose core data is a graph, such as permissions, social connections or product relationships, where the frontend already consumes graphql and a knowledge graph that outgrew a single machine and needs storage distributed across nodes without a per-core licence negotiation are not what Orkes is typically brought in for.
What can Dgraph do that Orkes cannot?
Dgraph covers Apache 2.0 licence, Generated GraphQL API, DQL query language, Predicate sharding. Orkes covers JSON workflow definitions, Polyglot workers, Visual workflow builder, AI and LLM tasks.

Answered from the vendors’ own pages

Dgraph: Is Dgraph open source?

Yes. The current repository is Apache 2.0, which is a permissive OSI licence, and the project is at v25 under Hypermode's maintenance.

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.

Dgraph: Is it really GraphQL?

It serves a generated GraphQL API, which is real GraphQL for clients. Its native language, DQL, resembles GraphQL syntactically but is Dgraph's own language and is not the GraphQL specification.

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.

Dgraph: How does it compare to Neo4j?

Neo4j has the larger ecosystem, Cypher, and far more operational precedent. Dgraph distributes storage across nodes by default and gives you a GraphQL endpoint without writing resolvers. The choice usually turns on whether you need horizontal scale and a GraphQL surface more than you need ecosystem depth.

Orkes: What does Enterprise cost?

Nothing is published; it is quoted by deployment and support requirements.

Dgraph: What does a production cluster look like?

At minimum a set of Zero nodes for coordination and a replicated set of Alpha nodes for data, typically three of each for fault tolerance, which is a meaningfully larger operational footprint than a single graph server.

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.

Dgraph: Who maintains it now?

Hypermode. Dgraph Labs, the original company, no longer operates it, and that change of custodian is the main non-technical risk to weigh.

Share

Related pages

Other head to heads