Softwr

Databases · head to head

Dgraph vs Qovery

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
Qovery logo

Qovery

Cloud

Deployment platform that provisions and operates Kubernetes inside your own cloud account

From
On request
Free plan
No

The short version

  • Dgraph starts at $39/mo; Qovery prices on request.
  • Only Dgraph lists apache 2.0 licence; only Qovery lists bring your own cloud.
  • Prices and features on this page were last checked on 13 November 2026.

How do Dgraph and Qovery differ?

Dgraph and Qovery differ on starting price (Free against On request), pricing model (Freemium against Quote) and free tier (Yes against No). Only the attributes on which Dgraph and Qovery actually diverge.

Attributes where Dgraph and Qovery differ
AttributeDgraphQovery
Starting priceFreeOn request
Pricing modelFreemiumQuote
Free tierYesNo
PlatformsLinux, macOS, Self-hosted, WebWeb, API, Self-hosted
CategoryDatabasesCloud

Not yet recorded: founded for Qovery.

Which features does each one have?

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

  • Bring your own cloud
  • Preview environments
  • Cluster lifecycle
  • Terraform provider
  • MCP server
  • Policy as code

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

Qovery

  • A regulated business that must keep application data inside its own AWS account but has nobody to build a deployment platformnot Dgraph
  • Giving twenty engineers preview environments per pull request without writing and maintaining Terraform and Helm by handnot Dgraph
  • Standardising deployment across AWS and GCP when acquisitions have left the organisation on two cloudsnot Dgraph
  • Replacing a managed platform when data residency rules put every hosted option out of reachnot Dgraph

Where do Dgraph and Qovery 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

Qovery

  • No plan publishes a price, deployment minute overage rates are not disclosed, and there is a 14 day trial rather than a free tier, so you cannot budget or compare against alternatives without going through sales
  • The GPL-3.0 engine and console do not constitute a self-hostable product, because the control plane and API are closed and the self-hosted option is gated behind Enterprise, so the open licence gives you no exit if the company changes direction
  • Qovery provisions managed Kubernetes into your account, which means the cloud bill sits on top of the licence and Qovery initiates control plane and ingress controller upgrades on infrastructure your team is accountable for
  • The company repositioned to agentic infrastructure in June 2026 and now ships a deployment platform, a browser development portal and autonomous coding agents concurrently, so a buyer of the deployment product is not at the centre of the roadmap
  • Team and Business are capped at two and three connected clusters with fixed 4 vCPU CI runners and no single sign-on on Team, which pushes teams of moderate size onto quoted Enterprise pricing earlier than the plan names imply

How much do Dgraph and Qovery cost?

Dgraph has a free plan, with paid plans from $39/mo; Qovery is priced on request. 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

Qovery

On request
  • TeamOn request
    • Billed on usage with no published rate card
    • 10 users, up to 100 environments, 2 connected clusters
    • 5,000 deployment minutes and 7 day audit logs
  • BusinessOn request
    • Billed on usage with no published rate card
    • 20 users, up to 250 environments, 3 connected clusters
    • 10,000 deployment minutes and 30 day audit logs
  • EnterpriseOn request
    • Custom users, environments and clusters
    • Self-hosted or air-gapped control plane
    • On-premises and bring-your-own-Kubernetes

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

  • You need bring your own cloud.
  • You work on Web, API, Self-hosted.
  • You also want preview environments.

Questions people ask

Is Dgraph or Qovery better?
Neither clearly leads. Dgraph starts at Free and Qovery at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Dgraph or Qovery?
Dgraph has a free tier; the other does not. Paid plans start at Free for Dgraph and On request for Qovery.
Does Dgraph or Qovery run on more platforms?
Dgraph runs on Linux, macOS, Self-hosted, Web. Qovery runs on Web, API, Self-hosted.
Can I use Dgraph for free?
Yes. Dgraph has a free tier, so you can try it without paying. Qovery starts at On request.
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 Qovery is typically brought in for.
What can Dgraph do that Qovery cannot?
Dgraph covers Apache 2.0 licence, Generated GraphQL API, DQL query language, Predicate sharding. Qovery covers Bring your own cloud, Preview environments, Cluster lifecycle, Terraform provider.

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.

Qovery: Does Qovery run my applications on its own servers?

No. It provisions and operates Kubernetes inside your AWS, GCP, Azure or Scaleway account, so compute and data stay with your cloud provider and that bill is entirely separate from the Qovery licence.

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.

Qovery: Can I self-host Qovery?

Only on Enterprise. The deployment engine and console are GPL-3.0, but the control plane is closed source and the self-hosted and air-gapped deployments are commercial Enterprise features.

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.

Qovery: What does it cost?

Qovery does not publish a rate card. Team and Business are billed on usage and quoted through sales, and Enterprise is fully custom. There is a 14 day trial 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.

Qovery: What survives if I stop paying?

The Kubernetes cluster and the workloads keep running in your cloud account, but you lose the console, the deployment pipeline, preview environments and every process built on top of them.

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