Loading…
Supabase Beta Pricing
Summary
Supabase outlines its beta pricing structure across different service tiers covering database infrastructure, authentication, file storage, and platform operations. Every tier includes a dedicated Postgres database, unlimited API requests, unlimited total users, and access to basic multi-factor authentication and social OAuth providers. Lower tiers offer fixed resources starting at 500 megabytes of database storage and 50,000 monthly active users, with project pausing occurring after one week of inactivity. Higher tiers introduce automated backups, point-in-time recovery, branching billed by the hour, increased egress limits, and compliance options like SOC2, ISO 27001, and HIPAA add-ons. Additional charges apply to resources exceeding tier allocations, including pipeline data processing, log drains, custom domains, and extra concurrent Postgres changes connections.
Takeaways
- Point-in-time recovery costs $100 per month per 7 days of retention, while database branching is priced at $0.01344 per branch per hour on supported tiers.
- Authentication includes unlimited total users and basic multi-factor authentication across all plans, with monthly active user thresholds scaling from 50,000 to custom limits.
- Enterprise compliance features such as SOC2 and ISO 27001, along with HIPAA paid add-ons and AWS PrivateLink, are reserved for upper-tier plans.
Related reading
Supabase ·
Introducing Supabase Enterprise
Supabase announced the launch of its Enterprise Plan alongside new features integrated across existing tiers. The Pro Plan now merges pay-as-you-go billing with a default twenty-five dollar monthly spend cap, and users gain access to self-serve database add-ons for on-demand scaling. A new Log Explorer powered by the Logflare acquisition allows querying logs directly with SQL, providing ninety days of retention on the Enterprise tier. Dedicated enterprise capabilities include Point-in-Time Recovery powered by the open-source tool WAL-G, custom Prometheus scraping endpoints for observability, and guaranteed support service level agreements. Additionally, Supabase achieved SOC2 Type 1 compliance and introduced Elixir Livebooks to monitor PgBouncer connection pools.
Rory Wilding, Paul CopplestoneSupabase ·
Supabase is now on Postgres 13.3
New Supabase projects now run on Supabase Postgres 13.3, transitioning the database platform forward from PostgreSQL 12.0. This release introduces features such as native UUID generation with gen_random_uuid, parallel index vacuuming, incremental sorting, smaller btree indexes, and extended statistics improvements. The underlying PostgreSQL binary was built from the ground up to enable Large System Extensions on AWS Graviton2 ARM instances, optimizing locking and synchronization performance. Alongside upgrading the underlying operating system to Ubuntu 20.04 for long-term support through 2025, the team integrated fail2ban to protect direct database connections on ports 5432 and 6543 against brute-force attacks. Finally, Supabase Postgres version numbering now mirrors upstream PostgreSQL major and minor versions to make tracking installed releases easier.