This is an automated archive made by the Lemmit Bot.
The original was posted on /r/selfhosted by /u/void_222 on 2025-01-29 19:38:42+00:00.
Hi everyone, it’s been a while! I shared Whoogle Search with the community a few years ago and was really grateful for everyone’s feedback and support.
I have a new project that I wanted to share called YeetFile: . It’s a file sending + file/password vault service that uses zero-knowledge encryption and is designed to be easily self-hosted.
Here is a quick rundown of some features:
- No file size limitation for sending
- Ability to set file expiration after a number of downloads or time limit
- File links don’t require an account to open
- Full vault for storing files (and passwords/logins) long term
- File and folder sharing from vault with other YeetFile users
- Zero knowledge encryption for all uploads (server never receives any unencrypted content, and is unable to decrypt uploads)
- Anonymous account creation (email is optional)
And here are some features specifically for self-hosting that can be helpful:
- Simple Docker-based deployment
- Server-specific passwords
- Ability to set max users per server
- Ability to set max user vault size and/or sending bandwidth
- Easily customized and configured further using environment variables (see readme)
- Configurable storage backend (currently either local storage or Backblaze B2)
One other nice feature is that aside from a web interface, YeetFile has a full featured CLI/TUI tool that allows access to all of the same features available on the web version. So if you prefer using a terminal for file-related activities or for security reasons, you can use YeetFile via the CLI and never have to log into your account from a browser.
While a primary goal has been ensuring the ease of self-hosting, there’s an official instance at if you want to use that as well or just want to try it out.
Other helpful links:
- FAQ:
- Security overview:
- GitHub:
Thanks for reading! I’m happy to answer any questions!