Hello Vercel community,
I'm looking for guidance on safely creating the first Preview deployment of a new Vercel project without accidentally creating a Production deployment.
Project context
- Plan: Hobby
- Application: static JavaScript dashboard
- Purpose: private internal testing with exclusively synthetic data
- Deployment Protection: Vercel Authentication (SSO) enabled for all deployments
- Git automatic deployments: disabled
- Production deployment: not authorized
- Current project state: no active deployments
What happened
Attempt 1 — Deployment API
We attempted to create a deployment from a specific Git commit without specifying a production target, expecting a Preview deployment.
However, Vercel classified it as target: production.
We immediately canceled the deployment. Its final status is CANCELED, and the project has no active deployment.
Attempt 2 — Explicit Preview target
We tried specifying target: "preview" in the deployment API.
The API returned HTTP 400:
target should be 'production', 'staging', or a custom environment identifier
No deployment was created.
Attempt 3 — Vercel CLI authentication
We prepared an isolated environment using Vercel CLI 66.1.0 to investigate a prebuilt Preview deployment.
However, vercel login failed with TypeError: fetch failed before displaying an authorization code or login URL.
We stopped without deploying anything.
What we need to know
- Is it officially possible to create a project's very first deployment directly in Preview, without first creating any Production deployment?
- For the Deployment API, is
target: "staging"equivalent to the built-in Preview environment, or does it have different semantics? - Does
vercel deploy --prebuilt --environment=previewguarantee that the first deployment will be classified as Preview? - If this is not supported, what is the safest officially recommended workflow for an isolated, private testing project?
- Is there a documented browser-based or other supported deployment workflow when the CLI environment cannot authenticate?
Security requirements
We must preserve Vercel Authentication and avoid publicly accessible deployment URLs, bypass links, real company data, automatic Git deployments, and accidental Production deployments.
We are not asking how to disable these protections.
Our goal is to validate a private static dashboard in a real HTTPS Preview environment before authorizing any further release.
Any guidance, official documentation, or clarification about first-deployment target classification would be greatly appreciated.
Thank you!