Softwr

Spreadsheets · head to head

APITable vs Dgraph

APITable logo

APITable

Spreadsheets

Open source spreadsheet database with an API first design and an embeddable widget system

From
Free
Free plan
Yes
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

The short version

  • APITable is free; Dgraph starts at $39/mo.
  • Only APITable lists API first design; only Dgraph lists apache 2.0 licence.
  • Where APITable falls short: automation is thin compared with the commercial alternatives, and most real workflows end up in an external automation tool.
  • Prices and features on this page were last checked on 13 November 2026.

Where they differ

Only the attributes on which APITable and Dgraph actually diverge.

Attributes where APITable and Dgraph differ
AttributeAPITableDgraph
Pricing modelOpen source, no licence feeFreemium
PlatformsWeb, LinuxLinux, macOS, Self-hosted, Web
CategorySpreadsheetsDatabases

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

Not yet recorded: founded for APITable.

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 APITable

  • API first design
  • Widget SDK
  • Embeddable views
  • Multiple view types
  • Linked records and formulas
  • Self hosting
  • Real time collaboration

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

What people use each for

The jobs each tool is most often brought in to do.

APITable

  • Embedding an editable table view inside a product you are building, rather than sending users to another toolnot Dgraph
  • An internal platform where tables are read and written mostly by code through the API and only occasionally by peoplenot Dgraph
  • A self hosted replacement for a per seat spreadsheet database where seat count is the cost drivernot Dgraph
  • Building a custom dashboard widget that sits beside the data instead of in a separate reporting toolnot Dgraph

Dgraph

  • An application whose core data is a graph, such as permissions, social connections or product relationships, where the frontend already consumes GraphQLnot APITable
  • A knowledge graph that outgrew a single machine and needs storage distributed across nodes without a per-core licence negotiationnot APITable
  • Recommendation or fraud-detection features that traverse several hops at request time, where a relational join chain has become the bottlenecknot APITable
  • Teams that want a graph database they can read, fork and self-host under a permissive licence rather than a source-available onenot APITable

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

APITable

  • Records are held in the product own schema rather than as native database tables, so the practical row ceiling is a product limit and large tables should be load tested before commitment
  • The hosted free tier caps records per space, so evaluating on the cloud version gives a misleading picture of what the software can do when self hosted
  • Automation is thin compared with the commercial alternatives, and most real workflows end up in an external automation tool
  • The self hosted deployment is heavier than a single container, so running it properly means managing several services rather than one
  • Documentation and community activity are uneven in English, and finding an answer to an operational problem can take longer than the problem itself deserves

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

Pricing, plan by plan

APITable

Free
  • Self hosted open sourceFree
    • No licence fee
    • No product record cap on self hosted deployments
    • Docker and Kubernetes deployment

Dgraph

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

Which should you pick?

Choose APITable if

  • You need api first design.
  • You want to start without paying.
  • You work on Web, Linux.
  • You also want widget sdk.

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.

Questions people ask

Is APITable or Dgraph better?
Neither clearly leads. APITable starts at Free and Dgraph at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, APITable or Dgraph?
APITable starts at Free and Dgraph at Free.
Does APITable or Dgraph run on more platforms?
APITable runs on Web, Linux. Dgraph runs on Linux, macOS, Self-hosted, Web.
Can I use APITable for free?
Both have a free tier, so you can try either at no cost before committing.
What is APITable best used for?
APITable is most often used for embedding an editable table view inside a product you are building, rather than sending users to another tool, an internal platform where tables are read and written mostly by code through the api and only occasionally by people, a self hosted replacement for a per seat spreadsheet database where seat count is the cost driver, building a custom dashboard widget that sits beside the data instead of in a separate reporting tool. Of those, embedding an editable table view inside a product you are building, rather than sending users to another tool and an internal platform where tables are read and written mostly by code through the api and only occasionally by people are not what Dgraph is typically brought in for.
What can APITable do that Dgraph cannot?
APITable covers API first design, Widget SDK, Embeddable views, Multiple view types. Dgraph covers Apache 2.0 licence, Generated GraphQL API, DQL query language, Predicate sharding.

Answered from the vendors’ own pages

APITable: What is the record limit?

The self hosted edition has no product cap, but performance is bounded by the internal schema rather than by your database. Test at your expected size.

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.

APITable: Can I embed it in my own product?

Yes, and that is the main reason to choose it. Views embed and the widget SDK extends them.

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.

APITable: Is the hosted version representative?

No. Its free tier caps records per space, which is a commercial limit rather than a technical one.

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.

APITable: How hard is self hosting?

Harder than a single container. Plan for several services and someone to keep them running.

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.

APITable: Does it do automations?

Lightly. Expect to pair it with an external automation tool for anything multi step.

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