Drop it.
It's Live.
Drop the whole system, not just the output. One ZIP becomes an app-backed deployment with its runtime, environment, domains, observability, and recovery controls attached.
product-system.zip Secure uploadThe archive is only the beginning.
A Drop becomes a workload, a URL, an environment, and an operational record inside your project.
From local project to operated system.
The upload path is designed as a deployment transaction, not a file transfer. Every stage has a clear state, and failures stop before an unsafe archive can become a live workload.
- 01
Upload
Send one project archive from Console or CLI, with an optional build path for monorepos and nested projects.
- 02
Inspect
Validate the ZIP structure and complete a mandatory security inspection before deployment resources are created.
- 03
Deploy
Bring the application online with a globally unique managed URL and framework-aware runtime routing.
- 04
Operate
Keep domains, environment, logs, monitoring, traffic, schedules, history, and recovery in one place.
Your Drop does not disappear after publish.
It lives beside your applications and databases as a first-class project resource. The same surface that launches it is where your team observes, updates, and recovers it.
- Replace the source without replacing the resource
- Preserve a deployment history for every release
- Use custom domains and explicit runtime settings
Same gesture. A different operating model.
Vercel and Netlify both offer capable browser-based deployment. Skytells Drops is built for teams that want the archive to remain attached to a complete application lifecycle inside an existing cloud project.
| Capability | Skytells Drops | Vercel Drop | Netlify Drop |
|---|---|---|---|
| Browser input | ZIP archive | File, folder, or ZIP | Project or output folder |
| Primary model | App-backed resource in an existing project | One-off uploads, static sites, and prototypes | Publish a web project or built output |
| Update path | Update the same Drop, redeploy source, or roll back | Each browser Drop creates a new project | Drop an updated project or output into Deploys |
| Archive gate | Mandatory validation and security inspection before launch | Provider deployment controls | Provider deployment controls |
| Skytells emphasis | Runtime, environment, domains, logs, monitoring, traffic, schedules, and recovery | Each platform provides its own broader project and deployment tooling | |
Comparison reflects public vendor documentation reviewed August 1, 2026. Read the current Vercel Drop documentation and Netlify deployment documentation.
Nothing launches before the archive clears inspection.
Drops treats uploaded code as untrusted until it passes structural validation and security inspection. The gate runs before the live workload and managed domain are created.
Everything that travels with the archive.
Is a Drop only for static sites?
No. A Drop is an app-backed deployment, not a static storage bucket. Upload the complete runnable project as an archive and manage its runtime, environment, domains, logs, monitoring, traffic, schedules, deployment history, and settings from the same project.
Do I need to connect a Git repository?
No. The archive is the source for the deployment. Create or update a Drop from Console, or send the same archive through the CLI workflow.
What happens before a Drop goes live?
Skytells validates the archive structure and performs a mandatory security inspection before provisioning the workload. An archive that does not pass inspection is not deployed.
Can I update or roll back a Drop?
Yes. Upload a new archive to the same Drop, redeploy an existing inspected source after configuration changes, or roll back to an earlier deployment from its history.