Databases · head to head
CosmosDB vs Dgraph

CosmosDB
Databases
Globally distributed, multi-model database service from Azure
- From
- Free
- Rated
- -

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: CosmosDB autoscale provisioned throughput enforces a minimum of 1,000 RU/s, billed hourly whether or not the database is used; 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: CosmosDB covers Global Distribution, 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 CosmosDB and Dgraph actually diverge.
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 CosmosDB
- Global Distribution
- Multi-model APIs
- Elastic Scaling
- Five Consistency Levels
- SLA-backed Latency
- Automatic Indexing
- Serverless
- Azure Functions
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.
CosmosDB
- Running a globally distributed multi model database on Azurenot Dgraph
- Serving low latency reads and writes from multiple Azure regionsnot Dgraph
- Storing document, key value and graph data behind a managed servicenot Dgraph
Dgraph
- An application whose core data is a graph, such as permissions, social connections or product relationships, where the frontend already consumes GraphQLnot CosmosDB
- A knowledge graph that outgrew a single machine and needs storage distributed across nodes without a per-core licence negotiationnot CosmosDB
- Recommendation or fraud-detection features that traverse several hops at request time, where a relational join chain has become the bottlenecknot CosmosDB
- Teams that want a graph database they can read, fork and self-host under a permissive licence rather than a source-available onenot CosmosDB
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
CosmosDB
- Autoscale provisioned throughput enforces a minimum of 1,000 RU/s, billed hourly whether or not the database is used
- Provisioned throughput is charged in every region the account is replicated to, so multi region accounts multiply the RU bill
- Storage charges cover data, indexes and backups in each replicated region
- Egress out of Azure and between regions is charged, though ingress is free
- The free allowance is one account per Azure subscription, limited to 1,000 RU/s and 25 GB
- RU/s rates vary by region and are only shown through the pricing calculator rather than a flat published rate
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
CosmosDB
Free- Free TierFree
- 1000 RU/s
- 25GB storage
- First 12 months
- ServerlessFree
- Pay per request
- Auto-scaling
- Event-driven workloads
Dgraph
Free- CommunityFree
- Native GraphQL
- Graph queries
- Full-text search
- Cloud$39/month
- Managed service
- Auto-scaling
- Enterprise support
Which should you pick?
Choose CosmosDB if
- You need global distribution.
- You want to start without paying.
- You work on Web, Azure.
- You also want multi-model apis.
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 CosmosDB or Dgraph better?
- Neither clearly leads. CosmosDB 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, CosmosDB or Dgraph?
- CosmosDB starts at Free and Dgraph at Free.
- Does CosmosDB or Dgraph run on more platforms?
- CosmosDB runs on Web, Azure. Dgraph runs on Linux, Mac, Docker, Web.
- Can I use CosmosDB for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is CosmosDB best used for?
- CosmosDB is most often used for running a globally distributed multi model database on azure, serving low latency reads and writes from multiple azure regions, storing document, key value and graph data behind a managed service. Of those, running a globally distributed multi model database on azure and serving low latency reads and writes from multiple azure regions are not what Dgraph is typically brought in for.
- What can CosmosDB do that Dgraph cannot?
- CosmosDB covers Global Distribution, Multi-model APIs, Elastic Scaling, Five Consistency Levels. Dgraph covers Apache 2.0 licence, Generated GraphQL API, DQL query language, Predicate sharding.
Answered from the vendors’ own pages
CosmosDB: Is there a free tier for Azure Cosmos DB?
Yes, Cosmos DB offers a free tier with 1,000 RU/s of throughput and 25 GB of storage per month for the lifetime of the account, available to new accounts.
SourceDgraph: 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.
CosmosDB: How is Cosmos DB priced after the free tier?
Cosmos DB uses three billing models: provisioned throughput billed per request unit per second, vCore pricing for certain APIs, or serverless consumption pricing where you pay only for requests processed. Reserved capacity offers 20% discount for one year or 30% for three years.
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.
CosmosDB: Can I change my pricing model after choosing one?
No. Once you select a compute pricing model and API, they cannot be changed. This choice is permanent for that database.
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.
CosmosDB: Is there a trial period for Cosmos DB beyond the free tier?
Azure offers a 30-day free trial account for all Azure services. Additionally, Azure AI customers may be eligible for a 90-day free Cosmos DB subscription through the Azure AI Advantage program.
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.
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
- CosmosDB vs Amazon Aurora
- CosmosDB vs Cockroach Labs
- CosmosDB vs Airtable
- CosmosDB vs PostgreSQL
- CosmosDB vs Google Cloud SQL
- CosmosDB vs ArangoDB
- CosmosDB vs DataStax
- CosmosDB vs FaunaDB
- CosmosDB vs Firebolt
- CosmosDB vs turbopuffer
- CosmosDB vs VerneMQ
- CosmosDB vs Vespa
- CosmosDB vs Xata
- CosmosDB vs YugabyteDB
- CosmosDB vs Zilliz
- CosmosDB vs Amazon Redshift
- CosmosDB vs BigQuery
- CosmosDB vs Amazon RDS
- CosmosDB vs Neo4j
- CosmosDB vs Elasticsearch
- CosmosDB vs Couchbase
- CosmosDB vs Cassandra
- CosmosDB vs Firebase Realtime Database
- CosmosDB vs RavenDB
- CosmosDB vs Convex
- CosmosDB vs Dragonfly
- CosmosDB vs Dremio
- CosmosDB vs Fivetran HVR
- CosmosDB vs Grist
- CosmosDB vs IBM Db2
- Dgraph vs Amazon Aurora
- Dgraph vs Cockroach Labs
- Dgraph vs Airtable
- Dgraph vs PostgreSQL
- Dgraph vs Google Cloud SQL
- Dgraph vs ArangoDB
- Dgraph vs DataStax
- Dgraph vs FaunaDB
- Dgraph vs Firebolt
- Dgraph vs turbopuffer
- Dgraph vs VerneMQ
- Dgraph vs Vespa
- Dgraph vs Xata
- Dgraph vs YugabyteDB
- Dgraph vs Zilliz
- Dgraph vs Amazon Redshift
- Dgraph vs BigQuery
- Dgraph vs Amazon RDS
- Dgraph vs Neo4j
- Dgraph vs Elasticsearch
- Dgraph vs Couchbase
- Dgraph vs Cassandra
- Dgraph vs Firebase Realtime Database
- Dgraph vs RavenDB
- Dgraph vs Convex
- Dgraph vs Dragonfly
- Dgraph vs Dremio
- Dgraph vs Fivetran HVR
- Dgraph vs Grist
- Dgraph vs IBM Db2
