Title: First Preview deployment unexpectedly classified as Production — safe recovery path?
Hello Vercel team,
I'm deploying a personal, non-commercial browser game on the Hobby plan.
I created a new, isolated Vercel project to test the game through a protected Preview deployment before making any public release.
Using Vercel CLI 65.5.0, I explicitly requested:
vercel deploy --target=preview
However, Vercel created the project's first deployment as Production, with the resulting deployment marked READY / PROMOTED.
Before deploying, I had configured Vercel Authentication for All Deployments. After detecting the unexpected deployment classification, I paused the project. The deployment and its two generated aliases now return HTTP 503.
Additional context:
- Git automatic deployments were disconnected.
- No custom domain was configured.
- No paid services or upgrades were enabled.
- The deployed application is a static Vite/Phaser website.
- No subsequent deployment attempts were made.
- The GitHub source repository remains private.
I found these relevant references:
I understand that Vercel may assign a project's first deployment to Production even when Preview was explicitly requested.
Could you please clarify the safest supported recovery procedure?
- Can the existing first Production deployment remain paused while a subsequent, correctly classified Preview deployment is created?
- Can that Preview be accessed through Vercel Authentication without resuming the Production deployment or its generated aliases?
- If project pausing prevents Preview access, is there a supported way to keep Production unavailable while testing Preview privately?
- Would deleting the existing deployment cause the next deployment to be treated as the first Production deployment again?
- Is there any recommended cleanup or billing verification for this situation on Hobby?
My goal is to test the website privately on desktop and mobile, without accidentally opening the Production website.
I can provide redacted deployment IDs, timestamps, and relevant logs through an appropriate private support channel.
Thank you.