Send files and messages straight to another device. No servers, no accounts, no setup.
$ beemr share vacation-photos/
Sharing "vacation-photos" (214 files, 1.3 GB)
Who can download: anyone with the command below
Downloads allowed: 1
Expires: never
On the other device, run:
beemr get AlTRKOzvjlzG5IBDDhhzcwj56mci3evFmCm22FhZ8NVAOe29ocweZCkDP1kmbFeakaMFBMCoARc
Waiting for the other device… (Ctrl+C to stop sharing)
✓ Reachable on your local network
✓ Hole punching ready (through firewalls, no setup needed)On the other device:
$ beemr get AlTRKOzvjlzG5IBDDhhzcwj56mci3evFmCm22FhZ8NVAOe29ocweZCkDP1kmbFeakaMFBMCoARc
Connecting…
Receiving "vacation-photos" (214 files, 1.3 GB) from Osman
via direct connection (through the firewall via hole punching)
Receiving [========================] 100.0% 1.3 GB / 1.3 GB 48.2 MB/s
Saved to ./vacation-photosMessages:
$ beemr msg sara "landed! call you later"
Sending to Sara…
Delivered (direct connection).
$ beemr inbox
Inbox: 1 message, 1 new
● 1 Sara · 2 min ago
welcome home 🎉
Reply with: beemr reply <number> <message>- Works across the internet with zero configuration. beemr connects directly when it can, punches through home and mobile NATs when it can't, and falls back to relaying through other beemr devices.
- No servers. Devices find each other through the BitTorrent DHT and connect peer to peer. Nothing is uploaded anywhere.
- End-to-end encrypted. Every byte is encrypted between the two devices, even when it passes through a relay.
- Device identities and names. Each device has a cryptographic ID and a name
you choose. Share with
--to saraand only Sara's device can download. - Limits. One download by default, or
-n 5. Expires after-e 10m. - Messages and an inbox that show names, not IDs.
- One small native binary (about 9 MB) for macOS, Linux and Windows.
One command. It downloads the right binary, verifies its checksum, names your device and starts the background service.
macOS and Linux
curl -fsSL https://raw.githubusercontent.com/osmanahmadxai/beemr/main/install.sh | shWindows (PowerShell)
irm https://raw.githubusercontent.com/osmanahmadxai/beemr/main/install.ps1 | iexNothing else is required: no Docker, no runtime, no account.
beemr share report.pdf # anyone with the printed command can download it once
beemr share photos/ -n 3 -e 2h # a folder, up to 3 downloads within 2 hours
beemr share contract.pdf --to sara # only Sara's device can download it
beemr get <ticket> # download, into the current folder
beemr get <ticket> -o ~/Downloadsbeemr id # your device ID: give it to people who want to reach you
beemr contact add Sara <her-device-id> # save a device under a name
beemr msg sara "are you free tonight?"
beemr inbox # read messages (unknown senders are clearly marked)
beemr reply 1 "yes, 8pm"If the other device is offline, the message is queued and delivered
automatically when you're both online. Messages arrive through the background
service that beemr setup starts. Check it with beemr daemon status.
beemr setup # name this device and start the background service
beemr name "Osman's Mac" # rename this device
beemr doctor # how reachable is this device, and whybeemr tries every path at once and keeps the best:
| Step | What happens | Needs |
|---|---|---|
| 1. Direct | LAN, IPv6, or a port your router opens via UPnP | nothing |
| 2. Hole punching | Both devices connect at the same moment through their firewalls, coordinated through a public relay | nothing |
| 3. beemr relay | Another beemr device that is reachable from the internet forwards the encrypted data | at least one reachable beemr device online |
Hole punching works on most home and mobile networks. When both devices sit behind the strictest kind of NAT (symmetric NAT, common on some carriers), some reachable third machine has to forward the traffic. No app can avoid that. beemr makes that machine another beemr user, never a company server. Any beemr device that is reachable from the internet (a router with UPnP, IPv6, a public IP) relays automatically while its background service runs. You can also run a dedicated relay on any machine:
beemr relay # relay for everyone (listed on the DHT)
beemr relay --private # relay only for devices you configure
beemr relay use <address> # use a specific relayRun beemr doctor to see which steps work on your network.
- Encryption. Connections use libp2p's Noise protocol (X25519 and ChaCha20-Poly1305) or TLS 1.3 over QUIC, end to end, including through relays.
- Identity. Each device proves its identity by signing the specific connection with its Ed25519 device key, so neither a relay nor anyone in the middle can impersonate it.
- Tickets. A ticket contains a one-time secret. Without it, a share can't be found or downloaded.
- Safe receiving. Received files land in a hidden staging folder and are moved into place only when complete. Existing files are never overwritten, and paths are checked so nothing can be written outside the download folder.
- Names are self-chosen. Unless you've saved a device as a contact, its name is shown as unverified.
beemr stores its identity, contacts and inbox in ~/.config/beemr/
(Linux), ~/Library/Application Support/beemr/ (macOS) or
%APPDATA%\beemr\ (Windows). Set BEEMR_HOME to use another folder.
The wire format is specified in PROTOCOL.md.
Needs Rust 1.89 or newer.
cargo build --release # binary in target/release/beemr
cargo test # unit tests + end-to-end tests (no internet needed)
cargo clippy --all-targets -- -D warningstests/docs-smoke.sh runs every command in this README against a real build,
as several devices on one machine (86 checks). tests/natlab/run.sh builds two
simulated home networks behind real Linux NAT routers in Docker and checks
hole punching, the relay fallback through symmetric NATs, and the error shown
when no relay exists. CI runs all of these on every push.
For troubleshooting, BEEMR_LOG=debug beemr … prints detailed network logs.
| Module | Responsibility |
|---|---|
main.rs |
Command-line interface |
node.rs |
libp2p node: QUIC/TCP, Noise, UPnP, AutoNAT, relays, hole punching |
connect.rs |
The connection ladder: direct → hole punching → relay |
discovery.rs |
Signed address records on the Mainline DHT |
proto.rs |
The beemr stream protocol |
share.rs / get.rs |
Sending and receiving files |
message.rs / daemon.rs |
Messages, inbox and the background service |
service.rs |
Starting at login on macOS, Linux and Windows |
relay.rs / doctor.rs |
Dedicated relays and connectivity diagnostics |
MIT