Softwr

Databases · head to head

Dgraph vs Timeplus

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
-
Full reviewWebsite
Timeplus logo

Timeplus

Databases

Streaming SQL engine built on ClickHouse internals, shipping as one small binary

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: 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.; Timeplus proton, the free version, is single-node by design, so any requirement for high availability or horizontal scale forces the commercial licence; the open source edition is a trial in practical terms.
  • They diverge on capability: Dgraph covers Apache 2.0 licence, Timeplus covers Streaming SQL.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Dgraph and Timeplus actually diverge.

Attributes where Dgraph and Timeplus differ
AttributeDgraphTimeplus
Pricing modelfreemiumPer month for cloud, quoted for self-hosted
PlatformsLinux, Mac, Docker, WebLinux, macOS, Docker, Kubernetes, Web
Founded2016Unknown

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

  • Streaming SQL
  • Unified streaming and historical
  • ClickHouse-based engine
  • Single binary deployment
  • External streams
  • Materialised views

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

Timeplus

  • Real-time alerting on Kafka topics where standing up a Flink cluster is more work than the use case justifiesnot Dgraph
  • Fraud or anomaly detection that must join a live event stream against recent history in one querynot Dgraph
  • Streaming ETL from Kafka or MySQL change data capture into ClickHouse without writing Javanot Dgraph
  • A small data team that needs continuous aggregation but has no platform engineers to operate JVM infrastructurenot 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.

Timeplus

  • Proton, the free version, is single-node by design, so any requirement for high availability or horizontal scale forces the commercial licence; the open source edition is a trial in practical terms.
  • It is a young project against Apache Flink’s decade of production history, so the hiring pool, the connector library and the body of known failure modes are all much smaller.
  • Inheriting ClickHouse internals also inherits ClickHouse constraints: memory-hungry queries, awkward updates and a SQL dialect that is not portable to other engines.
  • Exactly-once semantics and state recovery guarantees are less battle-tested than Flink checkpointing, which matters if the pipeline moves money.
  • Cloud pricing is by provisioned instance size rather than usage, so a bursty workload pays for peak capacity around the clock or has to be resized by hand.

Pricing, plan by plan

Dgraph

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

Timeplus

Free
  • Timeplus ProtonFree
    • Apache 2.0 licence
    • Single node only
    • Full streaming SQL engine
  • Timeplus Cloud$199/month
    • One to thirty-two CPUs
    • 4 GB to 128 GB memory
    • From 250 GB SSD storage
  • Self-hosted or BYOC$undefined/year
    • Multi-node clustering
    • Kubernetes or bare metal
    • Customisable compute and storage

Which should you pick?

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

Choose Timeplus if

  • You need streaming sql.
  • You want to start without paying.
  • You work on Linux, macOS, Docker, Kubernetes, Web.
  • You also want unified streaming and historical.
Timeplus review

Questions people ask

Is Dgraph or Timeplus better?
Neither clearly leads. Dgraph starts at Free and Timeplus at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Dgraph or Timeplus?
Dgraph starts at Free and Timeplus at Free.
Does Dgraph or Timeplus run on more platforms?
Dgraph runs on Linux, Mac, Docker, Web. Timeplus runs on Linux, macOS, Docker, Kubernetes, 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 Timeplus is typically brought in for.
What can Dgraph do that Timeplus cannot?
Dgraph covers Apache 2.0 licence, Generated GraphQL API, DQL query language, Predicate sharding. Timeplus covers Streaming SQL, Unified streaming and historical, ClickHouse-based engine, Single binary deployment.

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.

Timeplus: Is Timeplus open source?

The core engine, Timeplus Proton, is Apache 2.0. Timeplus Enterprise and Cloud are commercial.

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.

Timeplus: What is the difference from Flink?

Timeplus is one binary with SQL as the only interface; Flink is a JVM cluster with a Java and SQL API and far more operational surface.

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.

Timeplus: Can Proton run in production?

It can, but it is single-node only, so there is no high availability without the commercial edition.

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.

Timeplus: How much is the cloud?

From 199 US dollars a month, sized by CPU and memory, with a fourteen day trial.

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 Timeplus

Keep looking

Other head to heads