# Supabase vs TigerData

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

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

## At a glance

| Criterion | Supabase | TigerData |
| --- | --- | --- |
| Entry paid plan | $25/month for the Pro plan, including the first project and $10/mo of compute credits; additional projects from $10/mo | Compute starts at $30/month on Performance, billed hourly, with storage charged separately. Scale starts at $36/month. |
| Pricing model | Fixed monthly plan per organisation plus per-project compute, billed hourly by instance size | Compute and storage are billed separately and hourly rather than as one plan price — compute from $30 a month, storage at $0.177 per GB-month, with the headline storage figure resting on an assumed 5x compression ratio. |
| Engine | PostgreSQL | PostgreSQL with TimescaleDB, aimed at time-series, real-time analytics and events. A self-managed edition exists for on-prem and private cloud. |
| 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. | 3 days on Performance, with cross-region backups available for disaster recovery on higher tiers. |
| Read replicas | Supported | Supported |

## 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))
- TigerData: Compute starts at $30/month on Performance, billed hourly, with storage charged separately. Scale starts at $36/month. ([source](https://www.tigerdata.com/pricing))

### Pricing model

- Supabase: Fixed monthly plan per organisation plus per-project compute, billed hourly by instance size ([source](https://supabase.com/pricing))
- TigerData: Compute and storage are billed separately and hourly rather than as one plan price — compute from $30 a month, storage at $0.177 per GB-month, with the headline storage figure resting on an assumed 5x compression ratio. ([source](https://www.tigerdata.com/pricing))

### Engine

- Supabase: PostgreSQL ([source](https://supabase.com/docs/guides/database/connecting-to-postgres))
- TigerData: PostgreSQL with TimescaleDB, aimed at time-series, real-time analytics and events. A self-managed edition exists for on-prem and private cloud. ([source](https://www.tigerdata.com/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))
- TigerData: 3 days on Performance, with cross-region backups available for disaster recovery on higher tiers. ([source](https://www.tigerdata.com/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 TigerData if Time-series and analytics workloads that want to stay in Postgres — TimescaleDB's compression is the reason the storage line is affordable at volume.

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: TigerData — The advertised storage price assumes 5x compression, so a workload that does not compress that well pays materially more than the figure suggests.

## 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
- 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
- Database branching: 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.
- Storage price: TigerData: $0.177 per GB-month on Performance and $0.212 on Scale. TigerData notes the effective price assumes 5x compression, which is an average rather than a guarantee.
- 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 TigerData?**

Supabase: $25/month for the Pro plan, including the first project and $10/mo of compute credits; additional projects from $10/mo
TigerData: Compute starts at $30/month on Performance, billed hourly, with storage charged separately. Scale starts at $36/month.

**Should I choose Supabase or TigerData?**

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 TigerData if Time-series and analytics workloads that want to stay in Postgres — TimescaleDB's compression is the reason the storage line is affordable at volume.