Softwr

Databases · head to head

Dgraph vs Windmill

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

Windmill

Automation Integration

Open-source developer platform for building scripts, workflows, and internal apps

From
Free
Free plan
Yes

The short version

  • Free plans on both; paid from $39/mo and $120/mo.
  • Only Dgraph lists apache 2.0 licence; only Windmill lists script-to-workflow engine.
  • Where Windmill falls short: free self-hosted tier caps SSO users at 10 and workspaces at 3, requiring Enterprise for larger teams.
  • Prices and features on this page were last checked on 17 November 2026.

How do Dgraph and Windmill differ?

Dgraph and Windmill differ on pricing model (Freemium against Open-source), platforms and category. Only the attributes on which Dgraph and Windmill actually diverge.

Attributes where Dgraph and Windmill differ
AttributeDgraphWindmill
Pricing modelFreemiumOpen-source
PlatformsLinux, macOS, Self-hosted, WebWeb, API, Linux, Windows, macOS
CategoryDatabasesAutomation Integration

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

Not yet recorded: founded for Windmill.

Which features does each one have?

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

  • Script-to-workflow engine
  • Auto-generated UIs
  • Self-hosted deployment
  • Git sync
  • SSO support
  • Audit logs

What is each one used for?

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

Windmill

  • Turning ad-hoc scripts into scheduled jobs and APIsnot Dgraph
  • Building internal tools from existing Python/TypeScript codenot Dgraph
  • Self-hosted automation for engineering teamsnot Dgraph
  • Orchestrating multi-language workflowsnot Dgraph

Where do Dgraph and Windmill fall short?

Windmill's most cited limit: free self-hosted tier caps SSO users at 10 and workspaces at 3, requiring Enterprise for larger teams. 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

Windmill

  • Free self-hosted tier caps SSO users at 10 and workspaces at 3, requiring Enterprise for larger teams
  • Compute unit and seat-based pricing (developer vs. operator seats, worker compute units) adds pricing complexity beyond a flat monthly fee
  • Email triggers are capped at 100/day on the free tier, limiting event-driven use cases without upgrading
  • Smaller ecosystem of pre-built integrations compared to more established automation tools like n8n

How much do Dgraph and Windmill cost?

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

Windmill

Free
  • Free / Open-sourceFree
    • Unlimited executions
    • Self-hosted deployment
    • Max 10 users with SSO
  • Enterprise$120/mo
    • Unlimited executions and workspaces
    • Uncapped SSO seats
    • 24/7 priority support (3-hour response)

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

  • You need script-to-workflow engine.
  • You want to start without paying.
  • You work on Web, API, Linux, Windows, macOS.
  • You also want auto-generated uis.

Questions people ask

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

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.

Windmill: What does Windmill cost?

Windmill's Free and Open-source edition is $0/month for self-hosted use with unlimited executions, while Enterprise starts at $120/month with unlimited workspaces and uncapped SSO seats, priced further by developer/operator seats and compute units.

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.

Windmill: Is there a free plan and what are its limits?

The free self-hosted plan supports unlimited executions but caps SSO at 10 users, workspaces at 3, groups/permissions at 4, and email triggers at 100 per day.

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.

Windmill: How is usage metered on Windmill Enterprise?

Enterprise usage is metered through seats (developer seats at $20/month, operator seats at $10/month) and compute units, e.g. $100/month for 2 standard-worker compute units.

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

Windmill: What happens to a self-hosted Windmill deployment if the company shuts down?

The pricing page addresses this directly as an FAQ topic, noting that self-hosted applications built on the open-source edition can continue running independently of Windmill the company.

Source
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