015

Open-source temporary file sharing, honestly reviewed. No marketing fluff, just what you get when you self-host it.

TL;DR

• What it is: A self-hosted temporary file sharing platform — think WeTransfer, but running on your own server, with AGPL-3.0 licensing and no per-transfer fees [README].
• Who it’s for: Developers or small teams who need a clean, self-hosted alternative to disposable file-transfer SaaS. Currently skews toward a Chinese-speaking audience given its documentation and demo server origin [README][website].
• Cost savings: WeTransfer Pro runs ~$16/mo; similar tools on enterprise plans run $30–100/mo. 015 runs free on any VPS that can handle Docker and Redis.
• Key strength: Genuinely good engineering for a small project — chunked uploads, hash-based instant transfer (deduplication), JWT download tokens, pickup codes, and a Redis-backed async task queue are not features you expect from a 330-star project [README].
• Key weakness: No third-party reviews exist. No community discussion visible in English-speaking circles. AGPL-3.0 creates commercial use restrictions. The project’s demo server and documentation hint at a Chinese-origin solo/small-team project at an early stage of international adoption [README][website].

---

What is 015

015 (pronounced “zero-one-five”) is a self-hosted temporary file and text sharing platform. The name is a reference to Ichigo, a character from the anime DARLING in the FRANXX — which tells you something about the author’s communication style and target demographic [README].

The pitch is straightforward: upload a file or paste text, get a sharing link, the recipient downloads it, optionally it expires or is deleted after N downloads. That core loop is well-trodden territory — Plik, FileShelter, Pingvin Share, and a dozen others do it. What makes 015 technically distinct is the engineering depth underneath that simple surface.

The frontend is Vue 3 + Nuxt 3 + TypeScript + Tailwind CSS v4, which is a modern, defensible stack. The backend is Go with the Echo HTTP framework — also a reasonable choice for a file handling service that needs to be fast under concurrent load. The async processing system uses Redis + Asynq (a Go-native distributed task queue), which is not something you typically see in hobby projects [README]. Upload state is tracked via Redis, file hashes are calculated in the browser via Web Workers to keep the main thread free, and download tokens are issued as JWTs rather than bare links — meaning you can revoke access without deleting files [README].

As of this review, 015 has 330 GitHub stars. That’s a project people have noticed, not a project people have shipped to production at scale.

---

Why people choose it

There are no third-party reviews of 015 available — no Trustpilot entries, no blog posts from sysadmins who deployed it, no Reddit threads. This is a real data gap, not an editorial omission. The search landscape for “015 file sharing” is noise [search results].

What the GitHub activity and feature set suggest is that 015 is chosen by developers who want:

1. A complete, modern stack they can read and understand. Go + Vue 3 is approachable. The project structure is clean. Someone deploying this can audit what it does.
2. More engineering than similar tools. Chunked uploads with resume support, instant transfer via hash matching, and a proper async queue for image processing put this ahead of simpler alternatives like FileShelter or Lufi in raw feature count.
3. No per-transfer limits or account requirements. The website description explicitly says “No registration required” [website]. You get a link, they download it, done.

What it is not chosen for is stability guarantees, a large community, or production battle-testing. The evidence for any of those doesn’t exist yet.

---

Features

Based on the README, which is the most reliable source available:

Core upload flow:

• Chunked file uploads for large files [README]
• Frontend file hash calculation via Web Worker — enables instant transfer (if the same file was uploaded before, the server skips storing a duplicate and returns the existing link immediately) [README]
• Resume upload — if a chunked upload is interrupted, it picks up where it left off [README]
• Text sharing alongside file sharing [README]
• Real-time upload progress display [README]

Sharing controls:

• Password protection on shared links [README]
• Download count limits — link auto-expires after N downloads [README]
• Expiration time settings [README]
• Pickup code system — instead of a long URL, recipients can enter a short code [README]
• JWT-based download tokens — download URLs are signed and time-limited [README]

File processing:

• Image compression (automatic, multiple formats) [README]
• File preview for images, videos, audio, and documents [README]
• Image format conversion [README]
• Async processing via Redis + Asynq queue [README]

Infrastructure:

• Full Chinese and English internationalization [README]
• Responsive UI (Tailwind v4 + Reka UI) [README]
• Docker Compose deployment [README]
• Local filesystem storage (no external object store required) [README]

What’s notably absent:

• S3 or object storage backend option — it writes to local disk, which limits horizontal scaling
• Admin dashboard or management UI visible in the README
• User accounts or quotas (it’s designed to be anonymous and ephemeral)
• Audit logs
• Virus scanning on uploads

---

Pricing: SaaS vs self-hosted math

015 has no commercial tier. It’s AGPL-3.0 software you deploy yourself. The cost structure is purely operational:

Option	Monthly cost	Limits
015 self-hosted (Hetzner CX22)	~€4–6/mo	Disk space only
WeTransfer Free	$0	2 GB per transfer, branded
WeTransfer Pro	~$16/mo	200 GB storage, no ads
Filemail Business	~$20/mo	1 TB, email delivery
Smash Pro	~$6/mo	250 GB/mo, 5 GB per file

The math for a team regularly sharing large files is not complicated: a $5 VPS and 015 beats $16–$20/mo SaaS after one month. The catch is operational overhead — you maintain the server, handle disk full situations, and apply security updates.

One cost note: AGPL-3.0 matters if you’re thinking commercially. If you embed 015 into a product or service, AGPL requires you to open-source your application too. For internal use, that’s irrelevant. For anyone building a file sharing feature into a commercial app, it’s a blocker — you’d need to use an MIT or Apache 2.0 alternative instead.

---

Deployment reality check

The README’s install path is Docker Compose with a config YAML file. The steps are:

1. Download config.example.yaml and docker-compose.yml
2. Edit config.example.yaml with your settings, rename it to config.yaml
3. Run docker compose up -d

What you actually need:

• A Linux VPS with at least 1–2 GB RAM (Redis + Go backend + Nuxt SSR adds up)
• Docker and docker-compose
• Enough disk for whatever files you plan to store
• A reverse proxy (Caddy or nginx) for HTTPS — not bundled
• A domain name if you want clean sharing links

What can go sideways:

• The demo server at send.fudaoyuan.icu is a community instance, not an official managed product. Its uptime and data retention policies are unknown [website].
• Local filesystem storage means if your disk fills up, uploads fail. No graceful quota handling is documented.
• With 330 stars and no visible community forum or Discord, support means reading the source code or opening a GitHub issue. Response time is unknown.
• The project documentation is primarily in Chinese; the English README is a translation, and not every edge case is explained in detail [README].
• AGPL license compliance — if you’re deploying this for clients as part of a service business, get a lawyer’s opinion on what “network use” triggers the AGPL copyleft clause.

Realistic time to a working instance for someone comfortable with Docker: 30–45 minutes on a fresh VPS. For someone who’s never touched Docker or a reverse proxy, budget an afternoon.

---

Pros and cons

Pros

• Modern, auditable stack. Vue 3 + Go + TypeScript + Redis is not a cobbled-together mess. The code appears readable and intentionally structured [README].
• Instant transfer via hash deduplication. This is genuinely useful and not a feature you find in most small file sharing projects. If someone uploads the same file twice, the second upload is instant [README].
• Pickup code system. Simpler than sharing a long URL with someone over a phone call or chat. Small UX detail, but practical [README].
• JWT download tokens. Links aren’t just bare file paths — they’re signed and can be invalidated without touching the file [README].
• No registration, no tracking in the sharing flow. Anonymous by design [website].
• Resume upload. Matters when uploading large files on flaky connections [README].
• Docker Compose install. Deployment is not painful [README].

Cons

• No production track record. 330 GitHub stars, no third-party reviews, no public case studies. You’re in early adopter territory.
• AGPL-3.0 license. Restrictive for commercial embedding. MIT-licensed alternatives exist (Pingvin Share is MIT, for example).
• Local filesystem only. No S3 backend means you can’t scale horizontally or use cheap object storage for large file volumes.
• Chinese-origin project with thin English community. Issues and discussions may be primarily in Chinese. This is not a quality judgment — the code is good — but it matters for support expectations.
• No admin UI documented. File lifecycle management via a web interface isn’t clearly described. It’s unclear how an admin would view or delete files outside of direct filesystem access.
• No virus scanning. Uploading untrusted files from external users to your server without scanning is a risk depending on your deployment context.
• Small team or solo project. Bus factor is unknown. If the maintainer stops developing it, there’s no large community to fork and continue.

---

Who should use this / who shouldn’t

Use 015 if:

• You’re a developer who wants a modern, self-hosted WeTransfer alternative and can evaluate Go/Vue source code yourself.
• You have internal file sharing needs — team members sending each other large files — where AGPL compliance is not a concern.
• You want chunked uploads and instant transfer without paying per-GB fees.
• You’re comfortable being an early adopter and can tolerate rough edges or sparse documentation.

Skip it (for now) if:

• You need production stability guarantees or a large support community.
• You’re building a commercial service that embeds file sharing — AGPL blocks this path.
• You need S3 backend, horizontal scaling, or multi-region redundancy.
• You need English-language documentation for your team.

Skip it (pick Pingvin Share) if:

• You want a more established self-hosted file sharing tool with a larger community, English-first documentation, and MIT license. Pingvin Share covers the same basic use case with more public track record.

Skip it (pick Nextcloud) if:

• You need file sharing as part of a broader collaboration suite — calendars, contacts, document editing — rather than a standalone ephemeral sharing tool.

---

Alternatives worth considering

• Pingvin Share — The most direct comparable. MIT-licensed, English-first, larger community, fewer advanced features (no hash-based instant transfer), simpler stack.
• Plik — Older, minimal Go-based file dropper. No chunked upload or instant transfer. MIT license. Very stable.
• FileShelter — Even simpler, C++ based. Smaller feature set. If you just want “upload file, get link, it expires” with minimal operational overhead.
• Lufi — Perl-based, end-to-end encrypted in-browser. Different threat model — useful if you need E2E encryption, not just link-based access control.
• WeTransfer — SaaS, no ops, 2 GB free. The correct choice if you share files occasionally and don’t want to run a server.
• Nextcloud + sharing — If you already have Nextcloud, its built-in share links and expiration features cover 80% of what 015 does without adding another service.

---

Bottom line

015 is a well-engineered small project that punches above its weight technically. Hash-based instant transfer, JWT download tokens, Redis-backed async queues, and a resume-capable chunked uploader are not features you expect from a 330-star repo with no review coverage. If you’re a developer who reads source code before deploying software, the code is worth reading.

The honest caveat is that everything beyond the engineering is unknown. There’s no community to ask when things break, no English-language production deployments to learn from, and no commercial entity behind it ensuring long-term maintenance. For internal tooling where you have the technical capacity to maintain it yourself, that’s acceptable. For anything customer-facing or compliance-sensitive, the lack of track record is a real risk — and Pingvin Share or a commercial option would be the safer bet.

If you want to get something like this deployed without becoming its sysadmin, that’s exactly the kind of one-time setup that upready.dev handles for clients.

---

Sources

1. 015 GitHub Repository and README — github.com — https://github.com/keven1024/015
2. 015 Official Website / Demo Instance — send.fudaoyuan.icu — https://send.fudaoyuan.icu

Note: No third-party reviews, blog posts, or community discussions about 015 the file sharing platform were found at the time of this review. All feature claims are sourced directly from the project README and website metadata. Pricing comparisons for alternative SaaS products use publicly available information.