# ScaleGrid vs Supabase

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

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

## At a glance

| Criterion | ScaleGrid | Supabase |
| --- | --- | --- |
| Free tier | No | Yes |
| Pricing model | Two models: Dedicated Hosting, an all-inclusive plan covering machine, disk and network cost; or Bring Your Own Cloud (BYOC), management-only pricing where the cloud provider is billed separately. | Fixed monthly plan per organisation plus per-project compute, billed hourly by instance size |
| Regions | Six cloud providers: AWS, Google Cloud, Microsoft Azure, DigitalOcean, Oracle Cloud (OCI) and Akamai. Specific regional availability is not published on the pricing or product pages. | 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 | MySQL, PostgreSQL, MongoDB, Redis, RabbitMQ and SQL Server. | PostgreSQL |
| Backup retention | Up to five backups per deployment on ScaleGrid's dedicated hosting plans. | 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

### Free tier

- ScaleGrid: No ([source](https://scalegrid.io/pricing.html))
- Supabase: Yes ([source](https://supabase.com/pricing))

### Pricing model

- ScaleGrid: Two models: Dedicated Hosting, an all-inclusive plan covering machine, disk and network cost; or Bring Your Own Cloud (BYOC), management-only pricing where the cloud provider is billed separately. ([source](https://scalegrid.io/pricing.html))
- Supabase: Fixed monthly plan per organisation plus per-project compute, billed hourly by instance size ([source](https://supabase.com/pricing))

### Regions

- ScaleGrid: Six cloud providers: AWS, Google Cloud, Microsoft Azure, DigitalOcean, Oracle Cloud (OCI) and Akamai. Specific regional availability is not published on the pricing or product pages. ([source](https://scalegrid.io/mysql.html))
- 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

- ScaleGrid: MySQL, PostgreSQL, MongoDB, Redis, RabbitMQ and SQL Server. ([source](https://scalegrid.io/pricing.html))
- Supabase: PostgreSQL ([source](https://supabase.com/docs/guides/database/connecting-to-postgres))

### Backup retention

- ScaleGrid: Up to five backups per deployment on ScaleGrid's dedicated hosting plans. ([source](https://scalegrid.io/pricing.html))
- 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 ScaleGrid if Teams that already have a favored database engine and cloud provider but want someone else operating it — the BYOC model bills infrastructure at cost and adds management on top, worth it if the operational burden is the actual problem.

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: ScaleGrid — The workload fits a single-engine specialist with its own scale-to-zero or branching model — ScaleGrid's value is operating an engine you already chose, not offering a distinctive one.

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

- 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
- 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.
- Startup credit program: ScaleGrid: Startup Saver: up to 50% discount on ScaleGrid hosting for 12 months.
- 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
- 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
- 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.
- Read replicas: Supabase: Supported
- 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

**Free tier: ScaleGrid or Supabase?**

ScaleGrid: No
Supabase: Yes

**Should I choose ScaleGrid or Supabase?**

Pick ScaleGrid if Teams that already have a favored database engine and cloud provider but want someone else operating it — the BYOC model bills infrastructure at cost and adds management on top, worth it if the operational burden is the actual problem.
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.