# Supabase vs Turso

Canonical: https://inetgeek.com/compare/supabase-vs-turso/

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

## At a glance

| Criterion | Supabase | Turso |
| --- | --- | --- |
| Free tier | Yes | Yes |
| Entry paid plan | $25/month for the Pro plan, including the first project and $10/mo of compute credits; additional projects from $10/mo | $4.99/month for Developer, the cheapest paid plan. Scaler is $24.92 and Pro $416.58. |
| Pricing model | Fixed monthly plan per organisation plus per-project compute, billed hourly by instance size | Per database, metered on rows rather than compute time: 500 million rows read and 10 million written a month on the free plan, 2.5 billion and 25 million on Developer, with overage at $1 per billion rows read and $1 per million written. |
| Storage (entry plan) | 8 GB disk per project on the Pro plan; 500 MB on Free | 9 GB on Developer, then $0.75 per GB. The free plan includes 5 GB; Scaler is 24 GB at $0.50 and Pro 50 GB at $0.45. |
| Engine | PostgreSQL | SQLite, via libSQL — Turso's own fork. Not Postgres or MySQL, so the query surface and the client libraries differ from every other database on this site. |
| Database branching | Supported | Supported |
| Point-in-time recovery | 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. | 10 days on Developer. 1 day on the free plan, 30 days on Scaler and 90 days on Pro. |

## Where they differ

### Entry paid plan

- 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))
- Turso: $4.99/month for Developer, the cheapest paid plan. Scaler is $24.92 and Pro $416.58. ([source](https://turso.tech/pricing))

### Pricing model

- Supabase: Fixed monthly plan per organisation plus per-project compute, billed hourly by instance size ([source](https://supabase.com/pricing))
- Turso: Per database, metered on rows rather than compute time: 500 million rows read and 10 million written a month on the free plan, 2.5 billion and 25 million on Developer, with overage at $1 per billion rows read and $1 per million written. ([source](https://turso.tech/pricing))

### Storage (entry plan)

- Supabase: 8 GB disk per project on the Pro plan; 500 MB on Free ([source](https://supabase.com/pricing))
- Turso: 9 GB on Developer, then $0.75 per GB. The free plan includes 5 GB; Scaler is 24 GB at $0.50 and Pro 50 GB at $0.45. ([source](https://turso.tech/pricing))

### Engine

- Supabase: PostgreSQL ([source](https://supabase.com/docs/guides/database/connecting-to-postgres))
- Turso: SQLite, via libSQL — Turso's own fork. Not Postgres or MySQL, so the query surface and the client libraries differ from every other database on this site. ([source](https://turso.tech/pricing))

### Point-in-time recovery

- 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))
- Turso: 10 days on Developer. 1 day on the free plan, 30 days on Scaler and 90 days on Pro. ([source](https://turso.tech/pricing))

## Which should you choose?

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.

Pick Turso if Applications that want a database per tenant or per user — 100 databases on the free plan and unlimited above it make that a shape you can actually build.

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.

Consider something else: Turso — It is SQLite, not Postgres: the metered units are rows read and written rather than compute, and the extension ecosystem you may be relying on is not there.

## Documented by only one

- 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.
- 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
- Managed connection pooling: Supabase: Supported
- Regions: 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.
- 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
- Read replicas: Supabase: Supported
- Backup 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.
- 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: Supabase or Turso?**

Supabase: $25/month for the Pro plan, including the first project and $10/mo of compute credits; additional projects from $10/mo
Turso: $4.99/month for Developer, the cheapest paid plan. Scaler is $24.92 and Pro $416.58.

**Storage (entry plan): Supabase or Turso?**

Supabase: 8 GB disk per project on the Pro plan; 500 MB on Free
Turso: 9 GB on Developer, then $0.75 per GB. The free plan includes 5 GB; Scaler is 24 GB at $0.50 and Pro 50 GB at $0.45.

**Should I choose Supabase or Turso?**

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.
Pick Turso if Applications that want a database per tenant or per user — 100 databases on the free plan and unlimited above it make that a shape you can actually build.