Softwr

Databases · head to head

Dgraph vs Merge

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
Free plan
Yes
Merge logo

Merge

Automation Integration

One API for all your integrations

From
Free
Free plan
Yes

The short version

  • Merge is a unified API platform.
  • Free plans on both; paid from $39/mo and $650/mo.
  • Only Dgraph lists apache 2.0 licence; only Merge lists unified API.
  • Where Merge falls short: cannot access data outside Merge's universal schema; no support for custom objects or deep field mappings.
  • Prices and features on this page were last checked on 13 November 2026.

How do Dgraph and Merge differ?

Dgraph and Merge differ on pricing model (Freemium against Usage-based), platforms and category. Only the attributes on which Dgraph and Merge actually diverge.

Attributes where Dgraph and Merge differ
AttributeDgraphMerge
Pricing modelFreemiumUsage-based
PlatformsLinux, macOS, Self-hosted, WebAPI
CategoryDatabasesAutomation Integration
Founded20162020

Identical on both: starting price (Free), free tier (Yes).

Which features does each one have?

They share no listed features; 10 appear only for Dgraph and 20 only for Merge. 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 Merge

  • Unified API
  • HRIS integrations
  • Accounting integrations
  • CRM integrations
  • ATS integrations
  • Ticketing integrations
  • File storage integrations
  • Workday

What is each one used for?

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

Merge

  • Workflow Automationnot Dgraph
  • Data Integrationnot Dgraph
  • Process Automationnot Dgraph
  • App Integrationnot Dgraph
  • API Connectivitynot Dgraph

Where do Dgraph and Merge fall short?

Merge's most cited limit: cannot access data outside Merge's universal schema; no support for custom objects or deep field mappings. 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

Merge

  • Cannot access data outside Merge's universal schema; no support for custom objects or deep field mappings
  • Merge holds customer OAuth tokens, creating vendor lock-in; switching providers requires re-authentication from all customers
  • No support for legacy systems without APIs; limited to modern SaaS applications
  • Pricing complexity at scale with multiple dimensions (workflows, tasks, connectors) affecting costs

How much do Dgraph and Merge cost?

Dgraph has a free plan, with paid plans from $39/mo; Merge has a free plan, with paid plans from $650/mo. 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

Merge

Free
  • FreeFree
    • 1 linked account
    • All integrations
    • Standard support
  • Launch$650/mo
    • 50 linked accounts
    • All categories
    • Email support
  • Scale$2,500/mo
    • Unlimited accounts
    • Priority support
    • SLA
  • EnterpriseOn request
    • Dedicated support
    • Custom contracts
    • Advanced security

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 Merge if

  • You need unified api.
  • You want to start without paying.
  • You work on API.
  • You also want hris integrations.

Questions people ask

Is Dgraph or Merge better?
Neither clearly leads. Dgraph starts at Free and Merge at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Dgraph or Merge?
Dgraph starts at Free and Merge at Free.
Does Dgraph or Merge run on more platforms?
Dgraph runs on Linux, macOS, Self-hosted, Web. Merge runs on 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 Merge is typically brought in for.
What can Dgraph do that Merge cannot?
Dgraph covers Apache 2.0 licence, Generated GraphQL API, DQL query language, Predicate sharding. Merge covers Unified API, HRIS integrations, Accounting integrations, CRM 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.

Merge: What is a Linked Account in Merge?

A Linked Account represents an end customer's authenticated connection to a third-party application (like Salesforce, HubSpot, or Zendesk). Merge pricing is based on the number of production Linked Accounts your end users activate.

Source
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.

Merge: Can I access custom data not in Merge's universal schema?

No. Merge works well for standardized integrations but hits limits with enterprise customers. You cannot access data outside Merge's universal schema, cannot customize integration behavior for specific customers, and cannot pull deeply custom data from source systems.

Source
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.

Merge: What happens if I switch away from Merge?

Merge holds your customers' OAuth tokens. Switching providers means asking every customer to re-authenticate, resulting in potential customer churn and unhappy users.

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.

Merge: Does Merge work with legacy systems?

No. Merge only works if there's an API. Legacy ERPs, government portals, insurance carriers, and older enterprise systems that customers depend on often don't have APIs, making Merge unable to support these integrations.

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

Other head to heads