Files
supabase/apps/docs/content/guides/platform/manage-your-usage/compute.mdx

167 lines
9.2 KiB
Plaintext

---
id: 'manage-usage-compute'
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.
<Admonition type="note">
Paused projects do not count towards Compute usage. Compute Hours are **not** covered by the [Spend Cap](/docs/guides/platform/cost-control#spend-cap).
</Admonition>
## 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 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 512 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 | 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 <Price price="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] | <Price price="0" /> | <Price price="0" /> |
| Micro | <Price price="0.01344" /> | ~<Price price="10" /> |
| Small | <Price price="0.0206" /> | ~<Price price="15" /> |
| Medium | <Price price="0.0822" /> | ~<Price price="60" /> |
| Large | <Price price="0.1517" /> | ~<Price price="111" /> |
| XL | <Price price="0.2877" /> | ~<Price price="210" /> |
| 2XL | <Price price="0.562" /> | ~<Price price="410" /> |
| 4XL | <Price price="1.32" /> | ~<Price price="960" /> |
| 8XL | <Price price="2.562" /> | ~<Price price="1,870" /> |
| 12XL | <Price price="3.836" /> | ~<Price price="2,800"/> |
| 16XL | <Price price="5.12" /> | ~<Price price="3,730"/> |
| >16XL | - | [Contact Us](/dashboard/support/new?category=sales&subject=Enquiry%20about%20larger%20instance%20sizes) |
[^1]: Compute resources on the Free Plan are subject to change.
<Admonition type="note" title="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](/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 | - | <Price price="25"/> |
| Compute Hours Small Project 1 | 730 | <Price price="15" /> |
| **Subtotal** | | **<Price price="40" />** |
| Compute Credits | | -<Price price="10" /> |
| **Total** | | **<Price price="30" />** |
### Multiple projects
All projects run on the same Compute size throughout the entire billing cycle.
| Line Item | Hours | Costs |
| ----------------------------- | ----- | ------------------------ |
| Pro Plan | - | <Price price="25" /> |
| Compute Hours Small Project 1 | 730 | <Price price="15" /> |
| Compute Hours Small Project 2 | 730 | <Price price="15" /> |
| Compute Hours Small Project 3 | 730 | <Price price="15" /> |
| **Subtotal** | | **<Price price="70" />** |
| Compute Credits | | -<Price price="10" /> |
| **Total** | | **<Price price="60" />** |
### One project on different Compute sizes
The project's Compute size changes throughout the billing cycle.
| Line Item | Hours | Costs |
| ----------------------------- | ----- | --------------------------- |
| Pro Plan | - | <Price price="25" /> |
| Compute Hours Micro Project 1 | 230 | <Price price="3.09" /> |
| Compute Hours Small Project 1 | 500 | <Price price="10.30" /> |
| **Subtotal** | | **<Price price="38.39" />** |
| Compute Credits | | -<Price price="10" /> |
| **Total** | | **<Price price="28.39" />** |
### Projects not running for full month
One project is running for the entire month, two other projects were launched and deleted within a few days.
We only bill for the hours while the project was running and billing stops once a project is deleted.
Compute is always billed in arrears when your billing cycle resets.
| Line Item | Hours | Costs |
| ----------------------------- | ----- | --------------------------- |
| Pro Plan | - | <Price price="25" /> |
| Compute Hours Small Project 1 | 730 | <Price price="15" /> |
| Compute Hours Micro Project 2 | 20 | <Price price="0.27" /> |
| Compute Hours Micro Project 3 | 70 | <Price price="0.94" /> |
| **Subtotal** | | **<Price price="41.21" />** |
| Compute Credits | | -<Price price="10" /> |
| **Total** | | **<Price price="31.21" />** |
## View usage
You can view Compute usage on the [organization's usage page](/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={{
light: '/docs/img/guides/platform/usage-navbar--light.png',
dark: '/docs/img/guides/platform/usage-navbar--dark.png',
}}
width={1546}
height={208}
/>
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={{
light: '/docs/img/guides/platform/usage-compute--light.png',
dark: '/docs/img/guides/platform/usage-compute--dark.png',
}}
width={2050}
height={810}
/>
## Optimize usage
- Start out on a smaller Compute size, [create a report](/dashboard/project/_/observability) 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.