Neo4j vs Supabase
SEPT 2026 auditA comparison of Neo4j and Supabase built from values read directly from each provider's own documentation, with the source recorded against every figure.
The short answer
Choose Neo4j if…
Teams whose data is naturally relationships-first — recommendation engines, fraud detection, knowledge graphs — where the query itself is a graph traversal Cypher expresses directly and a relational join chain would not.
Editorial · Palash Bagchi · approved
Choose Supabase if…
Teams who want Postgres plus auth, storage and generated APIs from one vendor on a fixed monthly bill, and who would otherwise assemble those pieces themselves.
Editorial · Palash Bagchi · approved
Consider something else if…
- Neo4j: The data model is tabular and the graph shape is incidental — most CRUD apps fit a relational or document database better, and Neo4j's per-GB memory pricing is a worse fit for large flat datasets than a row-store.
- Supabase: You want only a database. Much of the $25 covers a platform you may not use, and free projects are paused after a week of inactivity, which is not the same as scaling to zero.
6 sourced criteria separate them — see where, with sources, below.
Pick the criteria you care about. The chart counts how many of them lean toward each provider — the same read as scanning the bars below, just totalled for the ones you chose.
Neo4j 0
Supabase 0
At a glance.
| Criterion | Neo4j | Supabase |
|---|---|---|
| Pricing | ||
| Free tier | Yes | Yes |
| Entry paid plan | $65/GB/month (minimum 1GB cluster) on AuraDB Professional, or $0.09/hour ($65.70/month for 1GB) metered hourly. 14-day free trial available. | $25/month for the Pro plan, including the first project and $10/mo of compute credits; additional projects from $10/mo |
| Pricing model | Usage-based, metered per GB-hour of memory on the Professional tier. A paused database cuts cost by roughly 80%. | Fixed monthly plan per organisation plus per-project compute, billed hourly by instance size |
| Infrastructure | ||
| Regions | AWS, Azure and Google Cloud, across more than 60 global cloud regions; also available through the AWS, Azure and Google Cloud marketplaces. | 17 specific AWS regions across the Americas, Europe, Asia-Pacific and South America, plus broader 'general region' groupings that place the project on an available AWS region within an area. General regions do not support read replicas or API management. |
| Data | ||
| Engine | Neo4j, a native property graph database. | PostgreSQL |
| Point-in-time recovery | Not included on the entry-paid (Professional) tier — point-in-time restore is a Business Critical feature, with hourly granularity and 30-day retention. | Point-in-time recovery is a paid add-on on Pro, Team and Enterprise, and needs at least a Small compute add-on alongside it. Worst-case recovery point is 2 minutes. Without it, restores go back only to a daily backup. |
| Read replicas | Supported | Supported |
| Backup retention | Daily backups, 7-day retention on the entry-paid (Professional) tier. Business Critical adds 30-day retention with hourly point-in-time restore; Virtual Dedicated Cloud gets hourly backups with 60-day retention. | Daily backups: 7 days on Pro, 14 days on Team, up to 30 days on Enterprise. Free projects get no automatic backups at all — Supabase tells free users to export their own data with the CLI. |
Where they differ.
Entry paid plan
- Neo4j
- $65/GB/month (minimum 1GB cluster) on AuraDB Professional, or $0.09/hour ($65.70/month for 1GB) metered hourly. 14-day free trial available.
- Supabase
- $25/month for the Pro plan, including the first project and $10/mo of compute credits; additional projects from $10/mo
Sources (2) →Sources ↓
- Neo4j Pricing ↗
“$65/GB/month, minimum 1GB cluster. 14-day free trial available. 1GB costs $0.09/hour or $65.70/month.”
Read 2026-09-11 · official pricing
- Pricing & Fees — Supabase ↗
“$25/month [...] First project included. Additional projects from $10/mo. [...] Paid plans include $10/mo in compute credits, enough to cover one Micro instance.”
Read 2026-09-05 · official pricing
Pricing model
- Neo4j
- Usage-based, metered per GB-hour of memory on the Professional tier. A paused database cuts cost by roughly 80%.
- Supabase
- Fixed monthly plan per organisation plus per-project compute, billed hourly by instance size
Sources (2) →Sources ↓
- Neo4j Pricing ↗
“Pause database, save 80% costs.”
Read 2026-09-11 · official pricing
- Pricing & Fees — Supabase ↗
“First project included. Additional projects from $10/mo. [...] Paid plans include $10/mo in compute credits, enough to cover one Micro instance.”
Read 2026-09-05 · official pricing
Regions
- Neo4j
- AWS, Azure and Google Cloud, across more than 60 global cloud regions; also available through the AWS, Azure and Google Cloud marketplaces.
- Supabase
- 17 specific AWS regions across the Americas, Europe, Asia-Pacific and South America, plus broader 'general region' groupings that place the project on an available AWS region within an area. General regions do not support read replicas or API management.
Sources (2) →Sources ↓
- Neo4j Pricing ↗
“Available on Azure, AWS, and Google Cloud. You can deploy AuraDB in over 60 global cloud regions.”
Read 2026-09-11 · official pricing
- Available regions — Supabase Docs ↗
“Each Supabase project is deployed to one primary region. [...] General regions deploy to an available AWS region within that broader area, which may not match a specific jurisdiction. For example, the "Europe" general region includes London and Zurich, which are not EU member states. Region selection is a data-location control, not proof of regulatory compliance. [...] General regions aren't yet supported for read replicas or management via the API.”
Read 2026-09-05 · official docs
Engine
- Neo4j
- Neo4j, a native property graph database.
- Supabase
- PostgreSQL
Sources (2) →Sources ↓
- Neo4j Aura documentation ↗
“Neo4j Aura is a fully automated graph platform offered as a cloud service.”
Read 2026-09-11 · official docs
- Connect to your database — Supabase Docs ↗
“The session mode connection string connects to your Postgres instance via the Shared Pooler (Supavisor).”
Read 2026-09-05 · official docs
Point-in-time recovery
- Neo4j
- Not included on the entry-paid (Professional) tier — point-in-time restore is a Business Critical feature, with hourly granularity and 30-day retention.
- Supabase
- Point-in-time recovery is a paid add-on on Pro, Team and Enterprise, and needs at least a Small compute add-on alongside it. Worst-case recovery point is 2 minutes. Without it, restores go back only to a daily backup.
Sources (2) →Sources ↓
- Neo4j Pricing ↗
“Business Critical: Daily backups with 30-day retention and hourly point-in-time restore.”
Read 2026-09-11 · official pricing
- Database Backups — Supabase Docs ↗
“Point-in-Time Recovery (PITR) allows you to back up a project at shorter intervals, giving you the option to restore to any chosen point with up to seconds of granularity. [...] Pro, Team and Enterprise Plan projects can enable PITR as an add-on. Projects that want to use PITR must also use at least a Small compute add-on to ensure smooth functioning. [...] in the worst case scenario, PITR achieves a Recovery Point Objective (RPO) of two minutes.”
Read 2026-09-05 · official docs
Backup retention
- Neo4j
- Daily backups, 7-day retention on the entry-paid (Professional) tier. Business Critical adds 30-day retention with hourly point-in-time restore; Virtual Dedicated Cloud gets hourly backups with 60-day retention.
- Supabase
- Daily backups: 7 days on Pro, 14 days on Team, up to 30 days on Enterprise. Free projects get no automatic backups at all — Supabase tells free users to export their own data with the CLI.
Sources (2) →Sources ↓
- Neo4j Pricing ↗
“Professional: Daily backups, 7-day retention. Business Critical: Daily backups with 30-day retention and hourly point-in-time restore. Virtual Dedicated Cloud: Hourly backups with 60-day retention.”
Read 2026-09-11 · official pricing
- Database Backups — Supabase Docs ↗
“We automatically back up all Pro, Team, and Enterprise Plan projects on a daily basis. [...] Pro Plan projects can access the last 7 days of daily backups. Team Plan projects can access the last 14 days of daily backups, while Enterprise Plan projects can access up to 30 days of daily backups. [...] We recommend that free tier plan projects regularly export their data using the Supabase CLI db dump command and maintain off-site backups.”
Read 2026-09-05 · official docs
When these numbers change, hear about it. Sources are re-checked monthly; a repricing goes out as a short note.
Documented by only one.
These criteria are published by one provider and not the other. An absence here means we have not found a source, not that the feature is missing.
Questions this comparison answers.
Entry paid plan: Neo4j or Supabase?
Neo4j: $65/GB/month (minimum 1GB cluster) on AuraDB Professional, or $0.09/hour ($65.70/month for 1GB) metered hourly. 14-day free trial available.
Supabase: $25/month for the Pro plan, including the first project and $10/mo of compute credits; additional projects from $10/mo
Should I choose Neo4j or Supabase?
Pick Neo4j if Teams whose data is naturally relationships-first — recommendation engines, fraud detection, knowledge graphs — where the query itself is a graph traversal Cypher expresses directly and a relational join chain would not.
Pick Supabase if Teams who want Postgres plus auth, storage and generated APIs from one vendor on a fixed monthly bill, and who would otherwise assemble those pieces themselves.