Relayium CLI
Free peer-to-peer, end-to-end encrypted, self-hostable. In push/pull, send/receive, text and daemon-direct, your data goes straight between machines and never touches Relayium's servers — only a tiny rendezvous handshake does, and only for send/receive and text. The exception is cloud up/down, which stores your file end-to-end encrypted so another machine can fetch it later.
Install
- One command downloads a prebuilt binary for your OS and puts it on your PATH: curl -fsSL https://relayium.com/install.sh | sh
- Prefer to pick it yourself, or on Windows? Download a prebuilt binary from the releases page.
- Or build from source with Go.
- Then run relayium --help to see every command.
Which mode?
- push / pull — over your own SSH — Copy files to (or from) any machine you can already ssh into — a VPS, a home server, a workstation. Bytes travel over your SSH connection and never touch Relayium's servers; you need no account.
- send / receive — by pairing code — Send to another person across networks. After relayium login, run send with no code: the CLI mints a 6-digit pairing code, good for 5 minutes, and prints the command the other end runs — you pass that on out of band. The receiver needs no account. The connection is direct peer-to-peer: only a small rendezvous handshake passes through Relayium — the file bytes never do. Both terminals also print a 6-digit verification code (SAS) derived from their pinned TLS certificate fingerprints — a different value from the pairing code. Comparing it out of band is optional (add --verify to stop for it) and confirms the fingerprints were not substituted and that the rendezvous service did not impersonate either endpoint; it authenticates the endpoints, not every network hop, and only when someone actually compares it.
- text — ephemeral messages — Share a snippet, a link or a command instead of a file. One machine runs relayium text to mint a pairing code — that side needs relayium login — and the other joins with the printed relayium text CODE, which needs no login. Both ends stay online for the session: it is its own end-to-end encrypted peer-to-peer session, Relayium servers keep no message bodies and no server-side history — the machine on the other end can of course copy or keep what it receives — and one message is at most 65,536 bytes of UTF-8. Anything larger is a file.
- daemon direct — server to server — For two hosts you control that already know each other's address: one listens, the other pushes straight to it over pinned TLS 1.3. No relay, no SSH, no code — trust is public-key, set up once.
- sync — keep a folder mirrored — Incremental one-way folder mirroring instead of a one-shot copy, with optional --delete and --watch.
- up / down — the far end is offline — Upload now, pull it from another machine later. The file is end-to-end encrypted and the link is the same zero-knowledge link the browser app makes, so the CLI and the web app interoperate.
Integrity, resume and trust
Verified and resumable
Every file is verified end-to-end with SHA-256, and an interrupted transfer resumes from where it stopped on the next run (disable with --no-resume).
Identity files
Identity and trust live in ~/.config/relayium/ (override with --config-dir, e.g. /etc/relayium for a systemd service): this host's persistent key, the fingerprints of listeners you've pushed to (pinned after first use), and, on a listener, the pushers allowed to connect.
Frequently asked questions
Does the CLI cost anything?
No. push/pull, send/receive, text, daemon-direct and sync connect the two ends directly, so there is nothing to meter. Sending by pairing code needs an account so the server can mint the code — receiving never does — but it still costs nothing. Only cloud up/down draws on your account's storage and traffic allowance.
Which platforms does it run on?
macOS, Linux and Windows — a single static binary, installed by one command or downloaded from the releases page.
Can I point it at my own server?
Yes — --server https://your-domain points login, up, down, send and receive at a self-hosted Relayium instance, so pairing codes are minted by your server too.
CLI guides
Relayium home · Guides · Apps · Pricing · CLI · Device Inbox · Privacy · Terms · Security · Releases