Data & Storage · Integration
Neo4j Aura
Add Neo4j Aura to your product for your customers, and give your AI agents governed access to it.
Embed a Neo4j Aura integration so your product can query and update the graph a customer already runs as a managed service rather than asking them to ship the data to you. Aura is the hosted Neo4j graph database, so the objects your product works with are nodes, relationships, labels and properties, reached through Cypher queries. Each customer connects their own Aura instance with their own credentials, so every query is scoped to their tenant and logged, and a graph model that differs per customer is a mapping change rather than a release on your side. fastn handles the credential storage, retries, result pagination and API upkeep, and the same governed connection is what your AI agents query when they need to traverse relationships rather than rows.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Neo4j Aura instance so your product can read the graph they already maintain, with no per-customer code.
Run a parameterised Cypher query from your product to answer a relationship question that would be expensive in a relational store.
Write nodes and relationships back so a connection discovered in your product becomes part of the customer's own graph.
Support graph models that differ per customer, including their own labels and property names, as configuration rather than a branch in your code.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent traverses a customer's own graph to explain how two records are connected, within scoped permissions.
An agent answers a lineage or dependency question from the graph rather than guessing, with every read audited.
An agent writes a relationship it has verified back into the graph, with the write attributed to the tenant that authorised it.
Example prompt
Using our Neo4j Aura graph, show how this account is connected to the accounts that churned last quarter.
Set up Neo4j Aura in 4 steps
- 01Enable the Neo4j Aura connector in your fastn dashboard.
- 02Have each customer supply credentials for their own Aura instance so queries run on their database.
- 03Map the labels, properties and queries your product uses, per customer, as configuration.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Neo4j Aura integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Neo4j Aura integration without building it. Your customers connect their own Neo4j Aura account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Neo4j Aura update is not your on-call problem.
- One integration serves your product and your agents. The same governed Neo4j Aura connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
MongoDB
PostgreSQL
SnowflakeOften used alongside
Tools the same teams tend to run next to Neo4j Aura, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceNeo4j Aura integration FAQ
How do I add a Neo4j Aura integration to my product?
Enable the Neo4j Aura connector in your fastn dashboard, then let each customer authenticate their own Neo4j Aura account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Neo4j Aura client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Neo4j Aura account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Neo4j Aura account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Neo4j Aura integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent traverses a customer's own graph to explain how two records are connected, within scoped permissions.
Who maintains the Neo4j Aura integration?
fastn does. When Neo4j Aura changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the Neo4j Aura integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large Neo4j Aura reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the Neo4j Aura integration?
A common starting point: let each customer connect their own Neo4j Aura instance so your product can read the graph they already maintain, with no per-customer code. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Neo4j Aura integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Neo4j Aura does not change your per-connector cost. You can start free with 3 connected accounts.
Add Neo4j Aura to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.