Prevent pausing by upgrading to Pro Plan
To prevent future automatic pausing, upgrade to the Pro Plan from Billing Settings. Paid projects cannot be paused and are not subject to pausing for inactivity.
platform
492 notes in this subject, read out of this brain and free to use. This is page 5 of 9.
Vanity subdomain requirements
To set up a vanity subdomain: install the latest Supabase CLI, log in to your Supabase account, ensure Owner or Admin permissions for the project, and ensure the organization is on a paid plan (Pro/Team/Enterprise).
Custom domain use cases
Custom domains are useful when using OAuth (Social Login) where the project URL is shown on the consent screen, creating APIs for third-party systems via Edge Functions or webhooks, and storing URLs in a database or encoding them in QR codes. Custom domains help keep APIs portable for the long term and enable migration between Supabase projects or API versioning.
Custom domain limitations
Custom domains are not intended to enable hosting of frontend applications through Edge Functions. A single custom domain can only be attached to any given Supabase project; it is not possible to break out a project's resources into multiple custom domains. Custom domains can only be powered by CNAME records.
CNAME record configuration for custom domains
Add a CNAME record to your domain's DNS settings to ensure your custom domain points to the Supabase project. If the project's default domain is abcdefghijklmnopqrst.supabase.co, create a CNAME record for api.example.com that resolves to abcdefghijklmnopqrst.supabase.co. Use a low TTL value to propagate changes.
Custom domain DNS verification with TXT records
To verify domain ownership, use the CLI command `supabase domains create --project-ref abcdefghijklmnopqrst --custom-hostname api.example.com` to get a TXT record for verification. The returned record follows the format `_acme-challenge.api.example.com. TXT -> <verification-string>`. Add this TXT record to your domain's DNS settings. Some DNS registrars automatically append the domain name to entries, so you may need to create the record for just the subdomain part (e.g., `api` instead of `api.example.com`).
Custom domain verification process
After configuring CNAME and TXT records, use the CLI command `supabase domains reverify --project-ref abcdefghijklmnopqrst` to begin domain verification. This command may need to be run multiple times due to DNS propagation delays. Supabase will check DNS records and issue an SSL certificate using multiple Certificate Authorities including Let's Encrypt, Google Trust Services, and SSL.com. This process can take up to 30 minutes.
Custom domain URLs for Edge Functions and Storage
After custom domain activation, Edge Functions are available at `https://api.example.com/functions/v1/your_function_name` and Storage objects at `https://api.example.com/storage/v1/object/public/your_file_path.ext`.
Vanity subdomains availability
Vanity subdomains are experimental and allow hosting services at a custom subdomain on Supabase (e.g., my-example-brand.supabase.co) instead of the default randomly assigned domain. They provide a basic branded experience compared to custom domains.
Custom domains availability and pricing
Custom domains are available as a paid add-on for projects on a paid plan. Both custom domains and vanity subdomains are supported types of domains.
Credit balance top-up as alternative to monthly charges
Instead of monthly credit card charges, you can make an upfront payment by topping up your credit balance. This option helps avoid recurring payment issues, provides more control over payment frequency, and may simplify accounting.
Credit card requirements for paid plans
Paid plans require a credit card on file. The card must not have expired, must have sufficient funds, and must have a sufficient transaction limit.
Billing details cannot be changed after invoice issued
Billing details such as billing email address, billing address, and tax ID cannot be changed once an invoice has been issued. These must be configured correctly from the start.
HIPAA projects require Business Associate Agreement
Organizations must have a signed Business Associate Agreement (BAA) with Supabase to store or process Protected Health Information (PHI). To start developing healthcare apps on Supabase, reach out to the Supabase team via https://forms.supabase.com/hipaa2 to sign the BAA.
HIPAA project required configuration
HIPAA High Compliance projects must be configured with the following security requirements: Point in Time Recovery enabled (which requires at least a small compute add-on), SSL Enforcement turned on, Network Restrictions enabled, and Postgres connection logging kept enabled.
HIPAA High Compliance projects run continuous security checks
Once High Compliance is enabled on a HIPAA project, additional security checks are run against the project to ensure the deployed configuration is compliant. These checks are performed on a continual basis and security warnings will appear in the Security Advisor if a non-compliant setting is detected.
HIPAA add-on enables High Compliance project configuration
When the HIPAA add-on is enabled on an organization, projects within that organization can be configured as High Compliance. This configuration is found in the General Project Settings page of the dashboard.
Supabase billing components
Supabase charges separately for multiple usage items: Compute, Read Replicas, Branching, Egress, Disk Size, Disk Throughput, Disk IOPS, Monthly Active Users, Monthly Active Third-Party Users, Monthly Active SSO Users, Storage Size, Storage Image Transformations, Edge Function Invocations, Realtime Messages, Realtime Peak Connections, Custom Domains, Point-in-Time Recovery, IPv4, MFA Phone, Log Drains, and Pipelines. Each component has its own cost calculation and optimization strategies.
Charges applied when downgrading to Free Plan
When you downgrade from a paid plan to the Free Plan, you receive credits for the unused time on the paid plan. However, you are also charged for any excessive usage in the billing cycle. The plan line item (e.g. Pro Plan) is charged upfront, while usage charges are charged in arrears. Excessive usage is charged whenever a billing cycle resets, either when your monthly cycle resets or when you do a plan change. If you were charged after downgrading to the Free Plan, you had excessive usage in the previous billing cycle.
Multiple payment methods allowed, one active at a time
You can add multiple payment methods to your billing account, but only one can be active at a time.
Update billing details on organization billing page
You can update your billing email address, billing address, and tax ID on the organization's billing page.
Set payment method as active
To set a payment method as active: go to the organization's billing page, navigate to the Payment Methods section, click the context menu of the payment method you want to use, click Use this card, and click Confirm.
Delete payment method from billing account
To delete a payment method: go to the organization's billing page, navigate to the Payment Methods section, click the context menu of the payment method you want to delete, click Delete card, and click Confirm.
No refunds to payment method per Terms of Service
According to the Terms of Service, Supabase does not offer refunds to the payment method on file. Upon subscription downgrade, prepaid subscription fees are credited back to the organization as account credits for unused time, rather than refunded.
Credits issued when downgrading subscription
When you downgrade your subscription, any prepaid subscription fee is credited back to your organization for unused time in the billing cycle. These credits do not expire and will be applied to future invoices. For example, if you start a Pro Plan subscription on January 1 and downgrade to the Free Plan on January 15, your organization receives about 50% of the subscription fee as credits for the unused time between January 15 and January 31.
Downgrade subscription plan process
To downgrade your subscription plan: go to the organization's billing page, navigate to the Subscription Plan section, click Change subscription plan, choose a lower subscription plan from the side panel, and follow the prompts. Downgrades take effect immediately. During the downgrade process, you are informed of the implications.
Upgrade subscription plan process
To upgrade your subscription plan: go to the organization's billing page, navigate to the Subscription Plan section, click Change subscription plan, choose a subscription plan from the side panel, and follow the prompts. Upgrades take effect immediately. During the upgrade process, you are informed of the associated costs. If you have credits in your account, they are used first before charging your card.
Cancel subscription by downgrading to Free Plan
To cancel your subscription, go to your organization's billing settings, click Change subscription plan, and select the Free Plan. The cancellation is immediate. Your Free Plan subscription will run indefinitely unless you delete the organization through your organization's settings. Cancellations are fully self-serve.
Add payment method to billing account
To add a payment method: go to the organization's billing page, navigate to the Payment Methods section, click Add new card, provide your credit card details, and click Add payment method.
Billing details changes reflect in upcoming invoices only
Any changes made to your billing details will only be reflected in your upcoming invoices. The payment provider cannot regenerate previous invoices.
Custom Domain pricing per hour
Custom domains are priced at $0.0137 per hour, which equals $10 per month.
Custom Domain add-on activation
Custom domains are configured for a project by enabling the Custom Domain add-on in project settings. You are charged for all custom domains configured across your projects.
Custom domains not covered by Spend Cap
Custom Domains are not covered by the Spend Cap cost control feature.
Custom Domain billing period rounding
Custom domains are charged by the hour. If a custom domain is active for part of an hour, you are still charged for the full hour. This means charges are rounded up for any partial hour of usage.
Custom Domain billing example with activation mid-cycle
If a custom domain is activated on January 10 at 4:30 PM during a billing cycle running January 1 to January 31, the time from 4:30 PM to 5:00 PM is counted as 1 full hour (rounded up), then all hours from 5:00 PM to January 31 at 11:59 PM are counted, totaling 512 hours for the month.
Custom Domain billing after removal
Custom domain add-ons are billed in arrears based on hours used. If you remove the custom domain add-on, you are no longer billed from the time of removal onward.
Optimize Custom Domain costs
To optimize custom domain usage costs, regularly check your projects and remove custom domains that are no longer needed. Use free vanity subdomains where applicable as an alternative.
Custom Domain Hours invoice line item
Custom domain usage appears on the invoice as a line item called 'Custom Domain Hours'.
Nano Compute on paid plans billed as Micro
In paid organizations, Nano Compute instances are billed at the same price as Micro Compute. New Nano instances cannot be launched on paid plans, only Micro and above. However, Nano instances may remain after upgrading from a Free Plan. It is recommended to upgrade Nano to Micro when convenient, though upgrades are not automatic to avoid downtime.
Compute size pricing table
Compute pricing by size: | Compute Size | Hourly Price USD | Monthly Price USD | |---|---|---| | Nano | $0.00 | $0.00 | | Micro | $0.01344 | ~$10 | | Small | $0.0206 | ~$15 | | Medium | $0.0822 | ~$60 | | Large | $0.1517 | ~$111 | | XL | $0.2877 | ~$210 | | 2XL | $0.562 | ~$410 | | 4XL | $1.32 | ~$960 | | 8XL | $2.562 | ~$1,870 | | 12XL | $3.836 | ~$2,800 | | 16XL | $5.12 | ~$3,730 | | >16XL | - | Contact Sales | Nano Compute resources on the Free Plan are subject to change. In paid organizations, Nano Compute are billed at the same price as Micro Compute.
View Compute usage on organization usage page
Compute usage can be viewed at the organization's usage page (/dashboard/org/_/usage). The page shows usage of all projects by default. To view usage for a specific project, select it from a dropdown. Different time periods can also be selected. The Compute Hours section displays hours used for each Compute size during the selected period, with daily breakdowns available by hovering over specific dates.
Optimize Compute usage strategies
To optimize Compute usage: start on a smaller Compute size and create a report on the Dashboard to monitor CPU and memory utilization before upgrading; load test your application in staging to understand Compute requirements; transfer projects to a Free Plan organization to reduce Compute usage; delete unused projects.
Compute costs are independent of database usage
Each project on the Supabase platform includes a dedicated Postgres instance running on its own server. Compute charges are based on the Compute resources of that server and are independent of database usage.
Compute billing per hour with partial hour rounding
Compute is charged by the hour. If a project runs for part of an hour, the full hour is billed. For example, a project running from 4:00 PM to 4:30 PM is charged for 1 full hour, and a project running from 4:30 PM to 5:00 PM is charged for another full hour.
Each project increases monthly Compute costs
Each project launched increases monthly Compute costs, as each project includes a dedicated Postgres instance running on its own server and is charged for Compute resources independently.
Compute Credits included in paid plans
Paid plans include $10 in Compute Credits per month, which cover one project running on Micro/Nano Compute size or portions of other Compute sizes. Compute Credits reset monthly and do not accumulate or apply to line items other than Compute. They do not cover Read Replica Compute or Branching Compute.
Paused projects do not incur Compute charges
Paused projects do not count towards Compute usage. Compute Hours are not covered by the Spend Cap.
GP3 disk pricing and included size
General purpose disks (gp3) are charged at $0.000171 per GB-Hr ($0.125 per GB per month). The primary database gets 8 GB of included disk provisioned. For Pro and Team plans, you are only charged for provisioned disk size exceeding these 8 GB. Enterprise plans have custom pricing and included disk size.
Free Plan disk size limits
Disk size charges do not apply to the Free Plan. Instead, Free Plan customers are limited by Database size.
IO2 high performance disk pricing
High performance disks (io2) are charged at $0.000267 per GB-Hr ($0.195 per GB per month). Unlike gp3 disks, io2 disks are billed from the first byte of provisioned disk with no included disk size. For Pro and Team plans, there is 0 GB included disk size. Enterprise plans have custom pricing.
Disk size distribution categories
Disk usage can be distributed across three categories: Database, WAL, and System. The disk size distribution shows how your provisioned disk is used across these categories.
gp3 disk throughput pricing by plan
For general purpose (gp3) disks: Pro plan includes 125 MB/s with 0.095 USD per MB/s per month over-usage charge; Team plan includes 125 MB/s with 0.095 USD per MB/s per month over-usage charge; Enterprise plan has custom included throughput and custom pricing.
Default disk throughput baseline and charges
General purpose (gp3) disks come with a baseline throughput of 125 MB/s. Charges only apply for provisioned throughput exceeding 125 MB/s. The pricing is 0.095 USD per MB/s per month or 0.00013 USD per MB/s-Hr for throughput above the baseline.
Disk throughput not covered by Spend Cap
Disk Throughput is not covered by the Spend Cap cost control feature, meaning it can incur charges even when spend cap protection is active.
Disk throughput charging model
Disk throughput is charged by MB/s-Hrs, where 1 MB/s-Hr represents disk throughput of 1 MB/s provisioned for 1 hour. For example, provisioning 10 MB/s for 5 hours results in 50 MB/s-Hrs (10 MB/s × 5 hours). Usage is shown as 'Disk Throughput MB/s-Hrs' on invoices.
No charges for default disk throughput without opt-in
Each database has a dedicated disk with provisioned disk throughput. However, unless you explicitly opt in for additional throughput beyond the baseline, no charges apply.
High performance disk (io2) throughput pricing
High performance (io2) disks have no throughput charges. Throughput scales with IOPS at no additional cost.
IPv4 Hours billing line item
Usage is shown as 'IPv4 Hours' on your invoice.
IPv4 add-on charges and coverage
IPv4 addresses are assigned to databases via the IPv4 add-on in the dashboard. You are charged for all IPv4 addresses configured across your databases. IPv4 Hours are not covered by the Spend Cap.
IPv4 billing by the hour with rounding up
IPv4 addresses are charged by the hour for the exact number of hours an IPv4 address is assigned to a database. If an address is assigned for part of an hour, you are still charged for the full hour.