Supabase PRO pricing & rate limits

Supabase positions its managed PostgreSQL offering as a direct competitor to AWS RDS, though it abstracts much of the underlying infrastructure complexity. Entry-level tiers start at $25.00/mo, which provides 1 GB of RAM and 2 vCPU cores. At the high end of the spectrum, costs reach $7460.00/mo, scaling resources up to 256 GB of RAM and 128 vCPU cores. While the RAM and core counts are generous for standard relational workloads, the included disk storage is fixed at 8 GB across the board, requiring immediate planning for extra volume provisioning.

• Exceeding the base storage allocation triggers a predictable $0.13/GB monthly overage fee, which is standard for managed cloud databases.
• Network egress is metered after initial thresholds, with additional data transfer billed at $0.09/GB.
• The platform relies on underlying AWS infrastructure, meaning connection limits are tied to the instance size rather than being arbitrarily capped by the Supabase control plane.
• High-availability configurations are essentially handled by standard RDS-style replication, though users should verify specific failover latency expectations for mission-critical write-heavy applications.

The hardware allocations here are optimized for teams that prefer not to manage underlying Linux kernel tuning or Postgres configuration files manually. Because the storage baseline remains low regardless of the compute tier, this platform is best suited for applications with high query density but relatively compact data sets. If your architecture relies on massive read-only blobs or historical data retention, the $0.13/GB storage cost will quickly inflate your monthly invoice compared to self-hosting on raw NVMe instances. Developers should ensure their indexing strategy is tight to avoid unnecessary storage growth, as the platform does not offer the same storage flexibility found in raw infrastructure providers like Linode or Vultr.