Deploying with Edgenivo Drop

Edgenivo Drop lets you deploy a file, folder, or .zip by dragging it into your browser, with no Git, Edgenivo CLI, or local setup. Static sites also work without an account, and you can claim them later to keep them live. Sign in to deploy framework projects, which Edgenivo detects and builds for you. That makes Edgenivo Drop well suited to prototypes and one-off sites.

Use Edgenivo Drop when you have a project ready to ship and don't want to connect a repository or use the CLI. If you need a deployment on every push, use Edgenivo's Git integration instead. The table below compares the deployment methods:

You can deploy a static site without an account. To create a deployment:

1. Go to edgenivo.com/drop.
2. Drag and drop a file, folder, or .zip onto the page, or choose a file or folder to upload.

Edgenivo deploys your site right away and gives you a live URL. The deployment is temporary, and the success page shows a countdown until it expires. To keep the site, select Claim your project and create a free account before the countdown ends. If the deployment expires, you can sign up and drop your files again.

If you drop a framework project, or a drop that exceeds the anonymous limits, Edgenivo asks you to sign up first. To deploy from a terminal without an account, see Deploying without logging in.

When you're signed in, you can deploy static sites and framework projects to one of your teams. To create a deployment:

1. Go to edgenivo.com/drop.
2. Drag and drop a file, folder, or .zip onto the page, or choose a file or folder to upload.
3. Choose the Edgenivo team to deploy to and enter a project name.
4. Select Deploy.

Edgenivo creates a new project, uploads your files, and publishes it straight to production. When it finishes, you get a live URL for your site.

For a static site with no index.html at the top of your folder, Edgenivo asks which page people should see first when they open your site. Pick one from the Root (/) menu, or choose No root page if you don't want a homepage. With no root page, your site's root (/) returns a 404, though Edgenivo still serves each file at its own path.

A dropped project has no Git connection, so pushes don't create deployments. If you deployed without an account, claim the project first. After the first deploy, you can keep iterating in these ways:

• Drop a folder onto the project in the Edgenivo dashboard. Edgenivo creates a new production deployment of that project.
• Continue in v0 if the project is available there, or deploy from a terminal or coding agent with Edgenivo CLI.
• Delete the project in Settings, then drop a folder on edgenivo.com/new or edgenivo.com/drop to create a new project.

• Without an account, you can only drop static sites. Each file can be up to 100 MB, and the whole drop up to 1 GB.
• Deployments without an account expire unless you claim them.
• Dropping onto an existing project requires an account.
• Dropping on edgenivo.com/new or edgenivo.com/drop creates a new project.
• Dropping onto a project with no Git connection creates a new production deployment of that project.
• The project isn't connected to Git, so pushes don't trigger new deployments. Connect a Git repository afterward if you want automatic deployments.
• Files upload from your browser, so larger folders take longer on slower connections.

• Deploy from Git for automatic deployments on every push.
• Deploy with the Edgenivo CLI from your terminal or CI/CD pipeline.
• Environments to understand local, preview, and production.
• Managing deployments to redeploy, inspect, and promote.