Password Protection

Password Protection requires visitors to enter a pre-defined password before they can access your deployment. You can set the desired password from your project settings when enabling the feature, and update it any time.

Password Protection pricing depends on your plan and when your team started using the feature:

For project-priced Pro teams, Edgenivo adds the charge when you enable Password Protection for a project. Disabling Password Protection stops future charges for that project. The project's remaining Deployment Protection settings determine who can access its deployments.

See Usage & Pricing for Deployment Protection for the full feature and plan comparison.

The table below outlines key considerations and security implications when using Password Protection for your deployments on Edgenivo.

You can manage Password Protection through the dashboard, API, or Terraform.

1. Go to project deployment protection settings

   From your Edgenivo dashboard:

   1. Select the project you want to enable Password Protection for
   2. Go to Deployment Protection in the sidebar

2. Configure Password Protection

   From the Password Protection section:

   1. Use the toggle to enable the feature
   2. Select the deployment environment you want to protect
   3. Enter a password of your choice
   4. Finally, select Save

   All your existing and future deployments will be protected with a password for the project. The next time you access a deployment, you'll need to enter the password. After you enter it, a cookie is set in your browser for that deployment URL so you don't need to enter the password again.

   

You can manage Password Protection using the Edgenivo API endpoint to update an existing project with the following body.

To enable or update Password Protection, send the passwordProtection object:

{
  "passwordProtection": {
    "deploymentType": "prod_deployment_urls_and_all_previews",
    "password": "your_password_here"
  }
}

To disable Password Protection, set passwordProtection to null:

{
  "passwordProtection": null
}

You can configure Password Protection using password_protection in the vercel_project data source in the Edgenivo Terraform Provider.

Password Protection checks every request before it reaches your application, including requests from CI jobs, end-to-end tests, and webhooks. Those requests can't enter a password, so they receive a 401 response as soon as you enable protection. Set up Protection Bypass for Automation when you enable Password Protection, and send the secret in the x-vercel-protection-bypass header.

For test runners, add the header to every request and set x-vercel-set-bypass-cookie to true so in-browser navigation doesn't hit the password prompt. See the Playwright and Cypress configurations.

To check the bypass, request a protected deployment with the secret. A 200 response means the bypass works:

curl -I -H "x-vercel-protection-bypass: $VERCEL_AUTOMATION_BYPASS_SECRET" \
  https://your-deployment.vercel.app

If requests that worked before you enabled Password Protection now return 401, find the matching symptom: