mirror of
https://github.com/supabase/supabase.git
synced 2026-10-16 06:39:09 +03:00
small edits
This commit is contained in:
Kevin Grüneberg committed
1 parent
65f47e7576
commit
f3b0bb92a2
7 files changed
+57
-31
No files matched your search
@@ -10,9 +10,9 @@ Every project on the Supabase Platform comes with its own dedicated Postgres ins
|
||||
|
||||
The following table describes the base instances, Nano (free plan) and Micro (paid plans), with additional compute instance sizes available if you need extra performance when scaling up.
|
||||
|
||||
<Admonition type="note" label="Nano instances in Pro organizations">
|
||||
<Admonition type="note" label="Nano instances in paid plan organizations">
|
||||
|
||||
In Pro organizations, Nano Compute are billed at the same price as Micro Compute. It is recommended to upgrade your Project from Nano Compute to Micro Compute when it's convenient for you. Compute sizes are not auto-upgraded because of the downtime incurred. See [Supabase Pricing](https://supabase.com/pricing) for more information.
|
||||
In paid organizations, Nano Compute are billed at the same price as Micro Compute. It is recommended to upgrade your Project from Nano Compute to Micro Compute when it's convenient for you. Compute sizes are not auto-upgraded because of the downtime incurred. See [Supabase Pricing](https://supabase.com/pricing) for more information. You cannot launch Nano instances on paid plans, only Micro and above - but you might have Nano instances after upgrading from Free Plan.
|
||||
|
||||
</Admonition>
|
||||
|
||||
|
||||
@@ -4,6 +4,7 @@ title: 'Credits'
|
||||
---
|
||||
|
||||
## Credit balance
|
||||
|
||||
Each organization has a credit balance. Credits are applied to future invoices to reduce the amount due. As long as the credit balance is greater than $0, credits will be used before charging your payment method on file.
|
||||
|
||||
<Image
|
||||
@@ -18,21 +19,25 @@ Each organization has a credit balance. Credits are applied to future invoices t
|
||||
You can find the credit balance on the [organization's billing page](https://supabase.com/dashboard/org/_/billing).
|
||||
|
||||
### What causes the credit balance to change?
|
||||
|
||||
**Subscription plan downgrades:** Upon subscription downgrade, any prepaid subscription fee will be credited back to your organization for unused time in the billing cycle.\
|
||||
As an example, if you start a Pro Plan subscription on January 1 and downgrade to the Free Plan on January 15, your organization will receive about 50% of the subscription fee as credits for the unused time between January 15 and January 31.
|
||||
|
||||
**Credit top-ups:** You self-erved a credit top-up or have signed an upfront credits deal with our growth team.
|
||||
|
||||
## Credit top-ups
|
||||
|
||||
You can top up credits at any time, with a maximum of $999 per top-up. These credits do not expire and are non-refundable.
|
||||
|
||||
You may want to consider this option to avoid issues with recurring payments, gain more control over how often your credit card is charged, and potentially make things easier for your accounting department.
|
||||
|
||||
<Admonition type="info">
|
||||
If you are interested in larger (> $1,000) credit packages, please [reach out](https://supabase.com/dashboard/support/new?subject=I%20would%20like%20to%20inquire%20about%20larger%20credit%20packages&category=Billing).
|
||||
If you are interested in larger (> $1,000) credit packages, please [reach
|
||||
out](https://supabase.com/dashboard/support/new?subject=I%20would%20like%20to%20inquire%20about%20larger%20credit%20packages&category=Billing).
|
||||
</Admonition>
|
||||
|
||||
### How to top up credits
|
||||
|
||||
1. On the [organization's billing page](https://supabase.com/dashboard/org/_/billing), go to section **Credit Balance**
|
||||
2. Click **Top Up**
|
||||
3. Choose the amount
|
||||
@@ -50,11 +55,11 @@ You may want to consider this option to avoid issues with recurring payments, ga
|
||||
/>
|
||||
|
||||
## Credit FAQ
|
||||
|
||||
### Can I transfer credits to another organization?
|
||||
|
||||
Yes, you can transfer credits to another organization. Please submit a [support ticket](https://supabase.help).
|
||||
|
||||
### Can I get a refund of my unused credits?
|
||||
|
||||
No, we do not provide refunds. Please refer to our [Terms of Service](https://supabase.com/terms#1-fees).
|
||||
|
||||
|
||||
|
||||
@@ -4,34 +4,40 @@ title: 'Manage Compute usage'
|
||||
---
|
||||
|
||||
## What you are charged for
|
||||
|
||||
Each project on the Supabase platform includes a dedicated Postgres instance running on its own server. You are charged for the [Compute](/docs/guides/platform/compute-and-disk#compute) resources of that server, independent of your database usage.
|
||||
|
||||
## How charges are calculated
|
||||
Compute is charged by the hour, meaning you are charged for the exact number of hours that a project is running and, therefore, incurring Compute resources. If a project runs for part of an hour, you are still charged for the full hour.
|
||||
|
||||
Compute is charged by the hour, meaning you are charged for the exact number of hours that a project is running and, therefore, incurring Compute usage. If a project runs for part of an hour, you are still charged for the full hour.
|
||||
|
||||
<Admonition type="caution">
|
||||
Each project you launch increases your monthly Compute costs.
|
||||
</Admonition>
|
||||
|
||||
### Example
|
||||
|
||||
Your billing cycle runs from January 1 to January 31. On January 10 at 4:30 PM, you switch your project from the Micro Compute size to the Small Compute size. At the end of the billing cycle you are billed for 233 hours of Micro Compute size and 511 hours of Small Compute size.
|
||||
|
||||
| Time Window | Compute Size | Hours Billed | Description |
|
||||
|---------------------------------------------|--------------|--------------|------------------------------------------------|
|
||||
| January 1, 00:00 AM - January 10, 4:00 PM | Micro | 232 | |
|
||||
| January 10, 04:00 PM - January 10, 4:30 PM | Micro | 1 | full hour is billed |
|
||||
| January 10, 04:30 PM - January 10, 5:00 PM | Small | 0 | time window is allocated to Micro Compute size |
|
||||
| January 10, 05:00 PM - January 31, 23:59 PM | Small | 511 | |
|
||||
| Time Window | Compute Size | Hours Billed | Description |
|
||||
| ------------------------------------------- | ------------ | ------------ | ------------------- |
|
||||
| January 1, 00:00 AM - January 10, 4:00 PM | Micro | 232 | |
|
||||
| January 10, 04:00 PM - January 10, 4:30 PM | Micro | 1 | full hour is billed |
|
||||
| January 10, 04:30 PM - January 10, 5:00 PM | Small | 1 | full hour is billed |
|
||||
| January 10, 05:00 PM - January 31, 23:59 PM | Small | 511 | |
|
||||
|
||||
### Usage on your invoice
|
||||
|
||||
Usage is shown as "Compute Hours" on your invoice.
|
||||
|
||||
## Compute Credits
|
||||
|
||||
Paid plans include $10 in Compute Credits, which cover one project running on the Micro/Nano Compute size or portions of other Compute sizes. Compute Credits are applied to your Compute costs and are provided to an organization each month. They reset monthly and do not accumulate.
|
||||
|
||||
## Pricing
|
||||
|
||||
| Compute Size | Hourly Price USD | Monthly Price USD |
|
||||
|--------------|------------------|-------------------|
|
||||
| ------------ | ---------------- | ----------------- |
|
||||
| Nano[^1] | $0 | $0 |
|
||||
| Micro | $0.01344 | ~$10 |
|
||||
| Small | $0.0206 | ~$15 |
|
||||
@@ -46,16 +52,23 @@ Paid plans include $10 in Compute Credits, which cover one project running on th
|
||||
|
||||
[^1]: Compute resources on the Free Plan are subject to change.
|
||||
|
||||
<Admonition type="note" label="Nano Compute size in Pro organizations">
|
||||
In Pro organizations, Nano Compute is billed at the same price as Micro Compute. It is recommended to upgrade your project from Nano Compute to Micro Compute when it's convenient for you. Compute sizes are not auto-upgraded because of the downtime incurred.
|
||||
<Admonition type="note" label="Nano Compute size in paid plan organizations">
|
||||
In paid organizations, Nano Compute are billed at the same price as Micro Compute. It is
|
||||
recommended to upgrade your Project from Nano Compute to Micro Compute when it's convenient for
|
||||
you. Compute sizes are not auto-upgraded because of the downtime incurred. See [Supabase
|
||||
Pricing](https://supabase.com/pricing) for more information. You cannot launch Nano instances on
|
||||
paid plans, only Micro and above - but you might have Nano instances after upgrading from Free
|
||||
Plan.
|
||||
</Admonition>
|
||||
|
||||
## Billing examples
|
||||
|
||||
### One project
|
||||
|
||||
The project runs on the same Compute size throughout the entire billing cycle.
|
||||
|
||||
| Line Item | Hours | Costs |
|
||||
|-------------------------------|-------|---------|
|
||||
| ----------------------------- | ----- | ------- |
|
||||
| Pro Plan | - | $25 |
|
||||
| Compute Hours Micro Project 1 | 744 | $10 |
|
||||
| **Subtotal** | | **$35** |
|
||||
@@ -63,10 +76,11 @@ The project runs on the same Compute size throughout the entire billing cycle.
|
||||
| **Total** | | **$25** |
|
||||
|
||||
### Multiple projects
|
||||
|
||||
All projects run on the same Compute size throughout the entire billing cycle.
|
||||
|
||||
| Line Item | Hours | Costs |
|
||||
|-------------------------------|-------|---------|
|
||||
| ----------------------------- | ----- | ------- |
|
||||
| Pro Plan | - | $25 |
|
||||
| Compute Hours Micro Project 1 | 744 | $10 |
|
||||
| Compute Hours Micro Project 2 | 744 | $10 |
|
||||
@@ -76,10 +90,11 @@ All projects run on the same Compute size throughout the entire billing cycle.
|
||||
| **Total** | | **$45** |
|
||||
|
||||
### One project on different Compute sizes
|
||||
|
||||
The project's Compute size changes throughout the billing cycle.
|
||||
|
||||
| Line Item | Hours | Costs |
|
||||
|-------------------------------|-------|---------|
|
||||
| ----------------------------- | ----- | ------- |
|
||||
| Pro Plan | - | $25 |
|
||||
| Compute Hours Micro Project 1 | 233 | $3 |
|
||||
| Compute Hours Small Project 1 | 511 | $11 |
|
||||
@@ -88,7 +103,9 @@ The project's Compute size changes throughout the billing cycle.
|
||||
| **Total** | | **$29** |
|
||||
|
||||
## View usage
|
||||
|
||||
You can view Compute usage on the [organization's usage page](https://supabase.com/dashboard/org/_/usage). The page shows the usage of all projects by default. To view the usage for a specific project, select it from the dropdown. You can also select a different time period.
|
||||
|
||||
<Image
|
||||
alt="Usage page navigation bar"
|
||||
src={{
|
||||
@@ -99,6 +116,7 @@ You can view Compute usage on the [organization's usage page](https://supabase.c
|
||||
/>
|
||||
|
||||
In the Compute Hours section, you can see how many hours of a specific Compute size your projects have used during the selected time period. Hover over a specific date for a daily breakdown.
|
||||
|
||||
<Image
|
||||
alt="Usage page Compute Hours section"
|
||||
src={{
|
||||
@@ -109,11 +127,14 @@ In the Compute Hours section, you can see how many hours of a specific Compute s
|
||||
/>
|
||||
|
||||
## Optimize usage
|
||||
- start out on a smaller Compute size, [create a report](https://supabase.com/dashboard/project/_/reports) on the Dashboard to monitor your CPU and memory utilization, and upgrade the Compute size as needed
|
||||
- load test your application in staging to understand your Compute requirements
|
||||
- [transfer projects](/docs/guides/platform/project-transfer) to a Free Plan organization to reduce Compute usage
|
||||
- delete unused projects
|
||||
|
||||
- Start out on a smaller Compute size, [create a report](https://supabase.com/dashboard/project/_/reports) on the Dashboard to monitor your CPU and memory utilization, and upgrade the Compute size as needed
|
||||
- Load test your application in staging to understand your Compute requirements
|
||||
- [Transfer projects](/docs/guides/platform/project-transfer) to a Free Plan organization to reduce Compute usage
|
||||
- Delete unused projects
|
||||
|
||||
## FAQ
|
||||
|
||||
### Do Compute Credits apply to line items other than Compute?
|
||||
No, Compute Credits apply only to Compute and do not cover other line items, including Read Replica Compute and Branching Compute.
|
||||
|
||||
No, Compute Credits apply only to Compute and do not cover other line items, including Read Replica Compute and Branching Compute.
|
||||
@@ -4,7 +4,7 @@ title: 'Manage Egress usage'
|
||||
---
|
||||
|
||||
## What you are charged for
|
||||
You are charged for the network data transmitted out of the system to a connected client. Egress is incurred by all services - Database, Auth, Storage, Edge Functions, and Realtime.
|
||||
You are charged for the network data transmitted out of the system to a connected client. Egress is incurred by all services - Database, Auth, Storage, Edge Functions, Realtime and Log Drains.
|
||||
|
||||
### Database Egress
|
||||
Data sent to the client when retrieving data stored in your database.
|
||||
@@ -41,7 +41,7 @@ Data pushed to to the connected log drain.
|
||||
**Example:** You set up a log drain, each log sent to the log drain is considered egress. You can toggle the GZIP option to reduce egress, in case your provider supports it.
|
||||
|
||||
## How charges are calculated
|
||||
Egress is charged by byte. Charges apply only for usage exceeding your subscription plan's quota. This quota is called the Unified Egress Quota because it can be used across all services (Database, Auth, Storage etc.).
|
||||
Egress is charged by gigabyte. Charges apply only for usage exceeding your subscription plan's quota. This quota is called the Unified Egress Quota because it can be used across all services (Database, Auth, Storage etc.).
|
||||
|
||||
### Usage on your invoice
|
||||
Usage is shown as "Egress GB" on your invoice.
|
||||
|
||||
@@ -10,7 +10,7 @@ Each [Read Replica](/docs/guides/platform/read-replicas) is a dedicated database
|
||||
Read Replica charges are the total of the charges listed below.
|
||||
|
||||
**Compute**
|
||||
Compute is charged by the hour, meaning you are charged for the exact number of hours that a Read Replica is running and, therefore, incurring Compute resources. If a Read Replica runs for part of an hour, you are still charged for the full hour.
|
||||
Compute is charged by the hour, meaning you are charged for the exact number of hours that a Read Replica is running and, therefore, incurring Compute usage. If a Read Replica runs for part of an hour, you are still charged for the full hour.
|
||||
|
||||
Read Replicas run on the same Compute size as the primary database.
|
||||
|
||||
|
||||
@@ -50,7 +50,7 @@ As the plan is set for your entire organization, upgrading your organization to
|
||||
|
||||
You can launch as many organizations as you want. For example, you can create two organizations on the Pro Plan for $25 each and launch a single project in each. This provides the same quotas and pricing that you'd receive today. Importantly, each subsequent database inside that Organization will cost $0.01344/hour (roughly $10 per month), rather than $25.
|
||||
|
||||
Read more about quotas and Organization-based Billing including examples in our [docs](https://supabase.com/docs/guides/platform/org-based-billing).
|
||||
Read more about quotas and Organization-based Billing including examples in our [docs](https://supabase.com/docs/guides/platform/billing-on-supabase).
|
||||
|
||||
## Free Plan
|
||||
|
||||
@@ -92,7 +92,7 @@ If you launch a second or third instance on your paid plan, it just adds additio
|
||||
compute usage.
|
||||
</div>
|
||||
|
||||
To read more about usage-based billing for compute, head over to the [docs](https://supabase.com/docs/guides/platform/org-based-billing#billing-for-compute-compute-hours).
|
||||
To read more about usage-based billing for compute, head over to the [docs](https://supabase.com/docs/guides/platform/manage-your-usage/compute).
|
||||
|
||||
## Unified Egress
|
||||
|
||||
@@ -194,7 +194,7 @@ The spend cap still exists, it's just set on the organization-level and not per
|
||||
<details className="cursor-default mb-2">
|
||||
<summary className="cursor-pointer"><span className="pl-2">Am I going to pay a different amount?</span></summary>
|
||||
|
||||
Most customers will pay less because we are offering more egress for free and it's cheaper to have multiple projects on the Pro Plan in a single organization. We're very conscious about the current users and use-cases. Check our docs for more [detailed breakdown and some examples](/docs/guides/platform/org-based-billing).
|
||||
Most customers will pay less because we are offering more egress for free and it's cheaper to have multiple projects on the Pro Plan in a single organization. We're very conscious about the current users and use-cases. Check our docs for more [detailed breakdown and some examples](/docs/guides/platform/billing-on-supabase).
|
||||
|
||||
</details>
|
||||
|
||||
|
||||
@@ -86,7 +86,7 @@ With the new integration, everything is unified in your Vercel bill. All Supabas
|
||||
|
||||
All services created through the Vercel integration are _exactly the same price_ that you'd get on the Supabase platform - including the **2 free databases** that we offer to all developers.
|
||||
|
||||
Supabase has [predictable pricing](/pricing) with [spend caps](/docs/guides/platform/spend-cap) for developers who are worried about becoming [too successful](https://i.kym-cdn.com/photos/images/newsfeed/001/444/303/2b6.jpg) with their upcoming launch.
|
||||
Supabase has [predictable pricing](/pricing) with [spend caps](/docs/guides/platform/cost-control) for developers who are worried about becoming [too successful](https://i.kym-cdn.com/photos/images/newsfeed/001/444/303/2b6.jpg) with their upcoming launch.
|
||||
|
||||
<Admonition>
|
||||
|
||||
|
||||
Reference in new issue
Block a user