fshy

Home / Compute

Neo4j AuraDB

neo4j.com/pricing/Managed databasecompute/neo4j-auradbJSONcomparereport an errorprovider JSON

Free allowance
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'.
Verdict
caveatusable, with a named limit or an unprobed read path
Cost
free tier
Identity
emailno card, no phone
Binding limit
per-object-cap400,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.
Evidence
documented3 sources; a first-party page was read and the sentence quoted
Freshness
stale on 2026-11-22checked 2026-10-22 (live); stale on 2026-11-22
Free tierAuraDB 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
Pricenone stated
Limits
  • per-object-cap (binding) 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
Identityemail not published
Egressnot stated
Interfaceunknown inferred from the tooling the provider documents; not probed
Toolingnot stated
Composes with200,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.
Reliabilityno reliability event recorded
NotesFree 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.
Parsed numbers
  • has-free-tier 1
  • per-object-cap 1 GB
Evidence 3
datesourcewhat it proved
2026-10-22neo4j.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-22neo4j.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-22support.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
facets{"class": "graph-free-tier","free_tier_kind": "perpetual-free","shape": {"vcpu": null,"ram_gib": null,"disk_gib": 1}}
Unknown values 7
  • egress metered: egress metering was not published
  • egress terms: a source was read and is silent on this field
  • interface: the access interface was not established
  • per object cap stated: the field does not apply to this kind of offer
  • reliability note: nothing of this kind was observed
  • retention stated: the field does not apply to this kind of offer
  • tooling: a source was read and is silent on this field