×
Cloudflare
×
Cloudflare
Cloudflare already runs DNS and the edge for neo4j.com — yet www, assets and media still ride a second CDN (AWS CloudFront) in front of an AWS origin. Fold the CDN, object storage, API protection, identity and AI-governance layers onto the one network already in front of you. You own the graph; Cloudflare secures and accelerates everything around it.
Neo4j has repositioned the graph database as “the knowledge layer that makes AI accurate” — powering Agentic GraphRAG so LLMs and agents reason over connected enterprise data. That puts Neo4j squarely in the path of customer AI traffic, where governance, cost control and audit logging matter as much as latency.
Recent signals: Neo4j is acquiring GraphAware (intelligence-analysis software for government agencies) — raising the bar on security and access control; an IDC study validated $4M in annual value and a 7.8-month payback; and the platform now spans 80+ of the Fortune 100, 300k developers and 170+ partners (Merck, Uber, BNP Paribas, Intuit, Transport for London).
The opportunity: Neo4j already trusts Cloudflare for apex DNS and edge, but its public surface is split across AWS CloudFront + ALB, Auth0, Google Workspace, Atlassian, Salesforce and more. Consolidating onto Cloudflare cuts a second CDN bill, removes egress tax, and unifies security and AI governance under one control plane — without touching the graph engine itself.
Neo4j already pays Cloudflare for the apex, but www, auth, assets and media still resolve to CloudFront. Point those hostnames at Cloudflare and run a single edge — one cache, one WAF, one bill.
The marketing and docs assets on dist.neo4j.com are served from AWS through CloudFront. R2 charges $0 egress — an ideal origin for assets, docs, downloads and database backups feeding the web.
Responses set an AWSALB cookie — the public site fronts an AWS Application Load Balancer. Keep AWS, but hide it: Magic Transit / Aegis put Cloudflare’s L3-L7 DDoS and origin cloaking in front of it.
The most-loaded third-party origin on the homepage is console.neo4j.io — the AuraDB control plane. API Shield discovers every endpoint and enforces schema, auth and volumetric limits inline at the edge.
With 300k developers and open docs, GraphAcademy and a public signup, the funnel is a magnet for scrapers, credential stuffing and fake-account abuse. WAF + Bot Management filter it before it hits origin or Auth0.
Support and enablement run on external SaaS — help.neo4j.com (Atlassian), support.neo4j.com (Salesforce Service Cloud) and SalesHood. Cloudflare Access puts identity-aware, device-posture-checked gates in front of each.
Neo4j’s whole story is the knowledge layer for AI and Agentic GraphRAG. You own the graph — Cloudflare AI Gateway puts a governed front door on the LLM/agent calls around it: caching, rate-limits, spend caps and full request logging.
Mail runs on Google Workspace with DMARC managed via EasyDMARC. Cloudflare Email Security layers in front to stop phishing, BEC and malicious links — critical as Neo4j moves into government-grade intelligence work.
| Function | Today | How it was identified | On Cloudflare |
|---|---|---|---|
| CDN / edge | Cloudflare + AWS CloudFront | cf-ray on apex; www/assets → cloudfront.net; x-amz-cf-pop | Consolidate on Cloudflare |
| Origin load balancer | AWS ALB | AWSALB / AWSALBCORS cookies | Magic Transit / Aegis (shield) |
| Asset / docs storage | AWS (dist.neo4j.com) | dist.neo4j.com served via CloudFront | R2 (egress-free) |
| Product APIs | console.neo4j.io / Aura | most-loaded origin on homepage (9×) | API Shield |
| Identity | Auth0 | login.neo4j.com → edge.tenants.auth0.com | Access / Zero Trust (augment) |
| Google Workspace | MX ASPMX.L.GOOGLE.com; SPF easydmarc.pro | Email Security (augment) | |
| Support / help | Atlassian JSM + Salesforce | help → saas.atlassian.com; support → siteforce.com | Zero Trust Access |
| Sales enablement | SalesHood | .saleshood.com in CSP | Zero Trust Access |
| A/B testing | VWO | dev.visualwebsiteoptimizer.com on page | Workers (edge experiments) |
| AI / GraphRAG traffic | Ungoverned LLM calls | “knowledge layer for AI” positioning | AI Gateway (augment) |