How billing works

Learn how organization-based billing works in Supabase.

Our goal at Supabase is to provide a predictable billing system that grows with your project.

How billing is organized#

The Supabase Platform has "organizations" and "projects". An organization may contain multiple projects. Each project is a dedicated Supabase instance with all of its sub-services including Storage, Auth, Functions and Realtime. For example:

• Organization 1
  • Project 1 (Database, Auth, Storage, Functions, Realtime)
  • Project 2 (Database, Auth, Storage, Functions, Realtime)
• Organization 2
  • Project 3 (Database, Auth, Storage, Functions, Realtime)

Legacy billing system#

Organization-based Billing was introduced on September 4th 2023. We are migrating all projects to this new structure. Read the announcement for more context.

Legacy Billing (Project-based)#

If your organization was created before September 4th 2023, each project had an individual subscription, a plan and addons.

Current Billing (Organization-based)#

With Organization-based Billing, each organization only has a single subscription with a single plan (Free, Pro, Team or Enterprise). Project addons such as Compute, Custom Domains and PITR are still configured per project and are added to your organization subscription.

Unified Egress#

Each organization receives a total egress quota (eg. 250GB on the Pro plan) which can be used for anything - Storage, Realtime, Auth, Functions or Database.

Included Egress Quota#

Each plan includes a quota for unified egress, which is applied to your entire organization.

Egress Dashboards#

You can see a breakdown of the different types of egress on your organization usage page.

Legacy Egress#

Under the old system, you had different quotas for each service. i.e. on the Pro plan, you had 50GB of database egress and 200GB of storage egress included. If you weren't using storage, you'd miss out on the included egress. The new system provides you more egress in every scenario.

Quotas and Features#

Quotas and features are applied to your entire organization, independent of how many projects you launch within that organization. For billing purposes, we sum the usage across all projects in a monthly invoice.

Upgrading your organization to a paid plan means that you unlock the benefits of the paid plan for all projects within that organizatio - for example, no projects in your "Pro" organization will be paused. See pricing page for details on all plans.

Usage Items#

Legacy quotas#

Under the legacy billing system, each project had an individual plan and the included quotas and features were on a project level. Besides the unified egress, the quotas have not changed. We are also not changing any fees for over-usage. You can launch as many organizations as you want, so you can still create two organizations on the Pro plan for $25 each and launch a single project in each one. Importantly, each subsequent database inside that Organization will cost $0.01344/hour (roughly $10 per month), rather than $25.

Usage-based billing for compute#

We provide a dedicated server for every Supabase project. By default, your instance runs on the Starter Compute instance. You can upgrade your compute size in your project settings.

With Organization-based Billing you won't get an immediate charge upfront when changing compute, instead we'll bill you based on compute runtime hours when your billing cycle resets.

If you launch a second or third instance on your paid plan, we add the additional compute hours to the final invoice.

Compute pricing#

With Legacy Billing, when you upgraded the Compute Add-On, you were immediately charged the prorated amount (days remaining in your current billing cycle) and when your billing cycle reset you were charged upfront for the entire month. When you downgraded, you got the appropriate credits for unused time.

Free plan#

Supabase provides two "Free organizations". Each organization can run a Starter instance for free. This is a great way to get started with Supabase and try out the platform.

Compute Credits#

Paid plans come with $10 of Compute Credits to cover one Starter instance or parts of any other Compute Add-On.

Compute Credits are deducted from your Compute Usage. You can launch as many instances as you want on paid plans and we'll bill based on the compute hours. If you upgrade an instance for 24 hours, you'll only be billed for those 24 hours of additional compute. Compute hours are billed when you do plan up/downgrades (resets the billing cycle) or whenever your billing cycle resets once a month.

Compute Credits do not apply to other usage fees like egress, database size, ... They solely apply to Compute usage.

Additionally, Compute Credits reset every month and do not accumulate, in case you're not running any projects.

With Legacy Billing, you used to pay $25 for every single Pro plan project in an organization. Previously, we gave you a free “Starter” instance on paid plans - we're now giving you $10 in Compute Credits instead, to cover the first instance. You end up not paying extra for the first project inside your paid plan organisation - just like before. In case you add a Compute Add-On to your first project, you also end up paying exactly the same as before.

Legacy vs Organization-based Billing#

If you are using Legacy Billing and have a single project in your organization, there is no change in pricing or quota. Here are some examples on how the new Organization-based Billing migration affects you.

Single free plan project#

If you’re just running a single free project, migrating to Organization-based Billing comes with no disadvantage and one big benefit: you now get a lot more egress.

Not only are we giving you an extra 1GB of egress for free, now it is unified across your org. This means that if you aren’t using Supabase Storage, you get even more Database Egress.

Multiple free plan projects#

We're not changing the number of free projects you can have. Here are the quotas for the free plan:

If you are currently running 2 free projects, this does require some work from you. Because we are now working on an Org-level, instead of Projects, you will need to:

1. Create a new “Free org”
2. Transfer one of your free projects into the newly-created org

Multiple pro plan projects#

If you're currently running multiple Pro plan projects, each one costs you $25 for the Pro plan + usage + addons.

Invoice Breakdown with Legacy Billing

As you're only paying for the plan once, you end up paying less for multiple projects on the Pro plan.

Invoice Breakdown with Organization-based Billing

However, you're no longer getting the quota thrice, but only once. Here's the quota for your entire organization:

If you wish to keep the same quota for each project like legacy billing, you can separate your projects into three organizations on the Pro plan each. You'd end up paying the same ($75) and getting the same quota as before.

See Project Transfers to move projects across organizations.

Mix of free and pro plan projects#

If you're currently running a mix of Free and Pro plan projects and migrate that to a Pro plan organization, your base fee might be higher, but you'll also get the benefits of the paid plan for all projects including no auto-pausing, daily backups, storage image transformations, 7-day log retention and e-mail support.

Invoice Breakdown with Legacy Billing

Invoice Breakdown with Organization-based Billing

All benefits of the Pro plan apply to all projects within your organization.

Self-Serve-Migration#

While we will roll out the new billing for all users during the next few weeks, you can pro-actively migrate, too. If you're not using Organization-based Billing yet, you may initiate the migration to Organization-based Billing yourself. We'll also actively reach out to you, in case you have multiple projects in a single organization.

Head over to your organization billing settings to initiate the migration.

FAQ#