Neo4j · Rate Limits

Neo4J Rate Limits

Neo4j is a graph database; capacity scales with instance size (RAM, CPUs, storage) rather than per-second HTTP throttling. The Aura management API and Query API do not publish explicit RPS limits. The AuraDB Free tier limits node and relationship counts. Bolt protocol concurrency depends on the chosen instance size.

Neo4J Rate Limits is the machine-readable rate-limit profile for Neo4j on the APIs.io network, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring nodes_relationships and varies.

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled and serviceUnavailable.

Tagged areas include Rate Limiting, Graph Database, and AuraDB.

3 Limits Exhausted: HTTP 429
Method: generated, dated 2026-05-05.
Written by API Evangelist on 2026-05-05 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Rate LimitingGraph DatabaseAuraDB

Limits

AuraDB Free node + relationship count instance
nodes_relationships
see AuraDB Free tier docs
Free tier limits node and relationship counts rather than request rate.
AuraDB Professional / Business Critical capacity instance
varies
bound by selected GB RAM, CPU, storage
Throughput scales with selected size (1-512 GB RAM, 1-96 CPU cores).
Aura Console / Query API account
varies
see Aura API specification
No explicit RPS limit published in the public Aura API specification.

Policies

Capacity-based scaling
Right-size AuraDB instance memory and CPU to handle target query throughput; Neo4j sizing guidance recommends measuring p95 query latency under load and scaling vertically.
Connection pooling
Use the official Neo4j drivers' connection pool; do not open a new Bolt session per request. Default pool size is 100 connections per driver instance.
Query timeouts
Set `dbms.transaction.timeout` to bound long-running Cypher queries on self-managed Enterprise; AuraDB applies platform timeouts.
Backpressure on free tier
Free tier reaches node/relationship caps; queries that would exceed the cap fail. Upgrade to Professional for production volumes.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/neo4j-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.