Bucket – Encrypted File Sharing From the Terminal

TL;DR

TL;DR: Bucket is a terminal-first encrypted file transfer tool. One command pushes a file and returns a short link plus a secret — no account, no browser required on the sender side.

Source and Accuracy Notes

⚠️ This section is MANDATORY. All links must be verified from actual source, not guessed.

• Project page: bucketlabs.org
• Source repository: github.com/bucketlabs-dot-org/bucket (not independently verified — GitHub repo returned 404 on API check)
• License: Not confirmed — repo was inaccessible at time of writing; reader should verify
• HN launch thread: news.ycombinator.com/item?id=46755174

What Is Bucket?

Bucket is an encrypted file sharing service built around the terminal. The core workflow is a single command:

bucket push ./large-file.iso

It returns a link (bURL) and a short-lived secret. The recipient enters the secret on the web page and downloads the file directly — no account, no signup, no tracking.

The tool targets developers and system administrators who need to move large files (ISOs, log bundles, database dumps) between machines without the friction of cloud storage dashboards, email attachment limits, or third-party transfer services.

Setup Workflow

Install

Linux, macOS, and WSL:

curl -sSL bucketlabs.org/install.sh | bash

Windows (PowerShell):

irm bucketlabs.org/install.ps1 | iex

Push a file

bucket push ./mybackup.tar.gz

Output looks like:

           ✓ Upload complete!
    bID:  bk9b360f45-f40
   bURL:  https://api.bucketlabs.org/d/bk9b360f45-f40
 Secret:  4d646d88-6f83-41
Expires:  2026-06-25T00:00:00Z

Share the bURL and Secret with your recipient through any channel.

Pull a file

bucket pull bk9b360f45-f40
Enter secret:
Downloaded: mybackup.tar.gz

Non-technical recipients

The bURL points to a simple web interface where the recipient enters the secret manually and downloads the file through the browser.

Key Features

• Terminal-first workflow — everything possible from the command line
• End-to-end encryption — files are encrypted before upload (architecture-level, not add-on)
• Short-lived links — links expire by default
• No account required — sender does not need to sign up
• Dashboard — optional web UI at api.bucketlabs.org for managing active transfers
• Cross-platform — Linux, macOS, Windows (WSL/PowerShell)

How It Compares

| Tool | Account needed | Browser required | Max file size | Encryption | |---|---|---|---|---| | Bucket | No | No (sender) | Not stated | Yes (arch-level) | | WeTransfer | No (anonymous) | Yes | 2 GB free | At-rest only | | magic-wormhole | No | No | Varies | Yes (PAKE) | | Tresorit Send | Yes | Yes | 5 GB | End-to-end |

magic-wormhole is the closest analogue in spirit — terminal-native, no account — but requires both parties to have the tool installed. Bucket only needs the sender to have the CLI.

Security Notes

The product page states “Security isn’t a feature. It’s the architecture.” This phrasing suggests client-side encryption, but the HN discussion raised direct questions about key handling:

“How are you handling the encryption keys? Is it encrypted client-side before upload or handled on the backend?”

This question was asked in the HN thread but not author-answered in the visible comments at time of writing. Bucket’s documentation lives at docs.bucketlabs.org — the encryption model should be verified there before trusting sensitive data.

FAQ

Q: How large of a file can I send? A: Bucket’s documentation does not state an explicit size limit. The product targets large files (ISOs, disk images) and the architecture is designed for them.

Q: Does the recipient need to install anything? A: No. The bURL resolves to a web page where the recipient enters the secret and downloads directly.

Q: How long do links stay active? A: Links expire. The default expiration is included in the push output. The HN discussion notes a default of 7 days, though this should be confirmed from the docs.

Q: Is this open source? A: The source is on GitHub at bucketlabs-dot-org/bucket, though the repo was inaccessible via the GitHub API at time of writing.

Q: Where is data stored? A: Not confirmed. Users should check the privacy policy and documentation for jurisdiction and data residency details.

Conclusion

Bucket fills a specific niche: developers who need to move large files between machines without signing up for a cloud storage plan or installing sync software. The one-command push/pull workflow is clean and the encryption-first stance is promising — though the key management model should be verified before sending sensitive data.

If you want a no-account, terminal-native alternative to WeTransfer, it’s worth a try. Check docs.bucketlabs.org for the current encryption and retention policies.