Cloud · head to head
Lambda (AWS Serverless) vs Dgraph

Lambda (AWS Serverless)
Cloud
Run code without thinking about servers
- From
- Free
- Free plan
- Yes

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
- Lambda (AWS Serverless) is free; Dgraph starts at $39/mo.
- Only Lambda (AWS Serverless) lists event-driven execution; only Dgraph lists apache 2.0 licence.
- Where Lambda (AWS Serverless) falls short: provisioned concurrency, used to avoid cold starts, is charged separately at $0.0000041667 per GB-second whether or not the function runs.
- Prices and features on this page were last checked on 13 November 2026.
How do Lambda (AWS Serverless) and Dgraph differ?
Lambda (AWS Serverless) and Dgraph differ on pricing model (Usage-based against Freemium), platforms and category (Cloud against Databases). Only the attributes on which Lambda (AWS Serverless) and Dgraph actually diverge.
| Attribute | Lambda (AWS Serverless) | Dgraph |
|---|---|---|
| Pricing model | Usage-based | Freemium |
| Platforms | Web, API | Linux, macOS, Self-hosted, Web |
| Category | Cloud | Databases |
| Founded | 2014 | 2016 |
Identical on both: starting price (Free), free tier (Yes).
Which features does each one have?
They share no listed features; 20 appear only for Lambda (AWS Serverless) and 10 only for Dgraph. 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 Lambda (AWS Serverless)
- Function-as-a-Service
- Event-driven execution
- Auto-scaling
- Pay-per-use
- Multiple languages
- Concurrency limits
- Dead Letter Queues
- Environment variables
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 is each one used for?
Lambda (AWS Serverless) is most often brought in for event-driven functions without managing servers. The jobs each tool is most often brought in to do.
Lambda (AWS Serverless)
- Event-driven functions without managing serversnot Dgraph
- API backends behind API Gatewaynot Dgraph
- Processing S3, DynamoDB, SQS and Kinesis eventsnot Dgraph
- Scheduled jobs without a always-on instancenot Dgraph
- Edge compute through Lambda@Edgenot Dgraph
Dgraph
- An application whose core data is a graph, such as permissions, social connections or product relationships, where the frontend already consumes GraphQLnot Lambda (AWS Serverless)
- A knowledge graph that outgrew a single machine and needs storage distributed across nodes without a per-core licence negotiationnot Lambda (AWS Serverless)
- Recommendation or fraud-detection features that traverse several hops at request time, where a relational join chain has become the bottlenecknot Lambda (AWS Serverless)
- Teams that want a graph database they can read, fork and self-host under a permissive licence rather than a source-available onenot Lambda (AWS Serverless)
Where do Lambda (AWS Serverless) and Dgraph fall short?
Lambda (AWS Serverless)'s most cited limit: ephemeral storage beyond the included 512 MB is metered. Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
Lambda (AWS Serverless)
- Billed on two axes at once, $0.20 per million requests plus $0.0000166667 per GB-second of duration, so memory settings change the bill as much as traffic does
- Provisioned concurrency, used to avoid cold starts, is charged separately at $0.0000041667 per GB-second whether or not the function runs
- Ephemeral storage beyond the included 512 MB is metered
- Lambda@Edge costs $0.60 per million requests, three times the standard request rate
- VPC use and cross-region data transfer carry EC2 charges on top
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
How much do Lambda (AWS Serverless) and Dgraph cost?
Lambda (AWS Serverless) is free to use; Dgraph has a free plan, with paid plans from $39/mo. Plan by plan below, from each vendor's own pricing page.
Lambda (AWS Serverless)
Free- Free TierFree
- 1M free requests/month
- 400,000 GB-seconds/month
- Always free
Dgraph
Free- CommunityFree
- Native GraphQL
- Graph queries
- Full-text search
- Cloud$39/mo
- Managed service
- Auto-scaling
- Enterprise support
Which should you pick?
Choose Lambda (AWS Serverless) if
- You need function-as-a-service.
- You want to start without paying.
- You work on Web, API.
- You also want event-driven execution.
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 Lambda (AWS Serverless) or Dgraph better?
- Neither clearly leads. Lambda (AWS Serverless) 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, Lambda (AWS Serverless) or Dgraph?
- Lambda (AWS Serverless) starts at Free and Dgraph at Free.
- Does Lambda (AWS Serverless) or Dgraph run on more platforms?
- Lambda (AWS Serverless) runs on Web, API. Dgraph runs on Linux, macOS, Self-hosted, Web.
- Can I use Lambda (AWS Serverless) for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is Lambda (AWS Serverless) best used for?
- Lambda (AWS Serverless) is most often used for event-driven functions without managing servers, api backends behind api gateway, processing s3, dynamodb, sqs and kinesis events, scheduled jobs without a always-on instance. Of those, event-driven functions without managing servers and api backends behind api gateway are not what Dgraph is typically brought in for.
- What can Lambda (AWS Serverless) do that Dgraph cannot?
- Lambda (AWS Serverless) covers Function-as-a-Service, Event-driven execution, Auto-scaling, Pay-per-use. Dgraph covers Apache 2.0 licence, Generated GraphQL API, DQL query language, Predicate sharding.
Answered from the vendors’ own pages
Lambda (AWS Serverless): Is there a free tier for AWS Lambda?
Yes. AWS Lambda offers a free tier including 1 million requests per month, 400,000 GB-seconds per month, and 100 GB monthly response streaming.
SourceDgraph: 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.
Lambda (AWS Serverless): How is AWS Lambda charged?
Lambda charges $0.20 per million requests. Duration charges are $0.0000166667 per GB-second for x86 (up to 6 billion GB-seconds/month in US East Ohio with tiered pricing). Ephemeral storage over the included 512 MB costs $0.0000000309 per GB-second. Provisioned Concurrency costs $0.0000041667 per GB-second with a 5-minute minimum.
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.
Lambda (AWS Serverless): What are Lambda Durable Functions pricing?
Lambda Durable Functions include operations at $8.00 per million (start execution, steps, waits). Data written costs $0.25 per GB. Data retention is $0.15 per GB-month with configurable 1-90 day retention (default 14 days).
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.
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.
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.
Related pages
More on Lambda (AWS Serverless)
Other head to heads
- Lambda (AWS Serverless) vs Deno Deploy
- Lambda (AWS Serverless) vs Cerebrium
- Lambda (AWS Serverless) vs Serverless Framework
- Lambda (AWS Serverless) vs Neon
- Lambda (AWS Serverless) vs Beam Cloud
- Lambda (AWS Serverless) vs Upstash
- Lambda (AWS Serverless) vs Koyeb
- Lambda (AWS Serverless) vs Azure Functions
- Lambda (AWS Serverless) vs Lambda
- Lambda (AWS Serverless) vs Porter
- Lambda (AWS Serverless) vs Terragrunt
- Lambda (AWS Serverless) vs Heroku
- Lambda (AWS Serverless) vs HAProxy
- Lambda (AWS Serverless) vs K3s
- Lambda (AWS Serverless) vs Proxmox VE
- Lambda (AWS Serverless) vs Buildah
- Lambda (AWS Serverless) vs CloudAMQP
- Lambda (AWS Serverless) vs Rancher
- Lambda (AWS Serverless) vs Neo4j
- Lambda (AWS Serverless) vs ArangoDB
- Lambda (AWS Serverless) vs Elasticsearch
- Lambda (AWS Serverless) vs Couchbase
- Lambda (AWS Serverless) vs Cassandra
- Lambda (AWS Serverless) vs FaunaDB
- Lambda (AWS Serverless) vs Firebase Realtime Database
- Lambda (AWS Serverless) vs RavenDB
- Lambda (AWS Serverless) vs ScyllaDB
- Lambda (AWS Serverless) vs Cockroach Labs
- Lambda (AWS Serverless) vs DynamoDB
- Lambda (AWS Serverless) vs Canary Labs
- Lambda (AWS Serverless) vs Chroma
- Lambda (AWS Serverless) vs Cloudinary
- Lambda (AWS Serverless) vs Convex
- Lambda (AWS Serverless) vs Dragonfly
- Lambda (AWS Serverless) vs Dremio
- Lambda (AWS Serverless) vs CouchDB
- Dgraph vs Deno Deploy
- Dgraph vs Cerebrium
- Dgraph vs Serverless Framework
- Dgraph vs Neon
- Dgraph vs Beam Cloud
- Dgraph vs Upstash
- Dgraph vs Koyeb
- Dgraph vs Azure Functions
- Dgraph vs Lambda
- Dgraph vs Porter
- Dgraph vs Terragrunt
- Dgraph vs Heroku
- Dgraph vs HAProxy
- Dgraph vs K3s
- Dgraph vs Proxmox VE
- Dgraph vs Buildah
- Dgraph vs CloudAMQP
- Dgraph vs Rancher
- 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 Canary Labs
- Dgraph vs Chroma
- Dgraph vs Cloudinary
- Dgraph vs Convex
- Dgraph vs Dragonfly
- Dgraph vs Dremio
- Dgraph vs CouchDB
