dima/supabase
1
0 Fork 0
mirror of https://github.com/supabase/supabase.git synced 2026-10-05 09:25:06 +03:00
Code Issues Packages Projects Releases Wiki Activity

docs: remove legacy billing info (#20185)

Browse Source
This commit is contained in:
Kevin Grüneberg authored and GitHub committed 2024-01-05 11:53:11 +01:00
1 parent 511ad5b675
commit d97f83bb84
3 files changed
+86 -248
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

apps/docs/pages/guides/platform/org-based-billing.mdx
+80 -242
View File
@@ -3,8 +3,8 @@ import Layout from '~/layouts/DefaultGuideLayout'
export const meta = {
id: 'organization-based-billing',
title: 'How billing works',
description: 'Learn how organization-based billing works in Supabase.',
subtitle: 'Learn how organization-based billing works in Supabase.',
description: 'Learn how billing works in Supabase.',
subtitle: 'Learn how billing works in Supabase.',
}
Our goal at Supabase is to provide a _predictable_ billing system that grows with your project.
@@ -25,21 +25,72 @@ The Supabase Platform has "organizations" and "projects". An organization may co
- `Organization 2`
- `Project 3` (Database, Auth, Storage, Functions, Realtime)
## Legacy billing system
Each organization only has a single subscription with a single plan (Free, Pro, Team or Enterprise). Project addons such as [Compute](/docs/guides/platform/compute-add-ons), [Custom Domains](/docs/guides/platform/custom-domains) and [PITR](/docs/guides/platform/backups#point-in-time-recovery) are still configured per project and are added to your organization subscription.
Organization-based Billing was introduced on September 4th 2023. We are migrating all projects to this new structure. Read the [announcement](https://supabase.com/blog/organization-based-billing) for more context.
![Billing: Current](/docs/img/guides/platform/org-billing-after.png)
### Legacy billing (project-based)
## Quotas and features
If your organization was created before September 4th 2023, each project had an individual subscription, a plan and addons.
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.
![Billing Before](/docs/img/guides/platform/org-billing-before.png)
Upgrading your organization to a paid plan means that you unlock the benefits of the paid plan for **all** projects within that organization - for example, no projects in your "Pro" organization will be paused. See [pricing page](https://supabase.com/pricing) for details on all plans.
### Current billing (organization-based)
### Usage items
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](/docs/guides/platform/compute-add-ons), [Custom Domains](/docs/guides/platform/custom-domains) and [PITR](/docs/guides/platform/backups#point-in-time-recovery) are still configured per project and are added to your organization subscription.
| Metric | Free | Pro/Team | Enterprise |
| -------------------------- | ------------------------ | ------------------------------------------- | ---------- |
| Egress | 5GB | 250GB included, then $0.09 per GB | Custom |
| Database Size | 500MB | 8GB included, then $0.125 per GB | Custom |
| Storage Size | 1GB | 100GB included, then $0.021 per GB | Custom |
| Monthly Active Users | 50,000 MAU | 100,000 MAU included, then $0.00325 per MAU | Custom |
| Function Invocations | 500K | 2 million included, then $2 per million | Custom |
| Function Count | 10 | 100 included, then $10 per 100 | Custom |
| Storage Images Transformed | Unavailable on Free plan | 100 included, then $5 per 1000 | Custom |
| Realtime Message Count | 2 million | 5 million included, then $2.5 per million | Custom |
| Realtime Peak Connections | 200 | 500 included, then $10 per 1000 | Custom |
![Billing: After](/docs/img/guides/platform/org-billing-after.png)
## 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](https://supabase.com/dashboard/project/_/settings/addons).
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.
<Admonition type="note" label="Paused projects">
We only count compute hours for instances that are active. Paused projects do not count towards compute usage. We’re working on self-serve pausing and unpausing on paid plans to further manage costs.
</Admonition>
### Compute pricing
| Instance Size | Hourly Price | Estimated Monthly Price |
| ------------- | ------------ | ----------------------- |
| Starter | $0.01344 | ~$10 |
| Small | $0.0206 | ~$15 |
| Medium | $0.0822 | ~$60 |
| Large | $0.1517 | ~$110 |
| XL | $0.2877 | ~$210 |
| 2XL | $0.562 | ~$410 |
| 4XL | $1.32 | ~$960 |
| 8XL | $2.562 | ~$1870 |
| 12XL | $3.836 | ~$2800 |
| 16XL | $5.12 | ~$3730 |
### 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](/docs/guides/platform/compute-add-ons).
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.
## Unified egress
@@ -70,133 +121,33 @@ You can see a breakdown of the different types of egress on your [organization u
/>
</div>
### Legacy egress
## Billing Examples
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 organization - for example, no projects in your "Pro" organization will be paused. See [pricing page](https://supabase.com/pricing) for details on all plans.
### Usage items
| Metric | Free | Pro/Team | Enterprise |
| -------------------------- | ------------------------ | ------------------------------------------- | ---------- |
| Egress | 5GB | 250GB included, then $0.09 per GB | Custom |
| Database Size | 500MB | 8GB included, then $0.125 per GB | Custom |
| Storage Size | 1GB | 100GB included, then $0.021 per GB | Custom |
| Monthly Active Users | 50,000 MAU | 100,000 MAU included, then $0.00325 per MAU | Custom |
| Function Invocations | 500K | 2 million included, then $2 per million | Custom |
| Function Count | 10 | 100 included, then $10 per 100 | Custom |
| Storage Images Transformed | Unavailable on Free plan | 100 included, then $5 per 1000 | Custom |
| Realtime Message Count | 2 million | 5 million included, then $2.5 per million | Custom |
| Realtime Peak Connections | 200 | 500 included, then $10 per 1000 | Custom |
### 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](https://supabase.com/dashboard/project/_/settings/addons).
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.
<Admonition type="note" label="Paused projects">
We only count compute hours for instances that are active. Paused projects do not count towards compute usage. We’re working on self-serve pausing and unpausing on paid plans to further manage costs.
</Admonition>
### Compute pricing
| Instance Size | Hourly Price | Estimated Monthly Price |
| ------------- | ------------ | ----------------------- |
| Starter | $0.01344 | ~$10 |
| Small | $0.0206 | ~$15 |
| Medium | $0.0822 | ~$60 |
| Large | $0.1517 | ~$110 |
| XL | $0.2877 | ~$210 |
| 2XL | $0.562 | ~$410 |
| 4XL | $1.32 | ~$960 |
| 8XL | $2.562 | ~$1870 |
| 12XL | $3.836 | ~$2800 |
| 16XL | $5.12 | ~$3730 |
With Legacy Billing, when you upgraded the [Compute Add-On](/docs/guides/platform/compute-add-ons), 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](/docs/guides/platform/compute-add-ons).
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 organization - 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.
| Usage Item | Old plan (per project) | New plan (org based) |
| ---------- | ---------------------------------- | --------------------------------------- |
| Egress | 4GB - (2GB Database + 2GB Storage) | 5GB across Database + Storage |
| | Max of 2 free projects | Max of 2 free orgs - 1 database per org |
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.
Here are some examples on how the Billing affects you.
### Multiple free plan projects
We're not changing the number of free projects you can have. Here are the quotas for the free plan:
Here are the quotas for the free plan:
| Usage Item | Old plan (per project) | New plan (org based) |
| ------------------------- | ---------------------------------- | --------------------------------------- |
| Egress | 4GB - (2GB Database + 2GB Storage) | 5GB across Database + Storage |
| Database Space | 500MB | 500MB |
| Storage Space | 1GB | 1GB |
| Monthly Active Users | 50,000 MAU | 50,000 MAU |
| Edge Function Invocations | 500K | 500K |
| Edge Function Count | 10 | 10 |
| Realtime Message Count | 2 million | 2 million |
| Realtime Peak Connections | 200 | 200 |
| | Max of 2 free projects | Max of 2 free orgs - 1 database per org |
| Usage Item | Free plan |
| ------------------------- | --------------------------------------- |
| Egress | 5GB across Database + Storage |
| Database Space | 500MB |
| Storage Space | 1GB |
| Monthly Active Users | 50,000 MAU |
| Edge Function Invocations | 500K |
| Edge Function Count | 10 |
| Realtime Message Count | 2 million |
| Realtime Peak Connections | 200 |
| | Max of 2 free orgs - 1 database per org |
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
While we allow you to launch a total of two free projects, the quota applies to the entire organization, i.e. you can have a total of 4GB of database space.
### Multiple pro plan projects
If you're currently running multiple Pro plan projects, each one costs you $25 for the Pro plan + usage + addons.
While you only pay for the $25 Pro plan once, launching additional projects at least incurs compute costs.
**Invoice Breakdown with Legacy Billing**
| Line Item | Price |
| ---------------------- | ----- |
| Pro Plan for Project 1 | $25 |
| Pro Plan for Project 2 | $25 |
| Pro Plan for Project 3 | $25 |
| Total | $75 |
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**
**Invoice Breakdown**
| Line Item | Price |
| ------------------------- | ----- |
@@ -205,7 +156,7 @@ As you're only paying for the plan once, you end up paying less for multiple pro
| Compute Credits | $-10 |
| Total | $45 |
However, you're no longer getting the quota thrice, but only once. Here's the quota for your entire organization:
Here's the quota for your entire organization:
| Usage Item | Quota |
| -------------------------- | ----------------------------------------- |
@@ -219,123 +170,10 @@ However, you're no longer getting the quota thrice, but only once. Here's the qu
| Realtime Message Count | 5 million included, then $2.5 per million |
| Realtime Peak Connections | 500 included, then $10 per 1000 |
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.
If you wish to keep the same quota for each project, you can separate your projects into three organizations on the Pro plan each. You'd end up paying $25 for each project, so $75 instead of $45 in total, while getting more quota.
See [Project Transfers](/docs/guides/platform/project-transfer) 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**
| Line Item | Price |
| ----------------------- | ----- |
| Pro Plan for Project 1 | $25 |
| Pro Plan for Project 2 | $25 |
| Free Plan for Project 3 | $0 |
| Free Plan for Project 4 | $0 |
| Total | $50 |
**Invoice Breakdown with Organization-based Billing**
| Line Item | Price |
| ------------------------- | ----- |
| Pro Plan for Organization | $25 |
| Starter Compute x4 | $40 |
| Compute Credits | $-10 |
| Total | $55 |
All [benefits](https://supabase.com/pricing) of the Pro plan apply to all projects within your organization.
<Admonition type="note">
You can transfer projects to a free organization, in case you haven't used up your 2 free project limit, if you don't want additional projects on the Pro plan. See [Project Transfers](/docs/guides/platform/project-transfer).
</Admonition>
### 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](https://supabase.com/dashboard/org/_/billing) to initiate the migration.
<div>
<Image
alt="Self-Serve migration"
className="w-full object-contain"
src={{
light: '/docs/img/database/partitions-light.png',
dark: '/docs/img/database/partitions-dark.png',
}}
/>
</div>
### FAQ
<details>
<summary>
<i>What happens to the 2 free plan projects?</i>
</summary>
We are not changing your 2 free project limit. You can have two organizations on a free plan with one project each.
</details>
<details>
<summary>
<i>What happens to the spend cap?</i>
</summary>
The [spend cap](/docs/guides/platform/spend-cap) still exists, it's just set on the organization-level
and not per project. Head over to your [organization billing settings](https://supabase.com/dashboard/org/_/billing)
to toggle your spend cap. We're working on more fine-grained control over costs to supersede the spend
cap.
</details>
<details>
<summary>
<i>If I'm exceeding quota, can I move out a single project to a different organization?</i>
</summary>
Yes, with the new [Project Transfers](/docs/guides/platform/project-transfer) you can move any project
to a different organization.
</details>
<details>
<summary>
<i>How do I know if I'm using the new Organization-based Billing?</i>
</summary>
If you head over to your [organizations' billing settings](https://supabase.com/dashboard/org/_/billing) and it displays your organization plan at the top, it means you already use the new Organization-based Billing. If it shows you the section to migrate the project to the new billing, you're using the old project-level billing.
![Organization-based Billing: View plan](/docs/img/guides/platform/org-billing-plan.png)
</details>
<details>
<summary>
<i>Does the migration come with any downtime?</i>
</summary>
Not at all. There are no service disruptions during the migration, as we’re not touching your projects’
infrastructure.
</details>
<details>
<summary>
<i>Where do I change my project add-ons such as PITR, Compute and Custom Domain?</i>
</summary>
Head over to your project [Add-ons page](https://supabase.com/dashboard/project/_/settings/addons) to change your compute size, Point-In-Time-Recovery or custom domain.
</details>
<details>
<summary>
<i>I have additional questions/concerns, how do I get help?</i>
</summary>
If you are concerned that your bill has increased as a result of this change or you have any other questions or concerns, please reach out [here](https://supabase.com/dashboard/support/new?category=billing&subject=Organization%20based%20billing).
</details>
export const Page = ({ children }) => <Layout meta={meta} children={children} />
export default Page
apps/docs/pages/guides/platform/spend-cap.mdx
+6 -6
View File
@@ -6,14 +6,14 @@ export const meta = {
subtitle: 'Learn about the cost control of Supabase.',
}
Supabase offers a "Spend Cap" on each project to manage your usage and costs.
Supabase offers a "Spend Cap" on each organization to manage your usage and costs.
This Spend Cap determines whether your project can exceed the free quota allowance of any [line item](#what-additional-usage-can-i-be-charged-for) in a given billing cycle.
This Spend Cap determines whether your organization can exceed the free quota allowance of any [line item](#what-additional-usage-can-i-be-charged-for) in a given billing cycle.
If you exceed the free quota allowance of a line item, and the Spend Cap is **"off"**, then you will be billed for any additional usage on that line item.
## What additional usage can I be charged for?
Supabase charges for certain usage line items in your project. Those line items include:
Supabase charges for certain usage line items in your organization. Those line items include:
- Database Size
- Storage Size
@@ -31,18 +31,18 @@ This will show you how much you have spent so far in the current billing cycle,
## How can I turn the Spend Cap on or off?
To set up a Spend Cap in your project, navigate to the [Subscription section](https://supabase.com/dashboard/org/_/billing) of your organization.
To set up a Spend Cap in your organization, navigate to the [Subscription section](https://supabase.com/dashboard/org/_/billing) of your organization.
From there, you can click on "Change subscription" to select the plan you want to use and, at the same time, turn on or off the Spend Cap.
## What happens when the Spend Cap is on?
Once you use all your free quota allowance for a [line item](#what-additional-usage-can-i-be-charged-for), your project will not allow any further usage on that line item until the next billing cycle begins.
Once you use all your free quota allowance for a [line item](#what-additional-usage-can-i-be-charged-for), your organization will not allow any further usage on that line item until the next billing cycle begins.
This can help you to avoid unexpected costs and manage your expenses more effectively.
## What happens when Spend Cap is off?
Your project will continue to operate after using all the free quota allowance for each [line item](#what-additional-usage-can-i-be-charged-for).
Your projects will continue to operate after using all the free quota allowance for each [line item](#what-additional-usage-can-i-be-charged-for).
This additional usage will be charged based on the line item's cost per unit outlined on the [pricing page](/pricing).
<Admonition type="note">
apps/docs/public/img/guides/platform/org-billing-before.png
BIN
View File
Binary file not shown.
Side by Side

Before

Width:  |  Height:  |  Size: 116 KiB