Softwr

Databases · head to head

ClickHouse vs Dgraph

ClickHouse logo

ClickHouse

Databases

Fast open-source column-oriented database for real-time analytics

From
Free
Rated
-
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
Rated
-

The short version

  • Each has a real cost: ClickHouse limited multi-row atomic transactions and expensive UPDATE/DELETE operations unsuitable for transactional systems; 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.
  • They diverge on capability: ClickHouse covers Column-oriented Storage, Dgraph covers Apache 2.0 licence.
  • Prices and features above were last checked on 30 August 2026.

Where they differ

Only the attributes on which ClickHouse and Dgraph actually diverge.

Attributes where ClickHouse and Dgraph differ
AttributeClickHouseDgraph
Pricing modelUnknownfreemium
PlatformsLinux, macOS, Windows (via Docker)Linux, Mac, Docker, Web
Founded20212016

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 ClickHouse

  • Column-oriented Storage
  • Real-time Analytics
  • SQL Support
  • Linear Scalability
  • Data Compression
  • Vectorized Query Execution
  • Approximate Calculations
  • Kafka

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

What people use each for

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

ClickHouse

  • Business intelligencenot Dgraph
  • Data warehousingnot Dgraph
  • Real-time analyticsnot Dgraph
  • Reportingnot Dgraph
  • Machine learningnot Dgraph

Dgraph

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

Where each one falls short

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

ClickHouse

  • Limited multi-row atomic transactions and expensive UPDATE/DELETE operations unsuitable for transactional systems
  • Requires upfront schema design discipline with MergeTree engine choices and sort/partition keys
  • Experimental vector search support, not production-ready for vector operations
  • Different query syntax from standard SQL requiring migration planning
  • Limited JOIN capabilities compared to traditional relational databases
  • Migration complexity with 2-4 weeks estimated for data type mapping and query translation

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.

Pricing, plan by plan

ClickHouse

Free

No published plan breakdown. See the ClickHouse review.

Dgraph

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

Which should you pick?

Choose ClickHouse if

  • You need column-oriented storage.
  • You want to start without paying.
  • You work on Linux, macOS, Windows (via Docker).
  • You also want real-time analytics.

Choose Dgraph if

  • You need apache 2.0 licence.
  • You want to start without paying.
  • You work on Linux, Mac, Docker, Web.
  • You also want generated graphql api.

Questions people ask

Is ClickHouse or Dgraph better?
Neither clearly leads. ClickHouse starts at Free and Dgraph at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, ClickHouse or Dgraph?
ClickHouse starts at Free and Dgraph at Free.
Does ClickHouse or Dgraph run on more platforms?
ClickHouse runs on Linux, macOS, Windows (via Docker). Dgraph runs on Linux, Mac, Docker, Web.
Can I use ClickHouse for free?
Both have a free tier, so you can try either at no cost before committing.
What is ClickHouse best used for?
ClickHouse is most often used for business intelligence, data warehousing, real-time analytics, reporting. Of those, business intelligence and data warehousing are not what Dgraph is typically brought in for.
What can ClickHouse do that Dgraph cannot?
ClickHouse covers Column-oriented Storage, Real-time Analytics, SQL Support, Linear Scalability. Dgraph covers Apache 2.0 licence, Generated GraphQL API, DQL query language, Predicate sharding.

Answered from the vendors’ own pages

ClickHouse: What is ClickHouse best used for?

ClickHouse is optimized for analytical workloads on large datasets. It excels at fast aggregations and queries, being 10-100x faster than PostgreSQL on large aggregations.

Source
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.

ClickHouse: Does ClickHouse support transactions?

ClickHouse has limited transaction support and expensive UPDATE/DELETE operations. It is not suitable for transactional workloads requiring strict ACID guarantees.

Source
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.

ClickHouse: How does ClickHouse compare to PostgreSQL?

ClickHouse is 10-100x faster for analytics but PostgreSQL is better for transactional workloads. Many teams use both: PostgreSQL for writes via MaterializedPostgreSQL replication to ClickHouse for analytics.

Source
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.

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.

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