# Crunchy Bridge vs Supabase

Canonical: https://inetgeek.com/compare/crunchy-bridge-vs-supabase/

Every value below is read from Crunchy Bridge's and Supabase's own documentation. See https://inetgeek.com/methodology/ for how.

## At a glance

| Criterion | Crunchy Bridge | Supabase |
| --- | --- | --- |
| 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 |
| Managed connection pooling | Supported | Supported |
| 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. |
| 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. ([source](https://docs.crunchybridge.com/concepts/plans-pricing))
- Supabase: $25/month for the Pro plan, including the first project and $10/mo of compute credits; additional projects from $10/mo ([source](https://supabase.com/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. ([source](https://docs.crunchybridge.com/concepts/plans-pricing))
- Supabase: Fixed monthly plan per organisation plus per-project compute, billed hourly by instance size ([source](https://supabase.com/pricing))

### Regions

- Crunchy Bridge: 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. ([source](https://docs.crunchybridge.com/concepts/plans-pricing))
- 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. ([source](https://supabase.com/docs/guides/platform/regions))

### 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. ([source](https://docs.crunchybridge.com/))
- Supabase: PostgreSQL ([source](https://supabase.com/docs/guides/database/connecting-to-postgres))

### Database branching

- Crunchy Bridge: Limited — a new cluster restored from backup, to any minute in 10 days ([source](https://docs.crunchybridge.com/concepts/backups))
- Supabase: Supported ([source](https://supabase.com/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. ([source](https://docs.crunchybridge.com/concepts/backups))
- 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. ([source](https://supabase.com/docs/guides/platform/backups))

### Backup retention

- Crunchy Bridge: 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. ([source](https://docs.crunchybridge.com/concepts/backups))
- 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. ([source](https://supabase.com/docs/guides/platform/backups))

## Which should you choose?

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.

Consider something else: Crunchy Bridge — You need a free plan to start on, or a second database engine later. This is a single-engine paid service.

Consider something else: 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.

## Documented by only one

- Free tier: Supabase: Yes
- Egress over allowance: Supabase: $0.09 per GB for uncached egress and $0.03 per GB for cached, charged only above the plan's quota. Egress restrictions clear at the next billing cycle, or immediately on upgrading or disabling the spend cap.
- Storage (entry plan): Supabase: 8 GB disk per project on the Pro plan; 500 MB on Free
- Included bandwidth: Supabase: 250 GB uncached and 250 GB cached egress a month on Pro and Team, pooled across Database, Auth, Storage and every other service as one Unified Egress Quota
- Connection limit: Supabase: 60 direct and 200 pooled connections on the Micro instance included with Pro; both scale with instance size
- When idle: Supabase: Free projects are paused after one week of inactivity and must be restored manually; paid projects are not paused
- SOC 2: Supabase: SOC 2 Type 2 compliant; report available to Enterprise and Team customers via the dashboard.
- ISO 27001: Supabase: ISO 27001 certified; certificate available to Enterprise and Team customers via the dashboard.
- HIPAA: Supabase: HIPAA compliant; customers may store PHI after signing a BAA and meeting shared-responsibility obligations.
- GDPR / data residency: Supabase: Projects hosted in EU regions keep primary database data in-region; a DPA is available.
- Encryption at rest: Supabase: AES-256 at rest and TLS in transit; sensitive tokens/keys get application-level encryption before storage.
- Role-based access control: Supabase: Organization members can be granted access to specific resources, including read-only and billing-only roles.

## 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.