Vercel Deployment Protection and Jiayang Cloud

Updated 17 October 2026

On Vercel, Standard Protection covers every deployment but your production domains, which stay public unless you choose All Deployments. Viewers sign in with Vercel accounts, and passing a verified identity to your app takes Passport on Enterprise. On Jiayang Cloud every app starts private, anyone you share it with by email can sign in without an account, and your app gets a signed token saying who is calling, on every plan.

What follows about Vercel comes from Vercel's docs and knowledge base, read on 16 and 17 October 2026 and listed at the end.

What Vercel's protection covers

Standard Protection, on every plan, covers every deployment except production domains. Vercel Authentication is on by default. To cover production domains too, choose All Deployments, which every plan has.
With Vercel Authentication, a deployment opens for logged-in team members with at least a viewer role, project members, members of an access group with the project, Vercel users you've given access, anyone holding a shareable link, and tools sending the bypass header. On Hobby, an account can give one outside user access.
Password Protection costs $20 a month per protected project on Pro, and is included on Enterprise. Existing Pro teams on the older Advanced Deployment Protection package pay $150 a month per team. Hobby doesn't have it.
Passport signs visitors in through your own identity provider, and your code can read and verify who they are. It's on Enterprise. Trusted IPs are on Enterprise too.

Side by side, for an internal app

What	Vercel	Jiayang Cloud
Production, until you change it	Production domains are public, unless you choose All Deployments	Private. Only the people you share it with get in. A public path, for webhooks, has to be added by a person
Viewers	Vercel users with access, or anyone with a shareable link or the password	Any email address, everyone at your company's domain, or a group. No account needed
Your own identity provider	Passport, on Enterprise	Single sign-on, on Enterprise, and on Business for early customers for a limited time
The caller, in your code	Passport's verified identity, on Enterprise	A signed token on every plan, checked by SDKs for Node, Python, Go and Rust
Removing someone	Granted access can be revoked at any time	Within 60 seconds, open connections included
What it costs to protect	Vercel Authentication on every plan. A password at $20 a month per project on Pro	Part of every plan, priced per workspace

When Vercel is the better fit

For public sites and front ends on Vercel's network, and for previews a team reviews and comments on before they go live. If an app's viewers are all on your Vercel team already, Vercel Authentication may be all you need.

Move a Vercel project here

jiayang import reads the project with a Vercel token you paste once, clones its repository, and sets it up as a new app: its build settings, production variables and cron jobs, which become schedules. It shows you the plan and asks before it changes anything. A dry run stops after the plan, which looks like this, shortened:

jiayang import vercel:expense-tracker acme/expenses --dry-run

Importing expense-tracker from Vercel into acme/expenses.

Code: https://github.com/acme-finance/expense-tracker.git (main), cloned into expense-tracker, with the app in web
Runs as: a static site, served by Workers (Vite)

Environment variables (2)
  REGION
  VITE_API_BASE

Secrets (2)
  OPENAI_API_KEY for OpenAI, added to requests to api.openai.com, Vercel keeps it write-only, so its value has to come from you
  STRIPE_SECRET_KEY for Stripe, added to requests to api.stripe.com

Schedules, added once it's deployed (1)
  GET /api/cron/digest at "0 7 * * 1-5" (UTC)

That was a dry run, so nothing was made, written or deployed.

Only production's values come over. A key for an API we know becomes a secret that our outbound proxy adds to the app's requests, so the code never holds it. Next.js runs as a container unless it uses OpenNext. Vercel's Deployment Protection has nothing to carry over: only the people you share the app with can open it. See Import from Vercel.

Sources

Deployment Protection on Vercel, Vercel's docs, updated 15 September 2026. Checked 17 October 2026.
How to lock down deployments on Vercel and v0, Vercel's knowledge base, published 3 November 2025. Checked 17 October 2026.
Restrict access to deployments with Vercel Authentication, Vercel's docs, updated 15 September 2026. Checked 17 October 2026.
Restrict access to deployments with Passport, Vercel's docs, updated 21 September 2026. Checked 16 October 2026.

Import from Vercel, in the docs
How we differ from other ways to keep an app private
Pricing