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

Prettier for docs

Browse Source
This commit is contained in:
Joshen Lim committed 2023-08-31 14:25:01 +08:00
1 parent bb1e14452d
commit 8a485b3b07
1 file changed
+19 -12
Download Patch File Download Diff File Expand all files Collapse all files
apps/docs/pages/guides/platform/org-based-billing.mdx
+19 -12
View File
@@ -43,12 +43,12 @@ Each organization receives a total egress quota (eg. 250GB on the Pro plan) whic
Each plan includes a quota for unified egress, which is applied to your entire organization.
| Plan | Total Egress Quota | Over-Usage |
| ---------- | ------------------ | ------------- |
| Free | 5 GB | - |
| Pro | 250 GB | $0.09 per GB |
| Team | 250 GB | $0.09 per GB |
| Enterprise | Custom | Custom |
| Plan | Total Egress Quota | Over-Usage |
| ---------- | ------------------ | ------------ |
| Free | 5 GB | - |
| Pro | 250 GB | $0.09 per GB |
| Team | 250 GB | $0.09 per GB |
| Enterprise | Custom | Custom |
### Egress Dashboards
@@ -179,7 +179,7 @@ If you are currently running 2 free projects, **this does require some work from
### Multiple pro plan projects
If you're currently running multiple Pro plan projects, each one costs you $25 for the Pro plan + usage + addons.
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**
@@ -190,7 +190,7 @@ If you're currently running multiple Pro plan projects, each one costs you $25 f
| 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.
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**
@@ -245,7 +245,9 @@ If you're currently running a mix of Free and Pro plan projects and migrate that
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).
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
@@ -282,14 +284,18 @@ We are not changing your 2 free project limit. You can have two organizations on
<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.
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.
Yes, with the new [Project Transfers](/docs/guides/platform/project-transfer) you can move any project
to a different organization.
</details>
<details>
@@ -306,7 +312,8 @@ If you head over to your [organizations' billing settings](https://supabase.com/
<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.
Not at all. There are no service disruptions during the migration, as we’re not touching your projects’
infrastructure.
</details>
<details>