Vercel Changes the Bill for Private Production Sites

The added bill for a private production site on Vercel now starts at $0, not a mandatory $150 a month. Since September 9, 2026, you can protect production with Vercel Authentication at no extra protection charge, while a shared password on Pro costs $20 for each protected project.

The change is really two price paths

Vercel changed the cost of keeping a whole deployment private. This is a gate in front of the deployed site, not the sign-in system you build for your end users.

The free path is Vercel Authentication. Turn it on for All Deployments and Vercel protects the production domain, preview URLs, and generated deployment URLs. A visitor has to sign in with a Vercel account and have access to that project. Vercel now includes this on Hobby, Pro, and Enterprise at no added protection cost.

The paid path is Password Protection. On a Pro team using the per-project model, it costs $20 per protected project per month. Visitors enter the password you set before they can see the deployment.

Before this change, protecting production through Vercel's Advanced Deployment Protection add-on cost $150 per team per month. Password Protection came with that team-level add-on and covered every project. The new pricing separates the two jobs: account-based access is free, while shared-password access is billed project by project.

That distinction matters more than the feature names. If everyone who needs the site already belongs in your Vercel project, the added protection line can be $0. If clients or outside reviewers need a simple password, the number of private projects now drives the bill.

What the cost looks like at 1, 5, and 8 projects

These are hypothetical project counts, not Vercel limits. The table isolates the protection line so you can see the choice clearly.

For one password-protected project, the new project price is $130 less than the legacy team charge. At five, it is $50 less. At eight, it is $10 more. Eight is the first example here where the old team-wide price beats the new per-project total.

The comparison only works if the access method fits. Eight internal tools used by people who already have project access can still carry a $0 added Vercel Authentication charge. One client site whose reviewers should not join your Vercel project may justify the $20 password.

For the rest of the platform bill, keep the protection line separate from the Vercel pricing guide. Mixing seats, usage, and protection into one headline makes the decision harder than it is.

Who should use each option

An internal product team

A product team can put a production admin panel or operations dashboard behind Vercel Authentication. Staff sign in with their Vercel accounts, and access follows team, project, or access-group permissions.

The payoff is clean offboarding and a $0 added protection charge. Remove someone's project access and the gate stops treating that account as eligible. You do not need to circulate a password that outlives the person who left.

An agency sharing private client sites

An agency may have five production sites waiting for approval across five clients. If each client needs a shared password instead of Vercel project access, the protection line is now $100 a month on project-priced Pro billing.

That is cheaper than the legacy $150 team add-on at this count, but it is not automatically the right workflow. You are paying to avoid account setup and project-access administration for external reviewers.

A startup preparing an unreleased launch

A startup can keep a real production domain private while the team finishes onboarding, pricing, or legal pages. If every reviewer can sign in to Vercel and receive project access, Vercel Authentication does the job without a separate protection fee.

There is one scope detail to understand. All Deployments protects previews and production together. A production-only scope that leaves previews public requires Trusted IPs on Enterprise, although free Deployment Protection Exceptions can make selected preview domains public.

A Pro team already paying $150

Existing Pro teams that bought Advanced Deployment Protection do not move automatically. Vercel says they keep the $150 monthly team model and password protection for every project. The invoice line appears as Team-level Password Protection.

That can be a good legacy position once enough projects need passwords. Do not cancel it because the new public price looks lower. Vercel tells existing teams to contact support if they want to switch to project-level Password Protection, so get the migration treatment confirmed before changing anything.

How to make the choice in the dashboard

You do not need code for this change. You need a project list, an audience decision, and the current settings page.

1. 1

   Label each private project by audience

   Mark a project account access when every visitor can sign in to Vercel and receive project access. Mark it shared password when outside reviewers need the password flow. Public projects stay out of both counts.

2. 2

   Calculate protection separately

   Multiply only the shared-password count by $20. Keep the $20 Pro platform fee, additional $20 paid seats, usage, and taxes on separate rows. If your invoice already has Team-level Password Protection, compare against $150 and contact support before changing it.

3. 3

   Turn on the matching gate

   Open the project in Vercel, then go to its Deployment Protection settings. For Vercel Authentication, enable it, choose All Deployments, and save. For Password Protection, enable it, choose the deployment environment, set the password, and save.

4. 4

   Test the visitor you actually have

   Open the production URL in a private browser. Test an approved Vercel account for the free path or the current password for the paid path. Also test any automated system that calls the deployment, because protected tools need an approved access route or an automation bypass.

The honest part

The free option moves cost into access administration. Every human visitor still needs a Vercel account with suitable project access, even when the protection charge is $0. That is usually fine for an internal team and often awkward for a rotating list of clients.

The password option moves administration into a shared secret. A visitor normally enters it once per deployment URL because Vercel sets a cookie. Change the password and those visitors have to enter the new one. Someone still has to distribute and rotate it safely.

Disabling project-level Password Protection stops future charges, but it also changes what stands between visitors and every existing deployment in that project. Confirm that Vercel Authentication or another intended method remains active before you turn the password off.

You may also still see Advanced Deployment Protection listed at $150 on Vercel's general pricing page. The current product-specific docs explain the split: existing Pro subscribers keep that team model, while current Pro Password Protection is $20 per protected project. Treat the invoice and the Deployment Protection docs as the source for your team's actual billing model.

What to do on Monday

Act this week if you pay for production protection, run internal production tools, or keep several client sites behind one shared password. List the private projects, mark who needs access, and put the protection charge on its own budget row.

Use free Vercel Authentication where account-based project access is acceptable. Use the $20 password only where the simpler external visitor flow earns its monthly cost. If you already have the $150 team model, wait for a written migration answer from support before touching it.

Public production sites are unaffected. Enterprise teams already have team-level Password Protection included, and Hobby users still cannot buy Password Protection, although they can use Vercel Authentication at no added protection cost.

For more plain-English breakdowns of the tools changing your operating costs, join the newsletter.