Softwr

Databases · head to head

Dgraph vs Spacelift

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

Spacelift

Developer Tools

Infrastructure-as-code orchestration for Terraform, OpenTofu, Pulumi and Kubernetes

From
Free
Free plan
Yes

The short version

  • Spacelift is free; Dgraph starts at $39/mo.
  • Only Dgraph lists apache 2.0 licence; only Spacelift lists multi-tool orchestration.
  • Where Spacelift falls short: three of the five tiers are quote-only, so a shortlist cannot be costed without entering a sales process with each vendor on it.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which Dgraph and Spacelift actually diverge.

Attributes where Dgraph and Spacelift differ
AttributeDgraphSpacelift
Pricing modelFreemiumBy private worker and tier, not by user
PlatformsLinux, macOS, Self-hosted, WebWeb, Self-hosted
CategoryDatabasesDeveloper Tools

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

Not yet recorded: founded for Spacelift.

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 Spacelift

  • Multi-tool orchestration
  • Policy as code
  • Private workers
  • Spaces
  • Blueprints
  • Drift detection

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

Spacelift

  • Platform teams running infrastructure changes through approval gates rather than through application CInot Dgraph
  • Organisations standardising Terraform and OpenTofu across many teams with policy enforcementnot Dgraph
  • Estates needing private runners so cloud credentials never leave the networknot Dgraph
  • Teams wanting drift detection and reconciliation rather than plan-time checks alonenot 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

Spacelift

  • Users are unlimited and private workers are metered, so deployment concurrency rather than headcount drives the bill, which inverts how most engineering budgets are built and is easy to under-forecast
  • There is no affordable paid entry point. The free tier stops at two users and the next tier is a five-figure commitment with nothing in between
  • Three of the five tiers are quote-only, so a shortlist cannot be costed without entering a sales process with each vendor on it
  • The self-hosted build lags the hosted one, has no public worker pool and lacks the Azure and Google Cloud integrations available in the SaaS product, with OIDC federation offered as the workaround
  • Stacks, Rego policies, Blueprints, Spaces and Spacelift-managed state are proprietary constructs, so leaving means rebuilding the orchestration layer rather than pointing it at a different runner

Pricing, plan by plan

Dgraph

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

Spacelift

Free
  • FreeFree
    • Two users
    • Public workers only
    • No private workers
  • Starter PlusOn request
    • Unlimited users
    • Two public workers
    • One to two private workers
  • BusinessOn request
    • Unlimited users
    • Three private workers
    • Quoted
  • EnterpriseOn request
    • Unlimited users
    • Five to thirty private workers
    • Self-hosted option

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

  • You need multi-tool orchestration.
  • You want to start without paying.
  • You work on Web, Self-hosted.
  • You also want policy as code.

Questions people ask

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

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.

Spacelift: How is Spacelift priced?

By tier and by private worker count rather than per user. Users are unlimited on every paid plan. The published figure on the pricing page carries no period label, and the FAQ describes the tier as an annual subscription, so confirm the period in writing.

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.

Spacelift: Does it support OpenTofu?

Yes, and Spacelift sponsors the OpenTofu project, which is a substantive hedge for anyone avoiding Terraform under the Business Source Licence.

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.

Spacelift: Is there a self-hosted version?

Yes, described as carrying Enterprise functionality, but it is priced on request and lags the hosted product on cloud integrations.

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.

Spacelift: Why not just use the CI system we already have?

That is the real comparison. General purpose CI handles state, drift, approval gates and concurrency control for infrastructure poorly, and whether that is worth a five-figure floor depends on how much infrastructure change your organisation actually ships.

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.

Spacelift: What happens to our pipelines if we leave?

They do not port. Rego policies, Blueprints, Spaces and managed state are Spacelift constructs and the orchestration has to be rebuilt elsewhere.

Share

Related pages

Other head to heads