Databases · head to head
Dgraph vs PartyKit

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
PartyKit
Developer Tools
Platform for building and deploying realtime multiplayer servers on the edge
- From
- Free
- Free plan
- Yes
The short version
- PartyKit is free; Dgraph starts at $39/mo.
- Only Dgraph lists apache 2.0 licence; only PartyKit lists stateful edge servers.
- Where PartyKit falls short: documentation and FAQ material on the marketing site is sparse compared to larger realtime platforms.
- Prices and features on this page were last checked on 13 November 2026.
Where they differ
Only the attributes on which Dgraph and PartyKit actually diverge.
Identical on both: starting price (Free), pricing model (Freemium), free tier (Yes).
Not yet recorded: founded for PartyKit.
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 PartyKit
- Stateful edge servers
- WebSocket-first API
- CRDT library compatibility
- Framework integrations
- Global edge deployment
- Custom domains
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 PartyKit
- A knowledge graph that outgrew a single machine and needs storage distributed across nodes without a per-core licence negotiationnot PartyKit
- Recommendation or fraud-detection features that traverse several hops at request time, where a relational join chain has become the bottlenecknot PartyKit
- Teams that want a graph database they can read, fork and self-host under a permissive licence rather than a source-available onenot PartyKit
PartyKit
- Multiplayer collaborative appsnot Dgraph
- Realtime AI agent backendsnot Dgraph
- Live cursors and presencenot Dgraph
- Collaborative whiteboards and documentsnot 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
PartyKit
- Documentation and FAQ material on the marketing site is sparse compared to larger realtime platforms
- Commercial free tier requires deploying to the user's own Cloudflare account, adding setup complexity
- Storage on the free Individual plan clears every 24 hours, limiting it to prototyping rather than persistent production data
- Smaller ecosystem and community than more established realtime infrastructure providers
Pricing, plan by plan
Dgraph
Free- CommunityFree
- Native GraphQL
- Graph queries
- Full-text search
- Cloud$39/mo
- Managed service
- Auto-scaling
- Enterprise support
PartyKit
Free- IndividualFree
- Up to 10 live projects
- Deploy to the global edge platform
- Storage clears every 24 hours
- CommercialFree
- Unlimited projects
- Custom domains
- Runs on your own Cloudflare account; pay only Cloudflare usage
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 PartyKit if
- You need stateful edge servers.
- You want to start without paying.
- You work on Web, API.
- You also want websocket-first api.
Questions people ask
- Is Dgraph or PartyKit better?
- Neither clearly leads. Dgraph starts at Free and PartyKit at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Dgraph or PartyKit?
- Dgraph starts at Free and PartyKit at Free.
- Does Dgraph or PartyKit run on more platforms?
- Dgraph runs on Linux, macOS, Self-hosted, Web. PartyKit runs on Web, API.
- 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 PartyKit is typically brought in for.
- What can Dgraph do that PartyKit cannot?
- Dgraph covers Apache 2.0 licence, Generated GraphQL API, DQL query language, Predicate sharding. PartyKit covers Stateful edge servers, WebSocket-first API, CRDT library compatibility, Framework integrations.
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.
PartyKit: How much does PartyKit cost?
PartyKit is completely free. Both the Individual and Commercial plans have no upfront costs.
SourceDgraph: 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.
PartyKit: What is PartyKit's Individual plan?
The Individual plan is free and includes deployment to a global edge platform, support for up to 10 live projects, and is suitable for small projects. Storage is cleared every 24 hours.
SourceDgraph: 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.
PartyKit: What is PartyKit's Commercial plan?
The Commercial plan is free but requires deploying to your own Cloudflare account. It includes custom domains, unlimited projects, and you pay only your Cloudflare usage costs.
SourceDgraph: 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.
PartyKit: Can I upgrade from Individual to Commercial plan?
Yes, both plans are free but offer different feature sets. The Commercial plan removes project restrictions but requires managing your own Cloudflare infrastructure.
SourceDgraph: 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 Qdrant
- Dgraph vs SingleStore
- Dgraph vs TiDB
- Dgraph vs Tinybird
- Dgraph vs Typesense
- Dgraph vs Valkey
- Dgraph vs CouchDB
- Dgraph vs Soketi
- Dgraph vs GitHub Copilot
- Dgraph vs Pieces for Developers
- Dgraph vs LaunchDarkly
- Dgraph vs CodeSandbox
- Dgraph vs Moonrepo
- Dgraph vs Swagger UI
- Dgraph vs Coder
- Dgraph vs StackBlitz
- Dgraph vs Deep Code
- Dgraph vs Refact
- Dgraph vs Earthly
- Dgraph vs Namespace
- Dgraph vs Nix
- Dgraph vs Nixpacks
- Dgraph vs Octopus Deploy
- Dgraph vs Okteto
- Dgraph vs OpsLevel
- PartyKit vs Neo4j
- PartyKit vs ArangoDB
- PartyKit vs Elasticsearch
- PartyKit vs Couchbase
- PartyKit vs Cassandra
- PartyKit vs FaunaDB
- PartyKit vs Firebase Realtime Database
- PartyKit vs RavenDB
- PartyKit vs ScyllaDB
- PartyKit vs Cockroach Labs
- PartyKit vs DynamoDB
- PartyKit vs Qdrant
- PartyKit vs SingleStore
- PartyKit vs TiDB
- PartyKit vs Tinybird
- PartyKit vs Typesense
- PartyKit vs Valkey
- PartyKit vs CouchDB
- PartyKit vs Soketi
- PartyKit vs GitHub Copilot
- PartyKit vs Pieces for Developers
- PartyKit vs LaunchDarkly
- PartyKit vs CodeSandbox
- PartyKit vs Moonrepo
- PartyKit vs Swagger UI
- PartyKit vs Coder
- PartyKit vs StackBlitz
- PartyKit vs Deep Code
- PartyKit vs Refact
- PartyKit vs Earthly
- PartyKit vs Namespace
- PartyKit vs Nix
- PartyKit vs Nixpacks
- PartyKit vs Octopus Deploy
- PartyKit vs Okteto
- PartyKit vs OpsLevel
