Compute Add-ons

Every project on the Supabase Platform comes with its own dedicated Postgres instance running inside a virtual machine (VM). The following table describes the base instance with additional compute add-ons available if you need extra performance when scaling up Supabase.

PlanHourly Price USDMonthly Price USDCPUMemoryConnections: DirectConnections: PoolerRecommended Maximum DB Size
Nano (free)$0$0SharedUp to 0.5 GB60200500MB
Micro$0.01344~$102-core ARM (shared)1 GB6020010GB
Small$0.0206~$152-core ARM (shared)2 GB9040050GB
Medium$0.0822~$602-core ARM (shared)4 GB120600100GB
Large$0.1517~$1102-core ARM (dedicated)8 GB160800200GB
XL$0.2877~$2104-core ARM (dedicated)16 GB2401,000500GB
2XL$0.562~$4108-core ARM (dedicated)32 GB3801,5001TB
4XL$1.32~$96016-core ARM (dedicated)64 GB4803,0002TB
8XL$2.562~$1,87032-core ARM (dedicated)128 GB4906,0004TB
12XL$3.836~$2,80048-core ARM (dedicated)192 GB5009,0006TB
16XL$5.12~$3,73064-core ARM (dedicated)256 GB50012,00010TB

Number of connections above are recommended values.

We charge hourly for additional compute based on your usage. Read more about usage-based billing for compute.

Compute sizes can be changed in the dashboard here by selecting your project. Contact us if you require a custom plan.

Dedicated vs. shared CPU

All Postgres instances on Supabase are dedicated applications running inside dedicated virtual machines. However, the underlying hardware resources, for example the physical CPU, may be shared between multiple VMs, but appear to the OS as if it is a dedicated hardware CPU. This is commonly referred to as a vCPU (virtual CPU). Cloud providers use these shared hardware resources to save cost—you can upgrade to a larger compute add-on to guarantee a dedicated physical CPU for your instance.

Compute upgrades

When considering compute upgrades, assess whether your bottlenecks are hardware-constrained or software-constrained. For example, you may want to look into optimizing the number of connections or examining query performance. When you're happy with your Postgres instance's performance, then you can focus on additional compute resources. For example, you can load test your application in staging to understand your compute requirements. You can also start out on a smaller tier, create a report in the Dashboard to monitor your CPU utilization, and upgrade later as needed

Disk IO

SSD Disks are attached to your servers and the disk performance depends on the compute add-on of your instance. Disk IO refers to two metrics: throughput (Megabits per Second) and IOPS (Input/Output Operations per Second). Disk throughput is capped at 1,048 Mbps and IOPS is capped at 3,000 IOPS for all compute add-ons.

PlanBaseline Disk ThroughputBaseline IOPS
Nano (free)43 Mbps250 IOPS
Micro87 Mbps500 IOPS
Small174 Mbps1,000 IOPS
Medium347 Mbps2,000 IOPS
Large630 Mbps3,000 IOPS
XL1,048 Mbps3,000 IOPS
2XL1,048 Mbps3,000 IOPS
4XL1,048 Mbps3,000 IOPS
8XL1,048 Mbps3,000 IOPS
12XL1,048 Mbps3,000 IOPS
16XL1,048 Mbps3,000 IOPS

Contact us if you require a plan with higher disk throughput and IOPS.

Bursting and disk IO budget

Smaller compute instances can burst up to 1,048 Mbps and 3,000 IOPS for 30 minutes in a day. Beyond that, the performance reverts to the baseline. For example, the micro plan can burst up to 1,048 Mbps for 30 minutes a day and reverts to the baseline performance of 87 Mbps. Your disk IO budget gets replenished throughout the day.

If you need consistent disk performance, choose the XL or larger compute add-on which has the same baseline and maximum disk throughput and IOPS.

If you're unsure of how much throughput or IOPS your application requires, you can load test your project and inspect these metrics in the Dashboard. If the Disk IO % consumed stat is more than 1%, it indicates that your workload has burst beyond the baseline IO throughput during the day. If this metric goes to 100%, the workload has used up all available disk IO budget and will revert to baseline performance. Projects that use any disk IO budget are good candidates for upgrading to a larger compute add-on with higher baseline throughput.

Postgres replication slots and WAL senders

Replication Slots and WAL Senders are used to enable Postgres Replication.

The maximum number of replication slots and WAL senders depends on your compute add-on plan, as follows:

PlanMax Replication SlotsMax WAL Senders
Nano (free)55