Softwr

Databases · head to head

Dgraph vs OpenCart

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
OpenCart logo

OpenCart

E-Commerce

Self-hosted open source shopping cart written in PHP, released under the MIT licence

From
Free
Free plan
Yes

The short version

  • OpenCart is free; Dgraph starts at $39/mo.
  • Only Dgraph lists apache 2.0 licence; only OpenCart lists MIT licensed source.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Dgraph and OpenCart actually diverge.

Attributes where Dgraph and OpenCart differ
AttributeDgraphOpenCart
Pricing modelFreemiumOpen-source
PlatformsLinux, macOS, Self-hosted, WebWeb
CategoryDatabasesE-Commerce
Founded20162009

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

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 OpenCart

  • MIT licensed source
  • Self-hosted PHP and MySQL
  • No transaction fees
  • Multi-store
  • Extension marketplace
  • Multi-currency and multi-language
  • OCMod modification system
  • Full data access

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

OpenCart

  • A merchant with volume high enough that a percentage transaction fee costs more than a developernot Dgraph
  • An agency building client stores where the client must own the code and the data outrightnot Dgraph
  • A store with unusual catalogue or pricing logic that a hosted platform will not permitnot Dgraph
  • Selling in a market where the local payment gateway is not supported by the mainstream SaaS platformsnot 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

OpenCart

  • Extensions modify core behaviour through an XML patching system, so two modules that patch the same file conflict in ways that surface as broken checkout rather than as an installation error, and resolving that requires a developer reading both patches
  • Major version upgrades have broken third party extension compatibility, so moving between them means re-purchasing or re-commissioning modules and effectively rebuilding parts of the store rather than clicking update
  • Hosting, patching, backups and PCI scope are all your responsibility, so a security update you postpone is a breach you own, and there is no vendor obligation to notify or protect you
  • Extension quality on the marketplace is uneven and modules are sold as one-off purchases with no guaranteed maintenance, so a module central to your store can simply stop being updated and leave you holding the code
  • The core project is maintained by a very small team relative to the platforms it competes with, so security fixes, compatibility with new PHP versions and feature work all arrive at a pace you cannot influence or pay to accelerate

Pricing, plan by plan

Dgraph

Free
  • CommunityFree
    • Native GraphQL
    • Graph queries
    • Full-text search
  • Cloud$39/mo
    • Managed service
    • Auto-scaling
    • Enterprise support

OpenCart

Free
  • Open SourceFree
    • Core ecommerce features
    • Free support
    • Extensions available

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

  • You need mit licensed source.
  • You want to start without paying.
  • You also want self-hosted php and mysql.

Questions people ask

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

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.

OpenCart: Is OpenCart really free?

The software is MIT licensed with no paid edition. The costs are hosting, extensions, and a developer, and for a low volume store those can exceed a SaaS subscription.

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.

OpenCart: Does it charge transaction fees?

No. There is no platform cut and no surcharge for using your own payment gateway, which is the main financial argument for self-hosting at volume.

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.

OpenCart: How hard is customisation?

Theme changes are ordinary PHP templates and are approachable. Changing behaviour means the OCMod patching system, which conflicts between extensions and needs a developer.

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.

OpenCart: What is the biggest hidden cost?

Upgrades. Version transitions have broken extension compatibility before, so budget for a partial rebuild rather than assuming updates are routine maintenance.

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