Usage meters
Section titled “Usage meters”Netlify Database billing is based on actual usage of compute and bandwidth.
Database storage will be billed no earlier than July 1, 2026, with rates announced in advance. Storage rates will be based upon comparable industry standards, and the vast majority of users are expected to utilize a very low credit amount for storage.
For more details on how credits are consumed, check out How credits work.
Database Compute
Section titled “Database Compute”This meter is based on the total amount of database compute units consumed over a billing period. This amount is dependent on the actual usage of your database, and your auto-scale and sleep on inactivity settings.
The current credit cost is 10 credits per unit.
Example compute usage
Section titled “Example compute usage”For this example, let’s assume the following:
- You have a Personal plan. On this plan, your database is configured with default auto-scale settings (minimum of 1 compute unit, maximum of 4) and goes to sleep automatically after 5 minutes of idle time.
- You have one project with a database.
- That database is active for 37 hours in total throughout the billing period (including idle time before going to sleep).
If the database only needs the default minimum compute units for that whole duration - you will be billed for 37 compute units in total.
However, what if the database consumes compute at varying levels throughout that time? For example, suppose it uses:
- 33 hours of using the minimum compute (1 unit) - consuming 1 unit per hour, or 33 units in total
- 2.5 hours of using 2 compute units - consuming 2 units per hour, or 5 units in total
- 1.5 hours of using 4 compute units - consuming 4 units per hour, or 6 units in total.
In this scenario, you will consume 44 compute units in total. At the current credit cost of 10 credits per unit, you will be billed for 440 credits for database compute.
Database Bandwidth
Section titled “Database Bandwidth”This meter measures the total network traffic going out from Netlify Database in response to any request over the billing period.
Typically, requests to the database are made mostly by code in your Netlify Functions or Edge Functions which query or modify data. Network traffic going out from your database into your functions is measured in this meter.
The current credit cost is 20 credits per GB.
If your database sent out 4.37 GB over the network in the billing period, you will be billed for 87.4 credits for database bandwidth.
Limits
Section titled “Limits”Netlify Database has limits based on your Credit-based pricing plan.
The limits below are designed to be fair and protect you from unintended high costs due to excessive usage. If you would like higher limits, here are your options:
- If you have an Enterprise plan, contact your account manager directly.
- If you have a Pro plan, please contact support.
| Limit | Free | Personal | Pro | Enterprise |
|---|---|---|---|---|
| Databases per account | 3 databases | 5 databases | 50 databases | 500 databases by default |
| Branches per database | 20 branches | 50 branches | 150 branches | 225 branches |
| On-schedule backup retention | 3 days | 7 days | 30 days | 30 days |
| On-publish backup retention | Backup of last published deploy only | For 3 latest published deploys | For 10 latest published deploys | For 10 latest published deploys |
| Minimum compute units per database | 1 | 1 | 1 | 4 |
| Maximum compute units per database | 1 | 4 | 16 | 32 |
| Minimum sleep-on-inactivity time | 5 minutes | 5 minutes | 5 minutes | 5 minutes |
| Maximum sleep-on-inactivity time | 5 minutes | 5 minutes | Always on | Always on |
| Total compute units per database over a billing period | 48 database compute units | No limit | No limit | No limit |
| Total data written per database over a billing period | 5 GB | 100 GB | 100 GB | No limit |
| Database bandwidth (network data out) per database over a billing period | 5 GB | 100 GB | 100 GB | No limit |
| Database storage size per database (maximum at any given point) | 5 GB | 100 GB | 100 GB | No limit |
Storage of payment card data
Section titled “Storage of payment card data”If you use or process credit card data, please note that Database Services are not certified under the Payment Card Industry Data Security Standard (PCI-DSS). You must not use Database Services to store, process, or transmit cardholder data, primary account numbers, or other data regulated under PCI-DSS.
HIPAA compliance
Section titled “HIPAA compliance”Database Services are not HIPAA-eligible by default. Customers who require HIPAA-compliant database functionality must contact Netlify to configure their account in a compliant fashion. You must not store Protected Health Information in Database Services that are not set up to be HIPAA compliant.
Did you find this doc useful?
Your feedback helps us improve our docs.