Drag and drop
Upload a file, a folder, or a ZIP from the console and deploy it without a repository or the CLI.
Drop takes files straight from your machine, packages them in the browser, and deploys them. Use it for output you have already built, for a one-off preview, or for code that is not in a repository Gigadrive Network can read.
What you can drop
A single file, a folder, several of either, or a ZIP archive. Folder structure is preserved. When everything you dropped sits under one top-level folder, that folder is stripped, so mysite/index.html is deployed as index.html.
A ZIP is unpacked in the browser, filtered, and repacked before it is uploaded. Its paths are kept as they are, so an archive whose files all sit under one folder deploys with that folder still in the path. Everything else is zipped client side.
Folders named dist or build are skipped
The packager drops any path with a segment named .git, node_modules, .next, dist, build, .turbo,
.vercel, or .DS_Store. That filter runs on the paths as dropped, before the shared top-level folder is stripped,
so dropping a folder literally named dist or build removes every file in it and the upload fails with nothing left
to deploy. Open the folder and drop its contents instead.
Deploy an upload
Open Drop
Drag files onto any console page, or select your organization, choose New app, then open the Drop tab.
Add your files and name the application
Drop the files, or use Choose files and Choose folder. The console counts what you selected and suggests an application name from it. Dropping onto an application page instead offers to redeploy into that application.
Deploy
Deploy packages the archive in your browser, creates the application, then uploads the archive in parts with a progress bar. The deployment is queued the moment the upload completes, and the console opens its log.
Static sites without a config file
When the upload has no gigadrive.yaml at its root (or one of the legacy nebula.* names) and its contents look like static web files, the console adds this one before uploading. It is the same fallback the platform writes for a static site with no configuration, and it is what makes a bare folder of HTML deployable with no setup.
version: 4
assets: '.'Put your own gigadrive.yaml in the upload when the project needs more than static files, for example a Function or a route table. Configuration describes the file.
Once the archive is packaged, the console says so if no index.html sits at the project root. Individual files still deploy at their own paths, but / returns 404 until something answers it.
How an upload differs from a Git deployment
An upload carries no branch, so it lands in the Preview environment and is served on that deployment's own permanent URL. The production alias <name>.gigadrive.app moves only for a deployment that runs in the Production environment, which needs a connected repository and a branch Production matches.
Nothing else about the deployment changes. The same build pipeline runs, and the same build cache applies. What you give up is the commit behind the deployment: to ship a change, drop the files again.