The startup’s guide to getting started building on Neo4j Aura

You’ve got credits for Neo4j Aura — this guide covers everything you need to start building your graph applications : what to install first, how to size your instance, which Neo4j projects fit your use case, and the mistakes we’ve already watched other startups make.

Install the agent skills first

Everything else in this post gets easier once your coding agent knows Neo4j. Install the Neo4j CLI (https://neo4j.sh), pull the full skills catalog into every Agent Skills compatible tool it finds on your machine, and turn on auto-refresh so your skills don’t go stale the next time on any Neo4j feature updates.

curl -sSfL https://neo4j.sh/install.sh | bash
neo4j-cli skill install --all --rw
neo4j-cli config set skill-auto-refresh true --rwCode language: JavaScript (javascript)

Auto-refresh is on by default, but setting it explicitly means you know it’s there. That matters for the rest of this post too: a few sections below point you to a prompt instead of a paragraph, because your agent’s answer stays current long after this page stops being updated.

Build something in one sitting

Tell the flagship neo4j-getting-started-skillwhat you’re building, in plain language, something like “fraud detection for a fintech startup.” It provisions a database, designs the schema, loads sample data, and generates a runnable app end to end. It’s a strong starting point you can build from and iterate on.

Size your instance without guessing

Sizing your instance well means understanding the size of your graph (nodes, relationships, and average properties per node and relationship), the number and types of indexes you use, your query patterns, and your concurrent load. The specifics shift as Aura’s tiers and tooling evolve, so ask your agent directly:

using the neo4j skills, give me the latest best practices for sizing an Aura instance

A few starting points while you’re at it:

• Sizing for Neo4j Aura (support article): https://support.neo4j.com/s/article/17151196982291-Sizing-for-Neo4j-Aura
• Instance resources (monitoring CPU, storage, and query metrics): https://neo4j.com/docs/aura/managing-instances/instance-resources/
• Troubleshooting (memory limit errors and how to fix them): https://neo4j.com/docs/aura/tutorials/troubleshooting/

And the tiers themselves, if you just want the numbers:

• Free: $0. Learn and prototype, with one free instance per account and every graph tool included.
• Professional: $65/GB/month, 1GB minimum. Up to 128GB memory per instance, scalable on demand, daily backups.
• Business Critical: $146/GB/month, 2GB minimum. Up to 1944GB (GCP) or 512GB (AWS/Azure), a 99.95% uptime SLA, and 24×7 support.

Storage is available of up to 1:16 memory ratio.
Full comparison: https://neo4j.com/pricing

Four Neo4j tools worth a look

You don’t need all of these on day one. Start with whichever matches what you’re building:

• GraphRAG: neo4j-graphrag-python (https://neo4j.com/docs/neo4j-graphrag-python/current/) builds retrieval, RAG and knowledge graph construction pipelines on top of your graph.
• MCP server: the Neo4j MCP server (https://neo4j.com/docs/mcp/current/) lets coding and production agents query your live database directly — both locally and on Aura.
• GDS: Graph Data Science (https://neo4j.com/docs/graph-data-science/current/) runs algorithms for fraud detection, recommendations, and pattern-finding (either as database plugin or serverless sessions).
• Agent memory (Neo4j Labs) : neo4j-agent-memory (https://neo4j.com/labs/agent-memory/), also known as Neo4j Agent Memory Service (NAMS), gives conversational agents persistent, structured memory.

Repeated anti-patterns we see

Real patterns, not hypotheticals:

• Duplicate applications. Same company, two applications? Check with your team before redeeming a second code.
• The credit clock. Your 12-month clock starts when you receive your credit code by email, not when you redeem it or get approved.
• Tier upgrades. Applying for additional credits after a funding round? Wait until about a month before your current credits expire to apply, so your new 12-month window starts as late as possible and you don’t risk losing unused credits to expiration.
• A single owner on your Aura organization. Add more than one person with the Owner role, and make your founder a co-owner even if they’re not technical. If the only listed owner leaves the company, proving account ownership for security and fraud checks gets hard fast. Losing your last owner? Suspend their email account instead of deleting it, so you can still prove you had access to it when verification comes up.

Level up with GraphAcademy

GraphAcademy (https://graphacademy.neo4j.com) is Neo4j’s free online learning platform, offering curated sequences of hands-on lessons, labs, and quizzes — each path takes you from first principles to shipping something real. Free, hands-on courses, no prior graph experience required:

• Data Modeling Fundamentals (https://graphacademy.neo4j.com/courses/modeling-fundamentals): the foundation for getting your schema right from day one.
• Data Science Fundamentals (https://graphacademy.neo4j.com/courses/gds-fundamentals/): centrality, community detection, and more.
• Neo4j and Generative AI Workshop (https://graphacademy.neo4j.com/courses/genai-workshop-graphrag/): GraphRAG pipelines, vector search, and retrieval agents.

Harden your application

Locking down your drivers, connections, and how you write data at load time is what separates a demo from something that holds up under real traffic. Ask your agent for the current playbook:

using the neo4j skills, give me the latest best practices for drivers and data ingestion on Aura

Background reading: Neo4j driver best practices (https://neo4j.com/blog/developer/neo4j-driver-best-practices/)

When you’re ready to start load testing your application, run through this:

• Load test first. Confirm your app holds up at peak load, not just average.
• Lock down the connection. Use neo4j+s and confirm access controls before launch.
• Know where to look. Turn on query logging and know your support channels.

Where to get help

You’re not building this alone.

Aura’s built-in tools are the fastest way to get moving, no extra setup required:

• Aura Agent (https://neo4j.com/docs/aura/aura-agent/): build and deploy AI agents grounded in your graph.
• Document Intelligence (https://neo4j.com/docs/aura/document-intelligence/introduction/): turn documents into a knowledge graph.
• Data Importer (https://neo4j.com/docs/data-importer/current/introduction/): import your data with a visual, no-code mapper.
• Aura MCP (https://neo4j.com/docs/mcp/current/): connect coding and production agents straight to your graph.

And when you need a person, not a tool:

• Your SE team: reach out any time for architecture questions, code review, or a sanity check. We also run dedicated technical sessions if you want to go deeper on something with us directly.
• Docs and community: Cypher cheat sheets (https://neo4j.com/docs/cypher-cheat-sheet/current/), GraphAcademy courses, and the Neo4j community forum (https://dev.neo4j.com/forum) for peer answers.
• Support portal (https://support.neo4j.com/s/): set up your access now, before you need it, so filing a ticket for account or technical issues is fast when the moment comes.

---