3 min read

Manage and optimize usage for Vercel Postgres

Learn how to understand the different charts in the Vercel dashboard, how usage relates to billing, and how to optimize your usage of Postgres.
Table of Contents

The Postgres section shows the following charts:

Manage and Optimize pricing
Compute timeThe CPU hours spent computing responses to requests by your Postgres storeYesLearn More
Data storageThe data stored across your Postgres storesYesLearn More
Data transferData transferred between your Postgres databases and compute endpointsYesLearn More
Written dataThe data written to all your Postgres databasesYesLearn More
DatabasesThe number of Postgres databases you have createdYesLearn More
Managed Infrastructure hobby and pro resources
Hobby Included
Pro Included
Pro Additional
Pro Price
60 HoursFirst 100 Hours1 Compute Hour$0.10
N/AFirst 512 MB1 GB$0.10
First DatabaseFirst DatabasePer 1 Database$1.00
First 512 MB IncludedFirst 512 MB Included1 GB$0.12
N/AFirst 512 MB1 GB$0.096

Vercel calculates compute time based on the active time of your database, multiplied by the number of CPUs available per month. The active time includes periods when the database is receiving requests and for a duration (default 300 seconds) after the last request is received. Following this period of inactivity, the database scales down to zero, effectively pausing compute time billing.

The usage chart shows the total amount of CPU hours your Postgres store has spent computing responses to requests during the selected period. Each plan includes a set amount of compute time, once you exceed this limit you're charged a set price per CPU hour. Learn More.

To reduce cost, you can reduce the Compute Size or the period of inactivity before the database scales down to zero. To manage these settings:

  1. Go to the Vercel Dashboard
  2. Click on the Storage tab and select your database
  3. From the Settings menu item, under Performance, adjust the settings as required

Vercel calculates storage as the average amount of storage used across all projects within your team in the past month. Each plan includes a set amount of storage, and once you exceed this limit you're charged a set price per GB of storage. Learn More.

  • You should note that each Postgres database uses 33MB of storage space, even before any data is stored. This is the default storage footprint of the Postgres server itself. Therefore, you should delete the database completely if you no longer need it

Vercel calculates Data Transfer as the amount of data transferred out of the database. Each plan includes a set amount of storage, and once you exceed this limit you're charged a set price per GB of data transfer. Learn More.

  • To stop incurring usage or costs for data transfer, you should stop querying the database or delete it when it is no longer required

Vercel calculates written data by the amount of data changes that are committed from compute resources to storage. It encompasses all operations that modify data within your tables, including: inserting, updating, deleting, and migrating data. For more information, see the Vercel Postgres docs.

You are charged based on the total volume of written data (measured in GB) multiplied by the price per GB. This includes both user-initiated data modifications and the initial written data from setting up new databases. Each plan includes a set amount of written data, and once you exceed this limit you're charged a set price per GB of written data. Learn More.

  • Frequent Updates or Deletions: High volumes of update or delete operations can contribute to written data volume.
  • Database Initialization: The initial setup of a database contributes to written data volume, as explained above.
  • System Operations: Background tasks and system maintenance operations that ensure the health and performance of your database also contribute to written data.

The Databases chart shows the total number of Postgres databases that your team currently has active. Each plan includes 1 Postgres database. After that you're charged a set price each month for each additional database, up to the plan maximum. Learn More

Last updated on May 18, 2024