Change payment method by adding new before removing old
To change your payment method, you must add the new payment method before being allowed to remove the old one. This can be done from the organization's billing page.
platform
492 notes in this subject, read out of this brain and free to use. This is page 4 of 9.
Tax on prepaid credit top-ups assessed at purchase time
If you purchase a prepaid top up or credit package, tax is assessed at the time of purchase, not when the credits are later consumed against usage or subscription invoices. This ensures the correct tax rate is applied based on your billing address at the time of purchase.
Prepaid multiple months via credit balance top-up
You can top up your credit balance to cover multiple months through your organization's billing page.
Tax shown separately on invoices from subscription costs
Tax is shown separately at the bottom of your invoice, clearly broken out from the cost of the products and services you are subscribed to.
Supported credit card brands
Supported credit card brands are: Visa, Mastercard, American Express, Japan Credit Bureau (JCB), China UnionPay (CUP), and Cartes Bancaires.
Marketplace purchases handled by marketplace provider for tax
If you use Supabase through a cloud marketplace such as AWS Marketplace or Vercel Marketplace, the marketplace provider handles tax collection and remittance. Supabase does not separately charge tax on marketplace-billed invoices.
Free plan allows two active free projects per organization
You are entitled to two active free projects. Paused projects do not count towards your quota. Within an organization, free project limits are counted from all members that are either Owner or Admin. If another organization member with Admin or Owner role has exhausted their free project quota, you cannot launch another free project in that organization.
Cannot mix free and paid projects in single organization
The subscription plan is set on the organization level and it is not possible to mix paid and non-paid projects inside a single organization. However, you can have a paid and a free organization and use self-serve project transfers to organize your projects. All projects in an organization benefit from the subscription plan.
Grace period does not reset after usage drops below limits
When your organization exceeds plan limits, you receive a grace period. After this grace period ends, the dashboard continues to show a warning notice even if you drop back under plan limits. This warning serves as an indicator that your organization previously exceeded limits. If you exceed limits again, you will not receive another grace period and your project will be restricted. The notice clears automatically if you stay under limits for multiple billing cycles.
Projects can be transferred between organizations
You can transfer your projects to another organization using self-serve project transfer.
Credit balance checked on organization's billing page
You can check your credit balance on the organization's billing page. Credits are used on future invoices before charging your payment method. If you have enough credits to cover an invoice, there is no charge.
Tax-exempt organizations submit exemption certificate to tax-documents@supabase.io
If your organization is tax-exempt, submit your exemption certificate to tax-documents@supabase.io so Supabase can verify and apply the exemption to your organization.
Payments taken at beginning of billing cycle; usage charges in arrears
Payments are taken at the beginning of each billing cycle and you are charged once a month. The subscription plan fee is charged upfront, whereas usage-charges, including compute, are charged in arrears based on your usage. You can see the current billing cycle and upcoming invoice in your organization's billing settings.
Paused projects incur no charges
No charges are incurred for paused projects. Compute hours are only counted for active instances.
Credits can be transferred between organizations via support
You can transfer credits to another organization by submitting a support ticket.
Payment methods accepted: credit card only
Supabase accepts credit card payments only. Alternatives for larger upfront payments may be available; create a support ticket to inquire.
VAT/GST registered organizations should provide Tax ID
If your organization is VAT- or GST-registered, ensure you have entered a valid Tax ID in your organization's billing page. This allows Supabase to apply the correct tax treatment, such as reverse charge for eligible B2B transactions.
Tax ID added in organization's billing page under address section
You can add or update your Tax ID directly in the Supabase Dashboard under your organization's billing page in the address section. Providing a valid Tax ID ensures the correct tax treatment is applied for your region. In many jurisdictions, this enables the reverse charge mechanism.
Annual subscription not officially supported; use credit top-up instead
Supabase does not officially support annual plans. However, you can do a credit top-up to avoid monthly payments.
Remove Fair Use restrictions by addressing underlying cause
To remove Fair Use Policy restrictions, address the issue that caused the restriction. This could be reducing your usage, paying overdue invoices, updating your payment method, or other issues. Restrictions due to usage limits are lifted once your quota refills at the start of the next billing cycle. You may immediately lift restrictions by upgrading to Pro Plan (if on Free Plan) or by disabling spend cap (if on Pro Plan with spend cap enabled).
Pausing or deleting projects does not remove usage already occurred
Pausing or deleting a project stops new usage from accumulating, but does not remove usage that already occurred during the current billing cycle. For quota-based limits, that usage still counts until the billing period resets.
Incorrect bill review process via support ticket
If your bill looks wrong, review the 'Your monthly invoice' page which may clarify any questions. If it still looks wrong, submit a support ticket through the dashboard. Select the affected organization and provide the invoice number.
Organizations contain multiple projects; each organization has one subscription plan
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. Each organization only has a single subscription with a single plan (Free, Pro, Team or Enterprise).
Exceeding Free Plan quota triggers notifications and service restrictions
When you exceed the Free Plan quota, you will be notified. If you continue to exceed the limits, service restrictions will apply. To avoid service restrictions, you can manage your usage or upgrade to a paid plan.
Invoices found on organization's invoices page
All invoices from your organization can be found on your organization's invoices page in the dashboard.
Pro Plan with spend cap enabled restricts usage exceeding quota
When you exceed your Pro Plan quota and have the spend cap on, you will be notified. To unblock yourself, toggle off your spend cap in organization billing settings to pay for over-usage. If you continue to exceed limits without managing usage or turning off the spend cap, restrictions will apply.
Spend cap disabled to scale beyond Pro Plan limits
The Pro Plan has a Spend Cap enabled by default. To scale beyond the plan's included quota, switch off the Spend Cap to pay for additional usage beyond the plans included limits. This is toggled in the organization's billing settings.
Fair Use Policy service restrictions include pausing, read-only mode, and 402 status code
The Fair Use Policy is applied through service restrictions which could mean: pausing projects, switching databases to read-only mode, disabling new project launches/transfers, or responding with a 402 status code for all API requests. The Fair Use Policy is generally applied to all projects of the restricted organization.
No refunds provided for unused credits
Supabase does not provide refunds for unused credits. This is per the Terms of Service.
Tax collection by jurisdiction; rolling out May 1 - June 30, 2026
Supabase is rolling out sales tax in applicable US states, and VAT, GST, and other indirect taxes for customers where required by law. Tax is only applied in jurisdictions where Supabase is registered to collect it. The rollout begins on May 1, 2026 and completes by June 30, 2026. You will receive an email notification in advance of any changes.
Egress is bandwidth quota shared across all services
Egress refers to the total bandwidth (network traffic) quota available to each organization. This quota can be used for Storage, Realtime, Auth, Functions, Supavisor, Log Drains and Database. Each plan includes a specific egress quota, and additional usage beyond that quota is billed accordingly. Cached egress (served via CDN from cache hits) and uncached egress are differentiated, with cached egress being cheaper. Cached egress only applies to Storage.
Subscription plan changes made in organization billing settings
Change your subscription plan in your organization's billing settings. To upgrade to an Enterprise Plan, complete the Enterprise request form.
Credit top-ups apply only to future invoices, not outstanding invoices
Credit top-ups apply only to future invoices. They cannot be used to pay or adjust outstanding invoices.
Cancellation provides credits for unused time
When you cancel your subscription, the organization is given credits for unused time on the subscription plan. The credits do not expire and can be used again in the future. You may see an additional charge for unbilled excessive usage charges from your previous billing cycle.
Compute billing is hourly based on instance type and duration
Each Supabase project is a dedicated VM and Postgres database running on Micro compute instance by default. Compute size can be upgraded in Project settings. When changing compute size, there are no immediate upfront charges. Billing is based on compute hours during the billing cycle reset. If you upgrade for 10 hours then downgrade, you only pay for the larger instance for those 10 hours at the end of your billing cycle.
Overdue payment results in project pause and downgrade to Free Plan
When an invoice becomes overdue, your projects are paused and your organization is downgraded to the Free Plan. You can restore your projects once you have paid all outstanding invoices.
Reasons for overdue payment status
You can be overdue when: a card is expired, the bank declined the payment, you had insufficient funds, or there was no card on record. Payments are always in USD and may show as coming from Singapore (where the payment entity is located). Ensure your payment methods are current and correct in your organization's billing page.
Project add-ons are configured per project and billed to organization
Project add-ons such as Compute, IPv4, Log Drains, Advanced MFA, Custom Domains, and PITR are configured per project and are added to your organization subscription.
Tax amount depends on billing address and jurisdiction
The tax amount applied to your invoice depends on your billing address and the tax regulations in your jurisdiction.
Usage breakdown available on organization's usage page
The breakdown of your usage can be found on your organization's usage page in the dashboard.
Pro Plan includes compute credits and billing for multiple projects
Each paid organization comes with compute credits to cover one project on the default compute size. Additional projects start at approximately the same monthly cost (billed hourly). For example, running 3 projects on a Pro Plan with default Micro instance would be approximately: Pro Plan base fee, compute credits that offset the first project, plus additional compute charges for the remaining 2 projects.
Payments cannot be delayed
Payments cannot be delayed.
Mistaken upgrade can be transferred as credits to another organization
If you mistakenly upgraded the wrong organization and then downgraded it, the amount can be transferred as credits to another organization of your choice. You can use these credits to upgrade the organization or pay the next month's invoice. This requires creating a support ticket.
Fair Use Policy applies when exceeding quotas or having overdue invoices
The Fair Use Policy may apply service restrictions to your organization if: you continually exceed the Free Plan quota, you continually exceed Pro Plan quota and have the spend cap enabled, you have overdue invoices, or you have an expired credit card. You will receive a notification before restrictions are applied, though in cases of suspected abuse, restrictions may apply without prior notice.
Update billing details on organization's billing page
You can update your billing details on the organization's billing page. Any changes made will only be reflected in your upcoming invoices, as the payment provider cannot regenerate previous invoices.
Compute upgrades incur downtime
Compute instance changes are usually applied with less than 2 minutes of downtime, but can take longer depending on the underlying Cloud Provider. Before upgrading, assess whether bottlenecks are hardware-constrained or software-constrained by considering optimizations like connection pooling or query performance improvements.
Dedicated vs shared CPU burst behavior
Compute instances from Nano to 2XL have CPUs which can burst to higher performance levels for short periods of time. Instances larger than Large (4XL and above) have predictable performance levels and do not exhibit the same burst behavior, with specific configurable IOPS and throughput limits.
Compute instance sizes and pricing
Supabase offers the following compute instance sizes with corresponding hourly and monthly prices: Nano (free tier, shared CPU, 0.5 GB memory, 500 MB max DB size), Micro ($0.01344/hr, ~$10/mo, 2-core shared CPU, 1 GB memory, 10 GB max DB), Small ($0.0206/hr, ~$15/mo, 2-core shared CPU, 2 GB memory, 50 GB max DB), Medium ($0.0822/hr, ~$60/mo, 2-core shared CPU, 4 GB memory, 100 GB max DB), Large ($0.1517/hr, ~$110/mo, 2-core dedicated CPU, 8 GB memory, 200 GB max DB), XL ($0.2877/hr, ~$210/mo, 4-core dedicated CPU, 16 GB memory, 500 GB max DB), 2XL ($0.562/hr, ~$410/mo, 8-core dedicated CPU, 32 GB memory, 1 TB max DB), 4XL ($1.32/hr, ~$960/mo, 16-core dedicated CPU, 64 GB memory, 2 TB max DB), 8XL ($2.562/hr, ~$1,870/mo, 32-core dedicated CPU, 128 GB memory, 4 TB max DB), 12XL ($3.836/hr, ~$2,800/mo, 48-core dedicated CPU, 192 GB memory, 6 TB max DB), 16XL ($5.12/hr, ~$3,730/mo, 64-core dedicated CPU, 256 GB memory, 10 TB max DB). Sizes larger than 16XL require contacting sales for custom pricing and specs.
Disk performance factors
Disk performance depends on compute size, provisioned disk throughput, provisioned disk IOPS (Input/Output Operations per Second), disk type (io2 or gp3), and disk size. The effective IOPS is limited by the lower of compute size support or provisioned disk IOPS. Similarly, effective throughput is limited by the lower of compute size support or provisioned disk throughput.
gp3 disk type specifications and pricing
General Purpose SSD (gp3) is the default disk type, suitable for general workloads, development environments, and small to medium databases. Max disk size is 16 TB. Max IOPS is 16,000 IOPS at 32 GB disk size. Throughput ranges from 125 MB/s (default) to 1,000 MB/s (maximum). Pricing: 8 GB included, then $0.125 per GB; 3,000 IOPS included, then $0.024 per IOPS; 125 MB/s included, then $0.95 per MB/s. You can provision additional 500 IOPS for every GB of disk size and additional 0.25 MB/s throughput per provisioned IOPS.
Disk IO consumption monitoring for upgrades
If the 'Disk IO % consumed' metric in the Dashboard is more than 1%, it indicates the workload has exceeded baseline IO throughput during the day. If this metric reaches 100%, the workload has used up all available disk IO budget. Projects showing any disk IO budget usage are candidates for upgrading to a larger compute instance with higher throughput.
io2 disk type specifications and pricing
High Performance SSD (io2) is designed for high-performance needs, large-scale databases, and mission-critical applications requiring low latency and very high IOPS. Max disk size is 60 TB. Max IOPS is 80,000 IOPS at 80 GB disk size. Throughput automatically scales with IOPS at no additional cost. Pricing: $0.195 per GB for disk, $0.119 per IOPS. Can be provisioned with 1,000 IOPS per GB of disk size.
IOPS and throughput provisioning requirements
Additional IOPS and throughput can be provisioned from the Infrastructure settings page, but this requires Large compute size or above. Be aware that increasing IOPS or throughput incurs additional charges.
Disk modification constraints
You can modify disk attributes up to 4 times within a rolling 24-hour window. A new modification can be initiated as soon as the previous one completes. You can increase disk size but cannot decrease it. If you reach the 4-modification limit, throttling occurs and you must wait for the rolling 24-hour window to permit further adjustments.
Free plan project pausing after 7 days low activity
Supabase pauses Free Plan projects that show low activity over a 7-day period to save server resources. A Free plan project is considered inactive if it does not receive sufficient user database activity over the past week. Typically a few user requests to the database each day over the previous week is enough to keep the project from being paused.
Paid plan projects cannot be paused
Projects under a paid plan cannot be paused and are not subject to automatic pausing for inactivity. To pause a project currently under a paid plan, first transfer the project to an organization on the Free plan.
Pausing notifications sent to project owner
Supabase sends two emails to the project owner regarding project pausing: a warning email roughly one week before the pause takes effect, and a confirmation email once the project has been paused.
Prevent pausing by generating activity
After receiving an initial email warning, the pause can be prevented by visiting the project from the Supabase Dashboard to generate activity, or by generating a sufficient amount of activity by making API calls to the project or sending requests via the connected application.
Restore paused project up to 1 year after pausing
A paused project can be restored for up to 1 year after it was paused. To restore: open the Supabase Dashboard, select the organization followed by the paused project, then click Resume project and confirm. The project will return to its previous state, including data and configurations.
1-year restore window reason and backup retention
The 1-year time limit to restore a paused project exists because backups are only retained for a limited period, and platform changes may not be backward compatible with older backups. Unlike active projects, static backups cannot be updated to accommodate such changes.