Analysis updated 2026-07-05 · repo last pushed 2025-10-26
Share a quarterly report with your team using a custom, password-protected link that expires automatically.
Automate file uploads from another application using the built-in API.
Send a large file to a client with a memorable link like your-site.com/project-file.
Host a private alternative to Dropbox or WeTransfer links for your small team.
| yorukot/sharing | danterolle/loqi | iwetan77/flume | |
|---|---|---|---|
| Stars | 2 | 2 | 2 |
| Language | Go | Go | Go |
| Last pushed | 2025-10-26 | — | — |
| Maintenance | Quiet | — | — |
| Setup difficulty | moderate | moderate | moderate |
| Complexity | 3/5 | 2/5 | 4/5 |
| Audience | pm founder | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires setting up a reverse proxy like Nginx with HTTPS for production use.
Sharing is a lightweight file-sharing service you can host yourself. It lets you upload a file and get back a short, memorable link (like your-site.com/my-document) that you can send to anyone. Recipients visit the link and the file downloads immediately, no landing pages, no sign-up walls, just the file. You can optionally add a password, set an expiration date, or choose a custom short link (called a "slug") when uploading. If a file is password-protected, the recipient sees a simple password prompt before the download starts. Expired files are automatically cleaned up by a background job that runs hourly. There are two ways to use it: through a web interface or through an API. The web UI requires you to log in with a single API key, and from there you can upload files, manage existing ones, and copy share links. The API lets you do the same things programmatically, useful if you want to build file sharing into another app or automate uploads. All management actions require that API key, only the public share links work without authentication. This is a good fit for a founder or small team that wants a private, self-hosted alternative to Dropbox or WeTransfer links. For example, you could share a quarterly report with a specific team using a link like share.example.com/q4-report, protected by a password, expiring at year-end. It's not designed for large-scale public services, there's no multi-user system or account management, just one API key controlling everything. The project is built in Go and uses SQLite for storage, which means it runs as a single small application with no external database to manage. Files are stored on the local filesystem. The README recommends placing it behind a reverse proxy like Nginx with HTTPS for production use.
A lightweight, self-hosted file-sharing service. Upload files and get short, memorable links to share with anyone, with optional passwords and expiration dates.
Mainly Go. The stack also includes Go, SQLite.
Quiet — no commits in 6-12 months (last push 2025-10-26).
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly pm founder.
This repo across BitVibe Labs
Verify against the repo before relying on details.