Usage, quotas and add-ons

Your plan comes with three quotas that every project on the instance shares: database size, file storage and monthly egress. This page explains how each one is measured, where to watch it, and what happens when you get close or go over.

The three quotas

Nothing else is metered. Monthly active users, API requests, Realtime connections and messages, and Edge Function invocations are all unlimited in billing terms. In practice they're bounded by the instance's CPU and memory; see the capacity guides on Plans and limits.

Database size

Database size is Postgres's own figure (pg_database_size) for each project's database. You can check one project yourself from Studio's SQL editor:

select pg_size_pretty(pg_database_size(current_database())) as db_size;

And find the biggest tables in it:

select relname as table_name,
       pg_size_pretty(pg_total_relation_size(relid)) as total_size
from pg_catalog.pg_statio_user_tables
order by pg_total_relation_size(relid) desc
limit 10;

Deleting rows doesn't always shrink the number straight away, because Postgres reuses freed space rather than giving it back. See Database size not shrinking after deleting data.

File storage

File storage is the total size of the files in each project's Storage folder on the instance disk. It doesn't include the database, even though Storage keeps file metadata in storage.objects. If the number looks too high, see Unexpectedly high storage usage.

Egress

Egress is the bytes in responses that leave your instance through its HTTPS gateway: the Data API, Auth, Storage downloads, Edge Function responses and Realtime traffic. It's read from the gateway's access logs. Outbound requests your Edge Functions make to other services don't go through the gateway, so they aren't counted. More detail in Egress on SupaHost explained.

Common ways to cut egress: select only the columns you need instead of select('*'), paginate large lists, and set cacheControl on Storage uploads so browsers reuse files.

Where to watch usage

• Usage & billing shows quota tiles for database, file storage and egress against your plan plus any add-ons.
• Plan usage at the bottom of the sidebar opens a quick summary from any page.
• Projects has summary meters at the top and can sort the list by database size, which shows which project is growing.

Usage alerts

SupaHost emails the owner as usage approaches each quota. You pick the threshold (80%, 90% or 100%) in Settings → Email notifications, and an alert is also always sent at 100%. Each alert fires once per level per month, so you won't get the same warning every day.

Usage alerts are on by default with an 80% threshold. You can turn them off, and you can copy up to 5 other addresses on alert emails with "Also send alerts to". See Quota alert emails and going over.

Add-ons

If you regularly need more than your plan's quota, add capacity in blocks. Add them with the steppers on Usage & billing → Add-ons.

Per GB, an add-on costs the same as overage. The difference is predictability: an add-on raises your quota, so the quota tiles and usage alerts work against the bigger number, and your invoice is known in advance.

Database and file storage add-ons also raise how large the instance disk is allowed to grow. There are no extra vCPU or Phone MFA add-ons; for more CPU, move to a bigger plan.

Going over

You aren't cut off when you pass a quota. Usage above plan plus add-ons is billed as overage:

For example, a Pro instance that sends 560 GB of egress in a month pays for 60 GB of overage: 60 × $0.12 = $7.20 on top of the plan.

Disk size versus quota

The database and file storage quotas are billing limits. The physical disk on your VM is a separate thing: it starts at 50 GB (Builder), 100 GB (Pro) or 200 GB (Business), and grows automatically as it fills, with no restart. You don't need to manage disk space yourself. See Monitoring, health checks and alerts.

Related

• Plans and limits
• Storage limits and quotas
• Limits reference