Lufi vs Send
A side-by-side comparison of two self-hosted file sync & storage options — licensing, setup difficulty, resource needs, and what each one replaces.
Not the right match-up?
Lufi
Let users fight uploads with client-side encryption
VS
Send
Encrypted file sharing fork of Firefox Send
| Feature | Lufi | Send |
|---|---|---|
| Category | File Sync & Storage | File Sync & Storage |
| License | AGPL-3.0 | MPL-2.0 |
| Language | Perl | JavaScript |
| Setup difficulty | Medium | Medium |
| Min. RAM | 128 MB | 256 MB |
| Deployment | docker, bare-metal | docker |
| GitHub stars | ★ 300 | ★ 5,847 |
| First released | 2015 | 2020 |
| Replaces | WeTransfer, Firefox Send | WeTransfer, Firefox Send |
Why pick each one
Choose Lufi if…
- Released under the AGPL-3.0 license
- First-class Docker support for quick deployment
- Written in Perl
- Tiny footprint — runs in 128 MB RAM
Choose Send if…
- Released under the MPL-2.0 license
- First-class Docker support for quick deployment
- Mature project with 5.8k GitHub stars
- Written in JavaScript
Frequently asked questions
Is Lufi or Send better?
Neither is universally better. Send has the larger community; both share a medium setup difficulty, so the decision comes down to features and licensing.
Are Lufi and Send free and open-source?
Yes. Lufi is licensed under AGPL-3.0 and Send under MPL-2.0. Both can be self-hosted at no software cost.
Can I run Lufi and Send with Docker?
Lufi: yes. Send: yes.