Cloud storage decision
Transfer.zip
Self-hosting is practical—Transfer.zip publishes its web repository so a technical user can stand up the product themselves in about a day and maintain it for modest monthly hosting costs.
Visit website↗$9/mo
$108/yr
Read off the official pricing page.
$20one-off6 h to build
$30/mo6 h/mo upkeep
On cash alone, building overtakes the subscription at 4 seats.
Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Transfer.zip alternatives, with the arithmetic →
What a replacement has to do
- Self-host the Transfer.zip webapp and run your own instance that accepts uploads, stores files, issues download links, and optionally sends email notifications.
What it still won’t have
- Managed scaling, multi-region CDN and high-bandwidth hosting optimizations
- Vendor support, uptime guarantees and priority support tiers
- Automated backups & paid operational monitoring provided by the hosted service
- Convenient hosted billing, trials, and built-in analytics managed by the vendor
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 4 seats.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a self-hosted instance of Transfer.zip using Docker (Docker Compose) on a single VPS (Ubuntu 22.04). Stack: Docker, Docker Compose, Postgres, MinIO (S3-compatible) or real S3, Nginx reverse proxy with Certbot for TLS. In scope: clone https://github.com/robinkarlberg/transfer.zip-web, configure environment variables, provision Postgres and object storage, run database migrations, configure SMTP for outgoing emails, set up Nginx with TLS and a domain, enable basic daily backups of stored files and DB, add healthchecks and systemd or Docker restart policies. Out of scope: reimplementing features, training models, or building a global CDN. Deliverables must include startup scripts, a README with deployment steps, automated migration and backup scripts, CI checks that run basic tests, and error handling/logging for failed uploads and full-disk conditions.
How we checked
How the score was reached
- Self-host verdict base92
- An open-source build was found+5
- 4 cited sources+3
- Price verified on pricing page+3
- 2/2 assessment runs agreed+4
- Evidence score99
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 4
Every page the run actually retrieved.
- official productTransfer.zip — product page
- official pricingTransfer.zip — pricing
- open sourceErugoOSS/Erugo
- open sourcecloudreve/cloudreve
Integrity checks
What held up, and what did not.
