Usage

Amount of hours your projects were active. Each project is a dedicated server and database.

Paid plans come with $10 in Compute Credits to cover one project running on Micro Compute or parts of any compute add-on.

Billing is based on the sum of Compute Hours used. Paused projects do not count towards usage.

Contains any outgoing traffic including Database, Storage, Realtime, Auth, API, Edge Functions, Pooler and Log Drains.

Billing is based on the total sum of uncached egress in GB throughout your billing period.

Each Supabase project comes with a dedicated disk. Each project gets 8 GB of disk for free. Billing is based on the provisioned disk size. Disk automatically scales up when you get close to it's size.

Each hour your project is using more than 8 GB of GP3 disk, it incurs the overages in GB-Hrs, i.e. a 16 GB disk incurs 8 GB-Hrs every hour. Extra disk size costs $0.125/GB/month ($0.000171/GB-Hr).

Sum of all objects in your storage buckets.

Billing is prorated down to the hour and will be displayed GB-Hrs.

Users who log in or refresh their token count towards MAU.

Billing is based on the sum of distinct users requesting your API throughout the billing period. Resets every billing cycle.

SSO users who log in or refresh their token count towards SSO MAU.

Billing is based on the sum of distinct Single Sign-On users requesting your API throughout the billing period. Resets every billing cycle.

We count all images that were transformed in the billing period, ignoring any transformations.

Usage example: You transform one image with four different size transformations and another image with just a single transformation. It counts as two, as only two images were transformed.

Billing is based on the count of (origin) images that used transformations throughout the billing period. Resets every billing cycle.

Every serverless function invocation independent of response status is counted.

Billing is based on the sum of all invocations throughout your billing period.

Count of messages going through Realtime. Includes database changes, broadcast and presence.

Usage example: If you do a database change and 5 clients listen to that change via Realtime, that's 5 messages. If you broadcast a message and 4 clients listen to that, that's 5 messages (1 message sent, 4 received).

Billing is based on the total amount of messages throughout your billing period.

Total number of successful connections. Connections attempts are not counted towards usage.

Billing is based on the maximum amount of concurrent peak connections throughout your billing period.