Databases · head to head
Dgraph vs Preact

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

Preact
Web Development
3kB alternative to React with the same modern API
- From
- Free
- Free plan
- Yes
The short version
- Preact is free; Dgraph starts at $39/mo.
- Only Dgraph lists apache 2.0 licence; only Preact lists 3kB runtime.
- Where Preact falls short: compatibility through preact/compat is good but not total, and some React libraries break in ways that are hard to diagnose.
- Prices and features on this page were last checked on 13 November 2026.
How do Dgraph and Preact differ?
Dgraph and Preact differ on pricing model, platforms and category (Databases against Web Development). Only the attributes on which Dgraph and Preact actually diverge.
Identical on both: starting price (Free), free tier (Yes).
Not yet recorded: founded for Preact.
Which features does each one have?
They share no listed features; 10 appear only for Dgraph and 4 only for Preact. 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 Preact
- 3kB runtime
- preact/compat
- Same modern API
- Fast rendering
What is each one used for?
Preact is most often brought in for embedded widgets that load inside someone else’s page and must stay small. 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 Preact
- A knowledge graph that outgrew a single machine and needs storage distributed across nodes without a per-core licence negotiationnot Preact
- Recommendation or fraud-detection features that traverse several hops at request time, where a relational join chain has become the bottlenecknot Preact
- Teams that want a graph database they can read, fork and self-host under a permissive licence rather than a source-available onenot Preact
Preact
- Embedded widgets that load inside someone else’s page and must stay smallnot Dgraph
- Marketing and content sites where JavaScript payload affects Core Web Vitalsnot Dgraph
- Applications targeting low-bandwidth or low-powered devicesnot Dgraph
Where do Dgraph and Preact fall short?
Preact's most cited limit: behavioural differences from React exist in edge cases, particularly around event handling. 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
Preact
- Compatibility through preact/compat is good but not total, and some React libraries break in ways that are hard to diagnose
- Behavioural differences from React exist in edge cases, particularly around event handling
- A much smaller community, so unusual problems have fewer existing answers than React
How much do Dgraph and Preact cost?
Dgraph has a free plan, with paid plans from $39/mo; Preact 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
Preact
Free- PreactFree
- Full library
- Commercial use permitted
- No usage limits
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 Preact if
- You need 3kb runtime.
- You want to start without paying.
- You also want preact/compat.
Questions people ask
- Is Dgraph or Preact better?
- Neither clearly leads. Dgraph starts at Free and Preact at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Dgraph or Preact?
- Dgraph starts at Free and Preact at Free.
- Does Dgraph or Preact run on more platforms?
- Dgraph runs on Linux, macOS, Self-hosted, Web. Preact runs on 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 Preact is typically brought in for.
- What can Dgraph do that Preact cannot?
- Dgraph covers Apache 2.0 licence, Generated GraphQL API, DQL query language, Predicate sharding. Preact covers 3kB runtime, preact/compat, Same modern API, Fast rendering.
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.
Preact: Is Preact free?
Yes, open source under the MIT 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.
Preact: Can I use React libraries with Preact?
Most, through the preact/compat layer. Compatibility is good but not complete, so libraries relying on React internals can break.
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.
Preact: Why choose Preact over React?
Bundle size, almost always. If payload is not a binding constraint, React’s ecosystem is usually the better trade.
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.
Related pages
Other head to heads
- Dgraph vs Neo4j
- Dgraph vs ArangoDB
- Dgraph vs Elasticsearch
- Dgraph vs Couchbase
- Dgraph vs Cassandra
- Dgraph vs FaunaDB
- Dgraph vs Firebase Realtime Database
- Dgraph vs RavenDB
- Dgraph vs ScyllaDB
- Dgraph vs Cockroach Labs
- Dgraph vs DynamoDB
- Dgraph vs Canary Labs
- Dgraph vs Chroma
- Dgraph vs Cloudinary
- Dgraph vs Convex
- Dgraph vs Dragonfly
- Dgraph vs Dremio
- Dgraph vs CouchDB
- Dgraph vs Vue.js
- Dgraph vs React
- Dgraph vs Alpine.js
- Dgraph vs SolidJS
- Dgraph vs MUI
- Dgraph vs Bootstrap
- Dgraph vs esbuild
- Dgraph vs Lit
- Dgraph vs Docusaurus
- Dgraph vs Angular
- Dgraph vs MySQL
- Dgraph vs Radix UI
- Dgraph vs Next.js
- Dgraph vs Django
- Dgraph vs Flask
- Dgraph vs Remix
- Dgraph vs Tailwind CSS
- Dgraph vs Astro
- Preact vs Neo4j
- Preact vs ArangoDB
- Preact vs Elasticsearch
- Preact vs Couchbase
- Preact vs Cassandra
- Preact vs FaunaDB
- Preact vs Firebase Realtime Database
- Preact vs RavenDB
- Preact vs ScyllaDB
- Preact vs Cockroach Labs
- Preact vs DynamoDB
- Preact vs Canary Labs
- Preact vs Chroma
- Preact vs Cloudinary
- Preact vs Convex
- Preact vs Dragonfly
- Preact vs Dremio
- Preact vs CouchDB
- Preact vs Vue.js
- Preact vs React
- Preact vs Alpine.js
- Preact vs SolidJS
- Preact vs MUI
- Preact vs Bootstrap
- Preact vs esbuild
- Preact vs Lit
- Preact vs Docusaurus
- Preact vs Angular
- Preact vs MySQL
- Preact vs Radix UI
- Preact vs Next.js
- Preact vs Django
- Preact vs Flask
- Preact vs Remix
- Preact vs Tailwind CSS
- Preact vs Astro
