Back to Supabase

Manage Read Replica usage

apps/docs/content/guides/platform/manage-your-usage/read-replicas.mdx

1.26.045.7 KB
Original Source

What you are charged for

Each Read Replica is a dedicated database. You are charged for its resources, which are the following, and mirrored from the primary database:

<Admonition type="note">

Read Replicas are not covered by the Spend Cap.

</Admonition>

How we calculate charges

Read Replica charges are the total of the charges listed below.

Compute

Compute is charged by the hour, meaning you are charged for the exact number of hours that a Read Replica is running and, therefore, incurring Compute usage. 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.

Disk size

Read the Manage Disk Size usage guide for details on how we calculate charges. 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.

Provisioned Disk IOPS (optional)

Read Replicas inherit any additional provisioned Disk IOPS from the primary database. Read the Manage Disk IOPS usage guide for details on how we calculate charges.

Provisioned Disk Throughput (optional)

Read Replicas inherit any additional provisioned Disk Throughput from the primary database. Read the Manage Disk Throughput usage guide for details on how we calculate charges.

IPv4 (optional)

If the primary database has configured an IPv4 address add-on, its Read Replicas are also assigned one, with charges for each. Read the Manage IPv4 usage guide for details on how we calculate charges.

Usage on your 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.

Billing examples

No additional resources configured

The project has one Read Replica, no IPv4, and no additional Disk IOPS and Disk Throughput configured.

Line ItemUnitsCosts
Pro Plan1<Price price="25" />
Compute Hours Small Project 1744 hours<Price price="15" />
Disk Size Project 18 GB<Price price="0" />
Compute Hours Small Replica744 hours<Price price="15" />
Disk Size Replica10 GB<Price price="1.25" />
Subtotal<Price price="56.25" />
Compute Credits-<Price price="10" />
Total<Price price="46.25" />

Additional resources configured

The project has two Read Replicas, IPv4, and additional Disk IOPS and Disk Throughput configured.

Line ItemUnitsCosts
Pro Plan1<Price price="25" />
Compute Hours Large Project 1744 hours<Price price="110" />
Disk Size Project 18 GB<Price price="0" />
Disk IOPS Project 13600<Price price="14.40" />
Disk Throughput Project 1200 MB/s<Price price="7.13" />
IPv4 Hours Project 1744 hours<Price price="4" />
Compute Hours Large Replica 1744 hours<Price price="110" />
Disk Size Replica 110 GB<Price price="1.25" />
Disk IOPS Replica 13600<Price price="14.40" />
Disk Throughput Replica 1200 MB/s<Price price="7.13" />
IPv4 Hours Replica 1744 hours<Price price="4" />
Compute Hours Large Replica 2744 hours<Price price="110" />
Disk Size Replica 210 GB<Price price="1.25" />
Disk IOPS Replica 23600<Price price="14.40" />
Disk Throughput Replica 2200 MB/s<Price price="7.13" />
IPv4 Hours Replica 2744 hours<Price price="4" />
Subtotal<Price price="434.09" />
Compute Credits-<Price price="10" />
Total<Price price="424.09" />

FAQ

Do Compute Credits apply to Read Replica Compute?

No, Compute Credits do not apply to Read Replica Compute.