Protected branches

Neon's protected branches feature lets you apply IP restrictions to specific branches in your Neon project as an added layer of data protection. Protected branches is a Neon Scale plan feature.

How to set up protected branches

The protected branches feature works in combination with Neon's IP Allow feature. The basic setup steps are:

1. Define an IP allowlist for your project
2. Restrict IP access to protected branches only
3. Set a branch as protected

Define an IP allowlist for your project

Neon ConsoleCLIAPI

To configure an allowlist:

1. Select a project in the Neon Console.
2. On the Neon Dashboard, select Project settings.
3. Select IP Allow.
4. Specify the IP addresses you want to permit. Separate multiple entries with commas.
5. Optionally, select Allow unrestricted access to non-primary branches to allow full access to your no primary branches.
6. Click Save changes.

For details about specifying IP addresses, see How to specify IP addresses.

Restrict IP access to protected branches only

After defining an IP allowlist, the next step is to select the Restrict access to protected branches only option.

This option removes IP restrictions from all branches in your Neon project and applies them to protected branches only.

After you've selected the protected branches option, click Save changes to apply the new configuration.

Set a branch as protected

The last step in the setup is to designate a branch as protected. We'll define a single branch as protected in this example, but you can have up to 5 protected branches.

To set a branch as protected:

1. In the Neon Console, select a project.

2. Select Branches to view the branches for the project.

   

3. Select a branch from the table. In this example, we'll configure our primary branch main as a protected branch.

4. On the branch page, click the More drop-down menu and select Set as protected.

   

5. In the Set as protected confirmation dialog, click Set as protected to confirm your selection.

   

   Your branch is now designated as protected, as indicated by the protected branch shield icon, shown below. Only the trusted IP addresses on your IP allowlist will be able to connect to this branch.

   important

   With this configuration, there is no restriction on IP access to the other branches in your project.

   

   The protected branch designation also appears on your Branches page.