Databases · head to head
Dgraph vs Square for Retail

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

Square for Retail
E-Commerce
Integrated point of sale and retail management
- From
- Free
- Free plan
- Yes
The short version
- Square for Retail is a comprehensive point of sale and retail management platform.
- Free plans on both; paid from $39/mo and $49/mo.
- Only Dgraph lists apache 2.0 licence; only Square for Retail lists contactless payments.
- Where Square for Retail falls short: limited customer support with primarily email and online forums, slow response times for urgent issues.
- Prices and features on this page were last checked on 13 November 2026.
Where they differ
Only the attributes on which Dgraph and Square for Retail actually diverge.
| Attribute | Dgraph | Square for Retail |
|---|---|---|
| Platforms | Linux, macOS, Self-hosted, Web | iOS, API |
| Category | Databases | E-Commerce |
| Founded | 2016 | 2009 |
Identical on both: starting price (Free), free tier (Yes).
Not yet recorded: pricing model for Square for Retail.
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 Square for Retail
- Contactless payments
- Inventory tracking
- Employee management
- Customer profiles
- Sales analytics
- Receipt printing
- Integration with Square Online
- Reporting tools
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 Square for Retail
- A knowledge graph that outgrew a single machine and needs storage distributed across nodes without a per-core licence negotiationnot Square for Retail
- Recommendation or fraud-detection features that traverse several hops at request time, where a relational join chain has become the bottlenecknot Square for Retail
- Teams that want a graph database they can read, fork and self-host under a permissive licence rather than a source-available onenot Square for Retail
Square for Retail
- Retail point-of-sale systemsnot Dgraph
- Online store payment processingnot Dgraph
- Appointment and booking schedulingnot Dgraph
- Phone and field payment collectionnot 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
Square for Retail
- Limited customer support with primarily email and online forums, slow response times for urgent issues
- Internet connectivity required for normal operations; weak signal impacts transaction processing and experience
- Restricted to Square's payment processing with higher transaction fees compared to some competitors
- Limited to iOS devices and Square's proprietary hardware, excluding Android or third-party devices
- Limited advanced retail capabilities and deeper third-party integrations compared to enterprise POS systems
Pricing, plan by plan
Dgraph
Free- CommunityFree
- Native GraphQL
- Graph queries
- Full-text search
- Cloud$39/mo
- Managed service
- Auto-scaling
- Enterprise support
Square for Retail
Free- FreeFree
- Payment processing at 2.6% + 15 cents
- Basic inventory management
- Invoicing
- Plus$49/mo
- In-person: 2.5% + 15 cents
- Online: 2.9% + 30 cents
- Product exchanges
- Premium$149/mo
- In-person: 2.4% + 15 cents
- Online: 2.9% + 30 cents
- Advanced features
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 Square for Retail if
- You need contactless payments.
- You want to start without paying.
- You work on iOS, API.
- You also want inventory tracking.
Questions people ask
- Is Dgraph or Square for Retail better?
- Neither clearly leads. Dgraph starts at Free and Square for Retail at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Dgraph or Square for Retail?
- Dgraph starts at Free and Square for Retail at Free.
- Does Dgraph or Square for Retail run on more platforms?
- Dgraph runs on Linux, macOS, Self-hosted, Web. Square for Retail runs on iOS, 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 Square for Retail is typically brought in for.
- What can Dgraph do that Square for Retail cannot?
- Dgraph covers Apache 2.0 licence, Generated GraphQL API, DQL query language, Predicate sharding. Square for Retail covers Contactless payments, Inventory tracking, Employee management, Customer profiles.
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.
Square for Retail: Does Square for Retail have a free tier?
Yes, Square for Retail's free tier includes payment processing at 2.6% plus 15 cents per transaction, basic inventory, invoicing, online shop, and booking tools with no monthly subscription fee.
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.
Square for Retail: What are the transaction fees across Square's pricing tiers?
Free tier: 2.6% + 15 cents. Plus tier ($49/month): 2.5% + 15 cents in-person, 2.9% + 30 cents online. Premium tier ($149/month): 2.4% + 15 cents in-person, 2.9% + 30 cents online.
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.
Square for Retail: What devices can run Square for Retail?
Square for Retail runs on iOS devices (iPad and iPhone) using Square's proprietary hardware or compatible mobile devices, and requires integration with Square's payment processing.
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.
Square for Retail: Can I use Square for Retail offline?
Square for Retail depends on an internet connection for optimal functionality. Offline functionality is limited, and high-traffic operations may require recharging or connection verification.
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.
Square for Retail: Does Square for Retail support third-party integrations?
Yes, Square offers integrations through its App Marketplace and provides APIs for custom development including payments, inventory, orders, customers, loyalty, and webhooks.
SourceRelated pages
More on Square for Retail
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 Heartland Retail
- Dgraph vs Shopkeep
- Dgraph vs Toast
- Dgraph vs Magento
- Dgraph vs KORONA POS
- Dgraph vs NCR Voyix
- Dgraph vs Erply
- Dgraph vs Retail Pro
- Dgraph vs Bluepark
- Dgraph vs Inventory Lab
- Dgraph vs Oracle Commerce
- Dgraph vs Sellfy
- Dgraph vs SAP Commerce Cloud
- Dgraph vs 3dcart
- Dgraph vs Algopix
- Dgraph vs Authorize.net
- Dgraph vs BackToMe
- Dgraph vs Big Cartel
- Square for Retail vs Neo4j
- Square for Retail vs ArangoDB
- Square for Retail vs Elasticsearch
- Square for Retail vs Couchbase
- Square for Retail vs Cassandra
- Square for Retail vs FaunaDB
- Square for Retail vs Firebase Realtime Database
- Square for Retail vs RavenDB
- Square for Retail vs ScyllaDB
- Square for Retail vs Cockroach Labs
- Square for Retail vs DynamoDB
- Square for Retail vs Qdrant
- Square for Retail vs SingleStore
- Square for Retail vs TiDB
- Square for Retail vs Tinybird
- Square for Retail vs Typesense
- Square for Retail vs Valkey
- Square for Retail vs CouchDB
- Square for Retail vs Heartland Retail
- Square for Retail vs Shopkeep
- Square for Retail vs Toast
- Square for Retail vs Magento
- Square for Retail vs KORONA POS
- Square for Retail vs NCR Voyix
- Square for Retail vs Erply
- Square for Retail vs Retail Pro
- Square for Retail vs Bluepark
- Square for Retail vs Inventory Lab
- Square for Retail vs Oracle Commerce
- Square for Retail vs Sellfy
- Square for Retail vs SAP Commerce Cloud
- Square for Retail vs 3dcart
- Square for Retail vs Algopix
- Square for Retail vs Authorize.net
- Square for Retail vs BackToMe
- Square for Retail vs Big Cartel
