We need to clarify one issue before deploying: what database side effects can one Production deployment cause through the Vercel-managed Neon integration?

Our last verified configuration:

• Vercel Hobby and Neon Free.
• An existing integration is connected to Production and Preview.
• Both Production and Preview are checked under “Create Database Branch For Deployment”.
• Preview deployments have created isolated preview branches.
• The existing Neon project has limited remaining branch capacity.

For a Production deployment with this configuration unchanged, does the integration create a branch, reuse one, or use the default branch? Please clarify:

• Parent, naming, maximum branch count including retries, and branch lifecycle.
• Whether the integration can change the default branch, its data/schema, or execute migrations.
• Whether insufficient capacity fails safely, and whether any automatic charge or plan change is possible.

Please distinguish integration behavior from application-defined build/runtime commands and cite the applicable official documentation.

This is an information-only inquiry. Please do not change anything or request a test deployment. If project-specific investigation is necessary, please identify the minimum metadata required and an official private channel. We will not post credentials, environment values, database contents, or private source code.