Neo4j AuraDB

neo4j.com · Compute · 1 record · JSON

Neo4j AuraDB Compute

caveatemailno cardDper-object-cap

neo4j.com/pricing/ · managed database · compute/neo4j-auradb · JSON · compare

Free tier	AuraDB Free, quoted from the quotas page: 'AuraDB Free: A perpetual free tier for learning, prototyping, and small projects' with Nodes '200,000', Relationships '400,000' and Storage '1GB'. Vendor support adds: 'after a period of 72 hours of inactivity, we will automatically pause it ... If the database remains paused for 30 days, it will be deleted by the system.' unit hours; metered on wall-clock; perpetual-free
Price	none stated
Per-object cap	not applicable
Retention	not applicable
Egress	not stated
Identity	email not published
Limits	per-object-cap 400,000 relationships caps a graph before the node count does for any connected dataset, because the average degree in a real graph is above 2; the 1 GB storage ceiling is the third constraint and usually arrives at the same time. source 400,000 relationships caps a graph before the node count does for any connected dataset, because the average degree in a real graph is above 2; the 1 GB storage ceiling is the third constraint and usually arrives at the same time.
Binding	per-object-cap 400,000 relationships caps a graph before the node count does for any connected dataset, because the average degree in a real graph is above 2; the 1 GB storage ceiling is the third constraint and usually arrives at the same time.
Interface	unknown inferred from the tooling the provider documents; not probed
Tooling	not stated
Composes with	200,000 nodes and 400,000 relationships is a complete citation graph or a mid-sized knowledge graph, and Aura's Cypher is the same query language as the open-source server, so a graph built here moves to a rented container unchanged.
Reliability	no reliability event recorded
Notes	Free instances run on GCP us-central1 only, cannot be paused by the user, and have on-demand backups only. A read-only query does not reset the 72-hour timer, because inactivity is defined as no updates or write queries, so a monitoring ping that only reads will not keep the graph awake. The graphacademy course page states the same limits.
Evidence rung	documented
Checked	2026-10-22 (live); stale on 2026-11-21
Parsed numbers	`$.limits[0].value` limit:per-object-cap 1.0 GB

Evidence (3)

date	source	what it proved
2026-10-22	neo4j.com/docs/aura/quotas-and-limits/	'AuraDB Free: A perpetual free tier for learning, prototyping, and small projects' with Nodes 200,000, Relationships 400,000, Storage 1GB, quoted
2026-10-22	neo4j.com/pricing/	AuraDB Free is 'Starting at $0'; the plan table lists 'Auto-pause/resume' as included, backups 'Not Included' to 'On-demand', and 'Available Zone' as single-zone
2026-10-22	support.neo4j.com/s/article/4406830696083-Why-is-my-AuraDB-F	'after a period of 72 hours of inactivity, we will automatically pause it ... If the database remains paused for 30 days, it will be deleted by the system', quoted

More fields (1)

{
 "wave2": {
  "class": "graph-free-tier",
  "free_tier_kind": "perpetual-free",
  "shape": {
   "vcpu": null,
   "ram_gib": null,
   "disk_gib": 1
  }
 }
}

Unknown or withheld values (10)

$.egress.metered egress-unknown
$.egress.terms not-stated
$.identity_cost.detail process
$.interface interface-unknown
$.per_object_cap.notes process
$.per_object_cap.stated not-applicable
$.reliability_note none-observed
$.retention.notes process
$.retention.stated not-applicable
$.tooling not-stated