Vercel password protection: Is $20 per project worth it?

Vercel password protection now creates a project-by-project budgeting decision for agencies. Vercel says Pro teams can enable Password Protection for $20 per protected project per month, according to its official changelog. The price is easy to understand. The harder question is deciding which projects need it.

That decision matters because Vercel also documents a separate access option with no additional cost on every plan. It requires authorised users to sign in with a Vercel account that has access to the project. The two options solve different access requirements, so agencies should compare the workflow before comparing only the price.

What we verified

Vercel’s pricing change is clear. Password Protection is available per project for Pro teams at $20 per protected project per month. Vercel’s changelog says the feature was previously offered as a $150-per-month team-level add-on.

The second documented option is Vercel Authentication. Vercel says it can protect all deployments in a project, including production deployments, at no additional cost on every plan. Access requires a Vercel account authorised for the project.

Those are the established facts. The sources do not establish every detail of an agency’s client-review process. They do not say that Password Protection is always the better choice for external reviewers, or that it removes project administration. Treat those points as workflow questions to test, not as guaranteed product behaviour.

Vercel password protection: the agency decision

The right choice depends on the access model your project needs. If the people who need access can use authorised Vercel accounts, the no-additional-cost authentication route deserves a test. If your team specifically needs Password Protection, budget it per protected project rather than as one team-wide fee.

The cost becomes more significant as the project count grows. At the documented September 2026 rate, two protected Pro projects would represent $40 per month, while five would represent $100 per month. Those are simple calculations from Vercel’s stated per-project price, not a claim about any additional plan charges.

Vercel’s changelog does not describe a bulk discount for multiple protected projects. Until Vercel documents one, agencies should model each protected project as a separate $20 monthly line item.

Where the paid option may make sense

Pay for Password Protection only when the documented control matches the project’s actual access requirement. This is a narrower recommendation than saying it is the best option for every client preview.

Start by writing down the people who need access to one representative project. Then ask whether each person can use a Vercel account authorised for that project. If the answer is yes, test Vercel Authentication before adding a recurring project charge.

If the required workflow specifically calls for Password Protection, record the $20 monthly cost against that project. Do not assume that protecting one project gives the same pricing treatment to the rest of the team’s projects. The changelog describes the charge as per project.

The cost scales faster than the headline suggests

The old and new prices answer different budgeting questions. The former $150 team-level add-on described by Vercel was a team charge. The current option is a $20 charge for each protected project on Pro.

That makes the simple comparison tempting, but an agency should model its own project list. One protected project is a different budget decision from a portfolio of five. The monthly total should be calculated before the team changes its default access process.

• List the projects. Count only the projects that genuinely need the Password Protection option.
• Identify the reviewers. Check whether the intended users can be authorised with Vercel accounts.
• Separate fact from preference. Record the access requirement first, then decide whether the paid option is worth its recurring cost.
• Test one project. Use a representative deployment and verify the access path with the people who will actually use it.

That final test is important because the changelogs establish pricing and access requirements, not the details of your agency’s approval process. A project administrator may find one option straightforward while a client reviewer finds the same path inconvenient.

What agencies should do now

Do not make Password Protection the default for every project without counting the recurring cost. Choose one project that reflects the agency’s normal client-review workflow. Compare the documented $20 monthly charge with the no-additional-cost Vercel Authentication route, including the requirement for authorised Vercel accounts.

The practical answer may differ by project. A team with authorised Vercel users can first test the no-additional-cost option. A team that has a specific reason to use Password Protection should budget it as a project-level expense and confirm the result on the deployment it plans to share.

Vercel’s change is useful because it makes the cost visible. The decision is not simply whether $20 is affordable. It is whether the selected access model is worth paying for on each project.

For the wider platform context, see our Vercel directory entry.

Sources

• Vercel: Password Protection is now available per project on Pro
• Vercel: Protect production deployments for free on every plan