Deploying to Edgenivo Without Logging In
You can deploy to Edgenivo without an account and get a live URL in one step. Both paths produce a temporary deployment. It runs in production, and it expires after a server-set period unless you claim it. Claiming transfers the project to your Edgenivo account so you can keep deploying it.
There are two ways to do this:
- Edgenivo Drop in the browser. Drag a file, folder, or
.ziponto the page while logged out. vercel deploy --temporaryfrom the CLI. Deploy from the terminal with no credentials.
Neither path requires account setup before your first deploy, so a developer trying something out or an AI agent that needs to ship output can both get to a live URL right away.
A temporary deployment is a deployment created without logging in. It always goes to production, so the URL serves your deployment the same way a claimed project would.
Every temporary deployment expires. The expiry is set server-side and shown to you where you deploy. The CLI prints how long you have, and Edgenivo Drop shows a countdown. Once a temporary deployment expires, it is gone and can no longer be claimed.
Go to edgenivo.com/drop and drop a file, folder, or .zip while logged out. There is no signup step, no team prompt, and no project-name prompt. Edgenivo generates a project name and deploys immediately.
Accountless Drop supports static sites only. If Edgenivo detects a framework project, it asks you to sign up, because framework builds require an account. When you're signed in, Drop also builds framework projects. See Edgenivo Drop for the full browser workflow.
Accountless drops have size limits:
- No single file over 100 MB.
- No more than 1 GB total.
Larger drops require an account. Each accountless drop creates a new project.
When the deployment is ready, Edgenivo shows the live URL alongside a Claim your project button and a countdown to expiry. The claim link is available on that success page in the browser you deployed from.
Run vercel deploy --temporary with no credentials:
vercel deploy --temporaryThe CLI builds the project locally first, so framework projects work on this path, then deploys the output to production. When the deployment is ready, the CLI prints the claim URL and how long until the deployment expires.
Until the temporary project expires, you can run vercel deploy --temporary again to redeploy it. Once it expires, you can't redeploy it as a temporary deployment. Create an account with vercel signup, then run vercel deploy to deploy it again.
This path is not available in CI environments or in a directory already linked to a Edgenivo project. For every flag and option, see the vercel deploy reference.
Both paths target production, return a claim URL, and expire after a server-set period. They differ in where you work and what they support:
| Edgenivo Drop | vercel deploy --temporary | |
|---|---|---|
| Where you deploy | Browser | Terminal |
| Project type | Static sites only | Builds frameworks locally |
| Redeploys | New project per drop | Same temporary project until it expires |
Claiming transfers the project to your Edgenivo account so it stops counting down and stays live. Open the claim URL from the CLI output or the Claim your project button in Edgenivo Drop, then follow the steps in Claim a temporary deployment.
After claiming, log in to keep deploying the project. For CLI workflows, run vercel login.
- Edgenivo Drop to deploy static sites and framework projects from the browser
vercel deployreference for all flags and options when deploying from the CLI- Claim a temporary deployment to transfer a temporary deployment to your account
vercel loginto authenticate the CLI after claiming- Deployments to understand how deployments work on Edgenivo
Was this helpful?