billing

56 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

MAU definition and counting

Monthly Active Users (MAUs) are distinct users who log in or refresh their token during a billing cycle, including users who authenticate via Social Login (Google, Facebook, GitHub). Each unique user is counted only once per billing cycle, regardless of how many times they authenticate.

MAU billing example exceeding quota

When an organization's MAU usage exceeds the quota, charges apply for all usage over the quota at the per-MAU rate. Example: 160,000 MAU on a Pro plan with 100,000 MAU quota (60,000 over quota) results in $195 in overage charges at $0.00325 per MAU.

MAU billing example within quota

When an organization's MAU usage is within quota, no charges apply for the additional MAUs. Example: 23,000 MAU on a Pro plan with 100,000 MAU quota results in $0 cost for Monthly Active Users.

MAU pricing by plan

Monthly Active Users pricing: Free plan has a quota of 50,000 MAU with no over-usage charges; Pro plan has a quota of 100,000 MAU with $0.00325 per MAU for over-usage; Team plan has a quota of 100,000 MAU with $0.00325 per MAU for over-usage; Enterprise plan has custom quotas and custom pricing.

MAU count reset

The MAU count resets at the start of each billing cycle.

MAU usage invoice line item

Usage is shown as 'Monthly Active Users' on the invoice.

Third-Party MAU usage calculation example within quota

When Third-Party MAU usage is within quota, no additional charges apply. Example: Pro plan at $25/month with 37,000 Third-Party MAUs within the 100,000 quota results in $0 charge for Third-Party MAU usage.

Third-Party MAU billing definition

You are charged for the number of distinct users who log in or refresh their token during the billing cycle using a third-party authentication provider (Clerk, Firebase Auth, Auth0, AWS Cognito). Each unique user is counted only once per billing cycle, regardless of how many times they authenticate. These users are referred to as 'Third-Party MAUs'.

Third-Party MAU quota and over-usage pricing by plan

Free plan: 50,000 quota, no over-usage charges. Pro plan: 100,000 quota, $0.00325 per Third-Party MAU over-usage. Team plan: 100,000 quota, $0.00325 per Third-Party MAU over-usage. Enterprise plan: Custom quota and custom over-usage pricing. The count resets at the start of each billing cycle.

Third-Party MAU usage calculation example exceeding quota

When Third-Party MAU usage exceeds quota, charges apply to the overage. Example: 130,000 Third-Party MAUs on a Pro plan with 100,000 quota results in 30,000 units over quota, charged at $0.00325 per unit for a total of $97.50.

PITR billing is hourly with full-hour minimum

PITR is charged by the hour. If PITR is active for any part of an hour, the full hour is billed.

PITR invoice line item description

PITR usage appears on the invoice as 'Point-in-time recovery Hours'.

PITR add-on billed in arrears

Project add-ons including PITR are billed in arrears based on the actual hours used. When you remove the PITR add-on, billing stops immediately from the time of removal.

Charged for every enabled PITR add-on

You are charged for every enabled PITR add-on across all your projects.

PITR add-on not covered by Spend Cap

Point-In-Time Recovery add-on charges are not covered by the Spend Cap feature. Users will be billed for PITR usage even if a Spend Cap is configured.

PITR billing calculation example

Example: If PITR is activated on January 10 at 4:30 PM and remains active until January 31 23:59 PM, the billing cycle from January 1 to January 31 results in 512 hours billed. The activation at 4:30 PM counts as 1 full hour (4:30 PM to 5:00 PM), then 511 additional hours until the end of the billing cycle.

Read Replica inherits Disk Throughput

Read Replicas inherit any additional provisioned Disk Throughput from the primary database.

Compute Credits do not apply to Read Replica Compute

Compute Credits do not apply to Read Replica Compute charges.

Read Replica charged resources

Each Read Replica is a dedicated database that is charged for its resources, which are mirrored from the primary database: Compute, Disk Size, Provisioned Disk IOPS, Provisioned Disk Throughput, and IPv4.

Read Replicas not covered by Spend Cap

Read Replicas are not covered by the Spend Cap cost control feature.

Read Replica Compute charging by hour

Compute is charged by the hour for each Read Replica. You are charged for the exact number of hours a Read Replica is running. 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.

Read Replica disk size calculation

The disk size of a Read Replica is 1.25x the size of the primary disk to account for WAL archives. With a Read Replica, you go beyond your subscription plan's quota for Disk Size.

Read Replica IPv4 billing

If the primary database has configured an IPv4 address add-on, its Read Replicas are also assigned one, with charges for each.

Read Replica line items on invoice

Compute incurred by Read Replicas is shown as 'Replica Compute Hours' on your invoice. Disk Size, Disk IOPS, Disk Throughput and IPv4 are not shown separately for Read Replicas and are rolled up into the project.

Realtime messages package pricing model

Realtime Messages are billed using Package pricing, with each package representing 1 million messages. If usage falls between two packages, you are billed for the next whole package.

Realtime messages billing example: pricing tiers

Billing tier examples: 999,999 messages = 1 package billed; 1,000,000 messages = 1 package billed; 1,000,001 messages = 2 packages billed; 1,500,000 messages = 2 packages billed.

View Realtime messages usage location

You can view Realtime Messages usage on the organization's usage page at /dashboard/org/_/usage. The page shows usage of all projects by default, but you can select a specific project from a dropdown and also select a different time period.

Realtime messages Pro Plan quota example

In the within-quota billing example, the Pro Plan includes a Realtime Messages quota. An organization with 1.8 million messages within quota incurs no charges for the Realtime Messages line item.

Realtime messages exceeding quota example

In the exceeding-quota billing example, an organization with 8.5 million messages that exceeds the quota by 3.5 million incurs a charge of $10 for the additional Realtime Messages usage.

Realtime messages billing: what counts as a message

You are charged for the number of messages going through Supabase Realtime throughout the billing cycle. This includes database changes, Broadcast, and Presence.

Realtime Peak Connections pricing structure

Realtime Peak Connections are billed using package pricing, with each package representing 1,000 peak connections. If usage falls between two packages, billing occurs for the next whole package.

Realtime Peak Connections invoice line item label

Usage is shown as 'Realtime Peak Connections' on your invoice.

View Realtime Peak Connections usage

Realtime Peak Connections usage can be viewed on 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.

Realtime Peak Connections with Pro Plan exceeding quota

Example invoice for Pro Plan organization with connections exceeding quota by 1,200: Pro Plan (1 unit), Compute Hours Small (730 hours), Realtime Peak Connections (1,700 connections at $20 charge), subtotal $60, minus Compute Credits $10, total $50.

Realtime Peak Connections billing metric definition

Realtime Peak Connections are measured by tracking the highest number of concurrent connections for each project during the billing cycle. Regardless of fluctuations, only the peak count per project is used for billing, and the totals from all projects are summed. Only successful connections are counted; connection attempts are not included.

Realtime Peak Connections package billing examples

Peak Connections 999 is billed as 1 package. Peak Connections 1,000 is billed as 1 package. Peak Connections 1,001 is billed as 2 packages. Peak Connections 1,500 is billed as 2 packages.

Storage Image Transformations billing: package pricing model

Storage Image Transformations are billed using package pricing, where each package represents 1000 origin images. If usage falls between two packages, you are billed for the next whole package. For example, 999 origin images are billed as 1 package, 1,000 are billed as 1 package, and 1,001 are billed as 2 packages.

Storage Image Transformations billing: counted by distinct origin images

You are charged for the number of distinct images transformed during the billing period, regardless of how many transformations each image undergoes. These distinct images are referred to as 'origin' images. For example, if you apply four different transformations to two images, you are charged based on 2 origin images, not 4 transformations.

Storage billing averages across billing period

Storage size for quota and billing is effectively the average across the billing period, not the live size. For example, storing 20 GB for the first half of the month and 0 GB for the second half averages to 10 GB. Reducing storage late in the cycle lowers the average only gradually, so it may not immediately clear a restriction until the next billing cycle begins.

Project transfer billing during handoff

For usage metrics such as disk size, egress, or image transformations, and for project add-ons such as Compute Add-On, Point-In-Time-Recovery, IPv4, Log Drains, Advanced MFA, or Custom Domain, the source organization is still charged for usage up until the transfer. These charges are added to the invoice when the billing cycle resets. The target organization is charged at the end of the billing cycle for usage after the project transfer.

Why invoices exceed subscription fee amount

Invoices can exceed the base subscription fee for several reasons: running multiple projects (each project incurs compute costs of at least $10 when Compute Credits are exhausted), usage exceeding included quotas when Spend Cap is disabled, or usage not covered by Spend Cap such as IPv4 addresses or custom domains.

Free usage quotas for different services

Egress has a free usage quota of 250 GB. Monthly Active Users has a free usage quota of 100,000 users. Storage includes a 100 GB quota. Custom Domain has no free usage quota and is charged for all hours active.

Compute Credits included in paid plans

Paid plans come with $10 in Compute Credits per month. This amount is sufficient for a single project using a Nano or Micro compute instance. Each additional project adds compute fees to the monthly invoice.

Discounted line items and usage quotas

Paid plans come with usage quotas for certain line items. You only pay for usage exceeding the quota. For example, Storage includes a 100 GB quota. If you use 105 GB, you pay for only 5 GB. If you use 95 GB, you pay nothing. This quota is declared as a discount on your invoice.

Usage-based fees definition and examples

Usage-based fees vary depending on actual usage and are paid in arrears. Examples include fees for monthly active users and storage size. The higher the usage, the higher the fee.

Fixed fees definition and examples

Fixed fees are independent of usage and paid in advance. They remain the same regardless of number of projects or active users. Examples include subscription fees, HIPAA fees, and priority support fees.

Invoice timing and coverage

When a billing cycle resets, an invoice is issued. The invoice contains fixed fees for the current billing cycle and usage-based fees for the previous billing cycle.

Billing cycle start and reset timing

A billing cycle starts when a Supabase organization is created. The billing cycle resets on the anniversary date each month. If the anchored day does not exist in the current month (e.g., the 31st in February), the last day of that month is used instead. For example, an organization created on January 6th will have its billing cycle reset on the 6th of each subsequent month.

Manual payment options for failed invoices

If payment fails, you can manually trigger a charge using the link provided in the Payment Failure email or by clicking the 'Pay now' button on the organization's invoices page in the dashboard.

Automatic invoice payment and retries

Monthly invoices are automatically collected by charging the payment method marked as 'active' for an organization. If payment fails, Supabase retries the charge multiple times and sends a Payment Failure email explaining the reason.

Invoice access locations

Invoices are sent via email and can also be accessed on the organization's invoices page in the Supabase dashboard.

Vercel Marketplace pricing

Pricing for databases created through Vercel Marketplace is identical to those created directly within Supabase. Detailed pricing information is available on the Supabase pricing page. Usage is tracked on the usage page and this information is sent to Vercel for billing, which appears on your Vercel invoice.

Vercel Marketplace billing cycle

The Supabase Organization billing cycle is separate from Vercel's. Plan changes will reset the billing cycle to the day of the change, with the initial billing cycle starting the day the integration is installed.

Realtime messages pricing structure

Realtime messages are priced at $2.50 per 1 million messages for usage exceeding the subscription plan's quota. The Free plan includes 2 million messages. The Pro plan includes 5 million messages with $2.50 per 1 million messages for overage. The Team plan includes 5 million messages with $2.50 per 1 million messages for overage. The Enterprise plan has custom messaging quota and custom pricing for overage.

Realtime connections pricing and quotas

Realtime connections are charged at $10 per 1,000 peak connections for usage exceeding the subscription plan's quota. The Free plan includes a quota of 200 peak connections with no over-usage charges. The Pro plan includes a quota of 500 peak connections with over-usage charged at $10 per 1,000 peak connections. The Team plan includes a quota of 500 peak connections with over-usage charged at $10 per 1,000 peak connections. The Enterprise plan has a custom quota and custom pricing for over-usage.

Storage billing charged by GB-Hours

Storage size is charged by Gigabyte-Hours (GB-Hrs). One GB-Hr represents 1 GB provisioned for 1 hour. For example, 10 GB provisioned for 5 hours results in 50 GB-Hrs (10 GB × 5 hours). Usage appears as 'Disk Size GB-Hrs' on your invoice.

Give your agent this brain