Crunchy Bridge vs Supabase
SEPT 2026 auditA comparison of Crunchy Bridge and Supabase built from values read directly from each provider's own documentation, with the source recorded against every figure.
The short answer
Choose Crunchy Bridge if…
Anyone who wants Postgres and nothing else, from people who work on Postgres. Ten days of per-minute recovery is included in the price of every cluster rather than sold as a tier, and replicas can sit in another region or another cloud.
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…
- Crunchy Bridge: You need a free plan to start on, or a second database engine later. This is a single-engine paid service.
- 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.
7 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.
Crunchy Bridge 0
Supabase 0
At a glance.
| Criterion | Crunchy Bridge | Supabase |
|---|---|---|
| Pricing | ||
| Entry paid plan | $9 a month for Hobby-0 — 2 cores, 512 MB, AWS only. Crunchy says the Hobby tier runs on lower-quality infrastructure, has no PgBouncer and is not intended for production; the first production tier is Standard-4 at $70 a month for 1 core and 4 GB. There is no free plan. | $25/month for the Pro plan, including the first project and $10/mo of compute credits; additional projects from $10/mo |
| Pricing model | Billed for the time a cluster is provisioned, prorated to the second, with the monthly figures on the plans page being what a full month costs. Price varies by instance size, region and storage. Three tiers — Hobby, Standard and Memory-optimized — where the tier decides IOPS, whether PgBouncer is included and what support you get, not just the size. | Fixed monthly plan per organisation plus per-project compute, billed hourly by instance size |
| Execution | ||
| Managed connection pooling | Supported | Supported |
| Infrastructure | ||
| Regions | 37 regions across three clouds — 16 on AWS, 14 on Google Cloud, 7 on Azure — counted from the region tables on Crunchy's own plans page, which lists them and publishes no total. | 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 | PostgreSQL only. Crunchy Bridge is a single-engine service — there is no MySQL or analytics product beside it in the same offering — and it runs on all three major clouds so the database can sit next to whatever else you already run. | PostgreSQL |
| Database branching | Limited — a new cluster restored from backup, to any minute in 10 days | Supported |
| Point-in-time recovery | Any minute inside the 10 days of retained backups. The WAL is streamed every 60 seconds or 16 MB, whichever comes first, and a restore produces a fork of the cluster rather than replacing it. | 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 | 10 days, included in the cluster price rather than sold as a tier, and extendable by configuring additional daily, weekly, monthly and yearly backups to keep. | 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
- Crunchy Bridge
- $9 a month for Hobby-0 — 2 cores, 512 MB, AWS only. Crunchy says the Hobby tier runs on lower-quality infrastructure, has no PgBouncer and is not intended for production; the first production tier is Standard-4 at $70 a month for 1 core and 4 GB. There is no free plan.
- 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 ↓
- Plans and pricing — Crunchy Bridge Documentation ↗
“In general, Hobby tier runs on lower quality underlying infrastructure, does not include PgBouncer, and is not intended for production usage. [...] Hobby-0* 2 512MB 5% 11,800 PG15-18 only ❌ ⚠️ Best effort $9.00 [...] Standard-4* 1 4GB 20,000 PG14-18 ✅ ✅ $70.00 [...] *Available on AWS only.”
Read 2026-09-09 · official docs
- 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
- Crunchy Bridge
- Billed for the time a cluster is provisioned, prorated to the second, with the monthly figures on the plans page being what a full month costs. Price varies by instance size, region and storage. Three tiers — Hobby, Standard and Memory-optimized — where the tier decides IOPS, whether PgBouncer is included and what support you get, not just the size.
- Supabase
- Fixed monthly plan per organisation plus per-project compute, billed hourly by instance size
Sources (2) →Sources ↓
- Plans and pricing — Crunchy Bridge Documentation ↗
“Clusters are billed according to the amount of time they're provisioned in a given month, prorated to the second. While prices on this page are quoted for the cost of an entire month, you will only be billed that amount if your cluster is provisioned for the entire month. Pricing varies based on: Instance size Region Storage [...] Crunchy Bridge offers three tiers of databases -- Hobby, Standard, and Memory -- to cover a variety of use cases.”
Read 2026-09-09 · official docs
- 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
37 regions across three clouds — 16 on AWS, 14 on Google Cloud, 7 on Azure — counted from the region tables on Crunchy's own plans page, which lists them and publishes no total.
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 ↓
- Plans and pricing — Crunchy Bridge Documentation ↗
“Regions Amazon Web Services (AWS) Name Provider ID Asia Pacific (Tokyo) ap-northeast-1 Asia Pacific (Mumbai) ap-south-1 [...] US West (Oregon) us-west-2 Azure Name Provider ID Australia East (NSW) australiaeast [...] Google Cloud Platform (GCP) Name Provider ID Asia Northeast 1 (Tokyo) asia-northeast1”
Read 2026-09-09 · official docs
- 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
- Crunchy Bridge
- PostgreSQL only. Crunchy Bridge is a single-engine service — there is no MySQL or analytics product beside it in the same offering — and it runs on all three major clouds so the database can sit next to whatever else you already run.
- Supabase
- PostgreSQL
Sources (2) →Sources ↓
- Crunchy Bridge — Crunchy Bridge Documentation ↗
“Crunchy Bridge is a fully managed Postgres service from Crunchy Data. It takes care of running and managing Postgres so that you can stay focused on building your applications, not on keeping your database up and running. Bridge provides highly available Postgres across every major cloud provider — Amazon Web Services, Google Cloud Platform, and Microsoft Azure — so regardless of where you're running, you can closely colocate your database.”
Read 2026-09-09 · 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
Database branching
- Crunchy Bridge
- Limited — a new cluster restored from backup, to any minute in 10 days
- Supabase
- Supported
Sources (2) →Sources ↓
- Backups — Crunchy Bridge Documentation ↗
“The automated daily backups are stored along with the associated WAL and can be used to create a point-in-time recovery fork of your cluster. [...] Forking from backup You can create a new fork from any of the backups stored for your cluster by clicking the "Fork from Backup" button. This process will create a new cluster according to the options you specify, and the new cluster will be populated with the data from the backup. Info Remember, each fork will have its own unique connection string.”
Read 2026-09-09 · official docs
- Pricing & Fees — Supabase ↗
“Branching [...] $0.01344 per branch, per hour”
Read 2026-09-05 · official pricing
Point-in-time recovery
- Crunchy Bridge
- Any minute inside the 10 days of retained backups. The WAL is streamed every 60 seconds or 16 MB, whichever comes first, and a restore produces a fork of the cluster rather than replacing it.
- 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 ↓
- Backups — Crunchy Bridge Documentation ↗
“kept current by streaming the WAL every 60 seconds or 16MB (whichever comes first). 10 days of these backups will be retained by the platform automatically. These backups can be used to restore a fork of your cluster to any minute in its history.”
Read 2026-09-09 · official docs
- 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
10 days, included in the cluster price rather than sold as a tier, and extendable by configuring additional daily, weekly, monthly and yearly backups to keep.
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 ↓
- Backups — Crunchy Bridge Documentation ↗
“10 days of these backups will be retained by the platform automatically. [...] By default, Crunchy Bridge automatically captures and retains the most recent 10 days' worth of backups for each cluster. That is included in the price of each cluster.”
Read 2026-09-09 · official docs
- 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: Crunchy Bridge or Supabase?
Crunchy Bridge: $9 a month for Hobby-0 — 2 cores, 512 MB, AWS only. Crunchy says the Hobby tier runs on lower-quality infrastructure, has no PgBouncer and is not intended for production; the first production tier is Standard-4 at $70 a month for 1 core and 4 GB. There is no free plan.
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 Crunchy Bridge or Supabase?
Pick Crunchy Bridge if Anyone who wants Postgres and nothing else, from people who work on Postgres. Ten days of per-minute recovery is included in the price of every cluster rather than sold as a tier, and replicas can sit in another region or another cloud.
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.