When is dlvr.sh a better Wormhole alternative?
dlvr.sh is a stronger fit when the job is temporary delivery of builds, logs, installers, or support artifacts and you want expiry, passwords, download limits, and an API-friendly workflow in one place.
Alternatives
Wormhole alternative
A Wormhole alternative for shipping real developer artifacts.
Wormhole is great when browser-native privacy and quick person-to-person sharing are the priority. dlvr.sh is better when you need repeatable artifact delivery with links you can hand to QA, support, or customers.
Best for
Teams sending build artifacts, installers, debug bundles, and release candidates instead of one-off personal transfers.
dlvr.sh
Temporary delivery with expiry, passwords, download caps, short links, and a public API surface built around software handoff.
Wormhole
Simple private sharing with an emphasis on lightweight browser transfer and end-to-end privacy.
Workflow fit
Step 1
Upload a build or log bundle.
Step 2
Set expiry and optional password.
Step 3
Share one stable short link with QA or a customer.
Step 4
Let the link expire instead of manually cleaning it up.
Developer comparison
| Area | dlvr.sh | Wormhole |
|---|---|---|
| Developer artifact delivery | Built around temporary software handoff and share links. | Better aligned with quick secure transfers between people. |
| Expiry and download controls | Native expiry, passwords, and max-download limits. | Expiry exists, but the workflow is less centered on software-release handoff. |
| API and CLI path | Public REST API and repo-shipped CLI. | Product focus is simpler browser sharing. |
FAQ
Does dlvr.sh try to replace Wormhole for every use case?
No. Wormhole may still be the better choice for its strongest native workflow. dlvr.sh is deliberately narrower: short-lived delivery for developers who need less ceremony and more control.
What are the current dlvr.sh limits?
The current product supports temporary delivery up to 2 GiB per file, with short links, expiry controls, optional passwords, and optional download limits.
Next step
Need a simpler path for temporary artifact delivery?
If your job is moving builds, installers, QA archives, logs, or support bundles, start with dlvr.sh’s software-distribution workflow and keep the handoff intentionally temporary.