> ## Documentation Index
> Fetch the complete documentation index at: https://docs.datafold.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connection Budgets

> How connection budgets are enforced across data diffs in Datafold

Datafold enforces a **shared connection limit per database** across all data diffs. This keeps database usage predictable, which matters most when a database has limited connection capacity.

When you set a maximum number of connections on a data connection, Datafold respects it **collectively** across all running diffs that target that connection, whatever their type. No combination of diff runs exceeds the limit, which:

* Keeps resource usage predictable
* Protects the database from overload
* Means you set the limit once instead of per diff

## What the budget applies to

| Job | Connection budget applied? |
| - | - |
| In-database diffs | Yes |
| Cross-database diffs | Yes |
| Monitor runs | Yes (each run is a data diff) |
| Schema fetching | No |

## Configuration

Set **Max connections** in **Settings** → **Integrations** → **Data Connections** → your connection. Datafold enforces it across all diff runs that target that database.

Questions or unexpected behavior? Contact [support@datafold.com](mailto:support@datafold.com).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.