Deploy a ZIP archive
Upload local source code or a static site without connecting a Git repository. Infralane validates the archive and uses it as the application’s source.
Prepare the archive
Include your source and dependency manifests. For a plain static site, include index.html and its assets. Remove credentials, local .env files, private keys, dependency caches and unrelated files before packaging.
A single wrapper directory is detected automatically. The default limits are 100 MiB compressed, 1 GiB extracted and 10,000 entries; deployments can enforce lower configured limits. Invalid archives and unsafe paths are rejected.
Use an amd64 server for ZIP source builds. ARM servers require compatible prebuilt Docker images.
Select ZIP upload
Open Applications → Deploy application. Enter a permanent application name and choose ZIP upload under Deployment source.
Choose the archive and root
Select a nonempty .zip file. Use / for automatic wrapper-folder detection, or enter the application directory inside the archive.
Set the application type and runtime
Choose a web service, static site, background worker or TCP/UDP service. Select the runtime that matches your source. A plain HTML/CSS/JS site needs no build command; choose its publish directory instead.
Configure and review
Choose an active pool, CPU and memory. Add the required environment variables, volumes and networking settings. Review the filename, directory and configuration, then select Deploy application.
Check the release
Follow deployment output and verify the application. The archive filename identifies the selected upload; selecting a file alone does not deploy it.
Replace the source
Open Settings → Source and build and choose a new ZIP. Save the section to upload and deploy it. A failed save retains the selected file for retry. If an upload succeeded but application creation failed, the dashboard reuses that upload for the same project rather than transferring it again.
If creation saved the application but the initial deployment failed, open that application’s settings using the provided link. Do not create a second application to retry the same release.
Archive rejected or files missing
Check the displayed validation message, file size and archive structure. Confirm the configured root contains the dependency manifest or index.html. Remove unsafe paths and unnecessary files, then create a corrected ZIP.
For an agent-led transfer, use the separate MCP ZIP upload workflow. An agent cannot send a local filesystem path as source to the remote server.