Drops Deployment & Operations
Deploy a static site or simple service from a ZIP archive without connecting a Git repository, then operate it through the inherited Skytells app architecture.
Drops let you deploy a static site or simple service directly from a ZIP archive. They are useful for generated sites, exported frontends, prototypes, and build artifacts that do not need a connected Git repository.
Every Drop belongs to a project and receives a managed *.drops.skytells.app domain.
In the Console, Drops have a separate Project > Drops menu from standard apps. Underneath that product-specific entry point, every Drop inherits the Skytells app architecture and is operated through the same deployment and resource systems as an app.
How Drops Inherit the App Architecture
A Drop uses an uploaded ZIP archive as its source instead of Git or a container registry. It shares the same project boundary, deployment history, status model, limits, networking, and operational controls as an app.
| Inherited app capability | What it means for a Drop |
|---|---|
| Project ownership and access | The Drop belongs to one project and follows that project's member roles and permissions. |
| Deployments | Every upload, redeploy, and rollback becomes part of the Drop's release history. Drop releases appear in the all-project Workspace Deployments timeline and in the Drop's own deployment history. |
| Workspace Resources | The Drop is included as an app in the all-project Workspace Resources inventory. |
| Domains and networking | The Drop receives a managed domain and can use custom domains through the standard app routing layer. |
| Environment and operations | Environment variables, logs, monitoring, traffic, schedules, and settings use the same architecture as standard apps. |
| Limits | App count, deployment quota, concurrent build, size, and billing checks apply in addition to Drop ZIP limits. |
The separate Drops menu gives archive deployments a focused creation and upload workflow while keeping familiar app operations in one consistent experience.
When to Use a Drop
No Git required
Upload the artifact you already have without creating or connecting a repository.
Fast replacement uploads
Publish a new ZIP to update the same Drop while preserving its domain and configuration.
Archive security scan
Skytells validates and scans the archive before any build or deployment begins.
Managed domain
Each Drop receives a stable *.drops.skytells.app hostname and can also use custom domains.
Use a standard Git app when you need branch-based CI/CD, preview deployments, or source history. Use App Catalog when you want to launch a curated complete application stack.
Prepare the ZIP
Before uploading:
- include the files the site or service needs at runtime;
- remove secrets, local credentials,
.envfiles, and private keys; - exclude dependency caches and unrelated source artifacts to keep the archive small;
- confirm the expected build output folder when your archive needs a build step;
- use a simple, recognizable filename so later operators know what was uploaded.
Treat the ZIP as deployable source. Never include credentials in the archive. Add secrets through the Drop's Environment Variables page after creation.
Create and Deploy a Drop
Open the Project
Choose the project that should own the Drop, then select Drops in the project navigation.
Start a New Drop
Select New Drop and choose the ZIP archive from your computer.
Choose Its Name and Slug
Enter a display name and an available Drop slug. The slug becomes part of the managed *.drops.skytells.app domain, so choose a stable public identifier.
Configure the Build Output
If the archive contains a project that must be built, set the build path or output folder required by that project. For a ready-to-serve static archive, use the folder containing the final site files.
Upload and Monitor
Start the deployment. The Console reports progress through upload validation, security inspection, resource preparation, build, and deployment. Do not close the page while the browser is still transferring the ZIP.
Verify the Result
Wait for a ready state, open the managed domain, and test the main routes and assets. Use deployment logs if the build fails or the deployed page is incomplete.
Upload Limits
| Plan | Drops | Maximum ZIP size |
|---|---|---|
| Free | Not available | — |
| Hobby | Available | 12 MB |
| Pro | Available | 50 MB |
| Enterprise | Available | 100 MB |
Normal project app limits, deployment quotas, concurrent build limits, and account billing status also apply.
What Happens During Deployment
- Skytells validates the archive type and size.
- The archive is checked for known malicious content.
- The Drop resource and managed domain are prepared.
- Skytells builds or serves the configured archive content.
- The release is added to deployment history and the managed domain points to the running version.
If authentication, plan limits, slug availability, archive validation, or security inspection fails, the archive is not deployed.
Update, Redeploy, and Purge
Upload a replacement ZIP when you have new source or output files. This creates a new deployment while preserving the Drop identity, domain, environment variables, and operational history.
Redeploy when you want to rebuild the currently stored archive without uploading it again. This is useful after changing environment variables or recovering from a transient build failure.
Purge build cache before the next upload when stale cached layers may be affecting the result. Purging makes the next build slower, so use it as a troubleshooting step rather than a default.
Roll back from deployment history when a previous deployment is known to work. Verify the managed domain after rollback and remember that current environment configuration may differ from the earlier release.
Operate a Drop
The Drop navigation includes:
| Page | Use it for |
|---|---|
| Overview | Current status, managed domain, and primary actions |
| Deployments | Upload history, logs, redeploy, and rollback |
| Domains | Managed and custom hostnames |
| Environment Variables | Runtime configuration and secrets |
| Logs | Build and runtime troubleshooting |
| Monitoring | Resource health and utilization |
| Schedules | Recurring jobs supported by the service |
| Traffic | Request and response activity |
| Settings | Name, configuration, and lifecycle controls |
These pages are Drop-specific routes in the Console, but their behavior is inherited from the corresponding app capabilities. Use the linked app documentation when you need deeper operational guidance:
- App Deployments explains deployment states, history, logs, and redeployment behavior shared by Drops.
- App Domains explains custom domain routing shared by Drops.
- App Environment Variables explains runtime configuration and secret handling shared by Drops.
- App Logs explains the build and runtime log streams shared by Drops.
- App Monitoring explains the container health and metrics model shared by Drops.
Troubleshooting
The ZIP is rejected before upload completes
Confirm it is a ZIP file and is smaller than your plan's maximum. Remove caches, local dependencies, media source files, or other content that is not needed at runtime.
Security inspection fails
Do not retry the same archive blindly. Scan the source locally, remove suspicious or unnecessary binaries, rebuild the ZIP from trusted source, and upload the clean artifact.
The deployment succeeds but the site shows 404 errors
Check that the configured build path contains the final entry file and assets. For client-side routers, make sure the application supports fallback routing where required.
Assets are missing
Inspect browser paths and letter casing. ZIP deployments run in a case-sensitive environment, so Logo.png and logo.png are different files.
A replacement still serves old output
Purge the build cache, upload the replacement again, and confirm the newest deployment is the active one.
CLI
Deploy an existing ZIP archive as a Drop with skytells drops deploy. The CLI streams the archive through the same validation and security pipeline and reports the accepted deployment in the terminal. See Deploy Drops with the CLI for command syntax, CI guidance, and examples.
Related
- Apps Overview — understand the architecture inherited by Drops.
- App Types — compare a Drop with standard apps, Compose apps, and App Catalog launches.
- Create an App — compare Git, Docker, Compose, Catalog, and Drop workflows.
- Workspace Resources — find this Drop among apps across all accessible projects.
- Workspace Deployments — find this Drop's deployments across the all-project timeline.
How is this guide?
Deploy on Skytells
Add a one-click Deploy on Skytells button to your README or documentation — let anyone deploy your project to Skytells in seconds.
Overview
Skytells managed databases run as containers inside your project's private network. They are internal-only by default and reachable by all apps in the same project without any configuration. You can expose a database to the internet when needed.