Softwr

Databases · head to head

Dgraph vs Restate

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
Visit DgraphFull review
Restate logo

Restate

Developer Tools

Durable execution engine in Rust with a free tier and low-latency workflows

From
Free
Free plan
Yes
Visit RestateFull review

The short version

  • Free plans on both; paid from $39/mo and $300/mo.
  • Only Dgraph lists apache 2.0 licence; only Restate lists durable execution.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Dgraph and Restate actually diverge.

Attributes where Dgraph and Restate differ
AttributeDgraphRestate
Pricing modelFreemiumPer month by durable action count
PlatformsLinux, macOS, Self-hosted, WebLinux, macOS, Web
CategoryDatabasesDeveloper Tools

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

Not yet recorded: founded for Restate.

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 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 Restate

  • Durable execution
  • Virtual objects
  • Single binary runtime
  • Multi-language SDKs
  • Workflows and sagas
  • Restate Cloud

What people use each 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 Restate
  • A knowledge graph that outgrew a single machine and needs storage distributed across nodes without a per-core licence negotiationnot Restate
  • Recommendation or fraud-detection features that traverse several hops at request time, where a relational join chain has become the bottlenecknot Restate
  • Teams that want a graph database they can read, fork and self-host under a permissive licence rather than a source-available onenot Restate

Restate

  • Payment or order flows where a crash between two external API calls must not double-charge or lose the ordernot Dgraph
  • AI agent loops that call tools over minutes or hours and must survive a deployment mid-runnot Dgraph
  • Replacing hand-rolled retry, idempotency key and outbox code across a set of microservicesnot Dgraph
  • A small team that wants durable workflows without operating a Temporal cluster and its databasenot Dgraph

Where each one falls 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

Restate

  • The runtime is under a Business Source Licence rather than an open source licence, so building a competing managed offering on it is prohibited and some procurement functions will reject it on licence grounds alone
  • Restate Cloud jumps from a free fifty thousand actions straight to 300 US dollars a month for twenty million, so a workload sitting at a few hundred thousand actions pays enterprise-shaped money for hobby-shaped volume
  • It is a young project against Temporal’s established base, so hiring engineers who already know it is unrealistic and the answer to most questions is in the docs rather than on Stack Overflow
  • The programming model requires structuring code around durable handlers and virtual objects, which is a genuine rewrite for existing services rather than a library you add
  • The single-binary simplicity that makes small deployments cheap also means fewer operational knobs at very large scale than a system designed as separable components

Pricing, plan by plan

Dgraph

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

Restate

Free
  • FreeFree
    • Fifty thousand durable actions per month
    • No credit card required
    • Community support
  • Starter$300/mo
    • Twenty million actions per month
    • Two hundred actions per second, bursting to one thousand
    • Twenty GB storage
  • Pro$1,000/mo
    • Fifty million actions per month
    • Five hundred actions per second, bursting to two thousand
    • Fifty GB storage
  • EnterpriseOn request
    • Negotiated volume
    • Twenty-four seven P0 support
    • 99.99 per cent SLA

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.
Dgraph review

Choose Restate if

  • You need durable execution.
  • You want to start without paying.
  • You work on Linux, macOS, Web.
  • You also want virtual objects.
Restate review

Questions people ask

Is Dgraph or Restate better?
Neither clearly leads. Dgraph starts at Free and Restate at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Dgraph or Restate?
Dgraph starts at Free and Restate at Free.
Does Dgraph or Restate run on more platforms?
Dgraph runs on Linux, macOS, Self-hosted, Web. Restate runs on Linux, macOS, 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 Restate is typically brought in for.
What can Dgraph do that Restate cannot?
Dgraph covers Apache 2.0 licence, Generated GraphQL API, DQL query language, Predicate sharding. Restate covers Durable execution, Virtual objects, Single binary runtime, Multi-language SDKs.

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.

Restate: Is Restate open source?

The SDKs are MIT. The runtime is under a Business Source Licence, which permits self-hosting but not offering it as a competing service.

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.

Restate: How does it compare with Temporal?

Same problem, different shape: one Rust binary with embedded storage instead of a server plus database plus workers, and lower per-step latency.

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.

Restate: Is there a free tier?

Yes, fifty thousand durable actions a month on Restate Cloud with no card required.

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.

Restate: Which languages are supported?

TypeScript, Java, Kotlin, Go, Python and Rust.

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

More on Dgraph

More on Restate

Keep looking

Other head to heads