Software · head to head
Dgraph vs Vitess

Vitess
Software
Scalable database clustering system for horizontal scaling of MySQL
- From
- Free
- Rated
- -
The short version
- Each has a real cost: Dgraph the GitHub repository (dgraph-io/dgraph) is licensed Apache 2.0 with no paid tier, cloud offering, or enterprise edition mentioned anywhere in the README; Vitess vTGate scatter queries without sharding key incur significant performance penalties
- They diverge on capability: Dgraph covers Native GraphQL, Vitess covers Horizontal Sharding.
Where they differ
Only the attributes on which Dgraph and Vitess actually diverge.
Identical on both: starting price (Free), free tier (Yes), user rating (Not yet rated), category (Unknown).
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
- Native GraphQL
- Distributed Architecture
- ACID Transactions
- GraphQL Subscriptions
- Full-text Search
- Geolocation Queries
- Horizontal Scaling
- GraphQL
Only in Vitess
- Horizontal Sharding
- Connection Pooling
- Query Routing
- Online Schema Changes
- Shard Management
- Replication Management
- Automated Failover
- MySQL
Both cover
- Linux support
- Docker support
What people use each for
The jobs each tool is most often brought in to do.
Dgraph
- Knowledge graphsnot Vitess
- Fraud detectionnot Vitess
- Recommendation enginesnot Vitess
- Network analysisnot Vitess
- Master data managementnot Vitess
Vitess
- Transaction processingnot Dgraph
- Data storagenot Dgraph
- Application backendnot Dgraph
- Reportingnot Dgraph
- Data analyticsnot Dgraph
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Dgraph
- The GitHub repository (dgraph-io/dgraph) is licensed Apache 2.0 with no paid tier, cloud offering, or enterprise edition mentioned anywhere in the README
Vitess
- VTGate scatter queries without sharding key incur significant performance penalties
- Foreign key constraints not enforced across shards, requiring application-level integrity handling
- Single primary per keyspace limits multi-region write capabilities
- Distributed transactions without proper sharding key routing suffer performance degradation
Pricing, plan by plan
Dgraph
Free- CommunityFree
- Native GraphQL
- Graph queries
- Full-text search
- Cloud$39/month
- Managed service
- Auto-scaling
- Enterprise support
Vitess
FreeNo published plan breakdown. See the Vitess review.
Which should you pick?
Choose Dgraph if
- You need native graphql.
- You want to start without paying.
- You work on Linux, Mac, Docker, Web.
- You also want distributed architecture.
Choose Vitess if
- You need horizontal sharding.
- You want to start without paying.
- You work on Linux, macOS, Docker, Kubernetes.
- You also want connection pooling.
Questions people ask
- Is Dgraph or Vitess better?
- Neither clearly leads. Dgraph starts at Free and Vitess at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Dgraph or Vitess?
- Dgraph starts at Free and Vitess at Free.
- Does Dgraph or Vitess run on more platforms?
- Dgraph runs on Linux, Mac, Docker, Web. Vitess runs on Linux, macOS, Docker, Kubernetes.
- 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 knowledge graphs, fraud detection, recommendation engines, network analysis. Of those, knowledge graphs and fraud detection are not what Vitess is typically brought in for.
- What can Dgraph do that Vitess cannot?
- Dgraph covers Native GraphQL, Distributed Architecture, ACID Transactions, GraphQL Subscriptions. Vitess covers Horizontal Sharding, Connection Pooling, Query Routing, Online Schema Changes. Both handle Linux support, Docker support.
Answered from the vendors’ own pages
Vitess: Is Vitess free to use?
Yes. Vitess is completely free and open source under the Apache 2.0 license. It is a graduated CNCF project with no licensing costs or pricing tiers.
SourceVitess: What databases does Vitess support?
Vitess supports MySQL and MariaDB as backend databases. It acts as a middleware layer that adds sharding and orchestration capabilities on top of these databases.
SourceVitess: Does Vitess require Kubernetes to run?
No. Vitess can run on Kubernetes using the Vitess Operator, but it can also be deployed on traditional infrastructure. Kubernetes integration is optional and provides additional automation benefits.
SourceVitess: How does Vitess handle cross-shard transactions?
Vitess supports distributed transactions across shards, but they require queries to be routed through the sharding key. Transactions without a proper sharding key can result in slower performance.
SourceVitess: Does Vitess enforce foreign key constraints?
Vitess does not enforce foreign key constraints across shards by default. Referential integrity must be managed at the application layer, though per-database support can be enabled with limitations.
SourceRelated pages
Keep looking
Other head to heads
- Dgraph vs Cockroach Labs
- Dgraph vs PostgreSQL
- Dgraph vs Airtable
- Dgraph vs Amazon Aurora
- Dgraph vs Elasticsearch
- Dgraph vs PlanetScale
- Dgraph vs Azure SQL
- Dgraph vs ClickHouse
- Dgraph vs Couchbase
- Dgraph vs DuckDB
- Dgraph vs DynamoDB
- Dgraph vs MariaDB
- Dgraph vs Oracle Database
- Dgraph vs Amazon RDS
- Dgraph vs Amazon Redshift
- Dgraph vs Apache Druid
- Dgraph vs Cassandra
- Dgraph vs CouchDB
- Vitess vs Cockroach Labs
- Vitess vs PostgreSQL
- Vitess vs Airtable
- Vitess vs Amazon Aurora
- Vitess vs Elasticsearch
- Vitess vs PlanetScale
- Vitess vs Azure SQL
- Vitess vs ClickHouse
- Vitess vs Couchbase
- Vitess vs DuckDB
- Vitess vs DynamoDB
- Vitess vs MariaDB
- Vitess vs Oracle Database
- Vitess vs Amazon RDS
- Vitess vs Amazon Redshift
- Vitess vs Apache Druid
- Vitess vs Cassandra
- Vitess vs CouchDB

