pipe

Stream bytes straight from one machine to another over plain HTTP — netcat-over-HTTP. Pick any path (no creation step), have one side read and the other write; data flows live writer → reader. 1:1 rendezvous: exactly one reader and one writer per channel.

Use one end in this browser

Be one side here; run the other with curl on the far machine. Send a file or pasted text, or Receive whatever someone pushes (it’s saved straight to your downloads).

…or type text below

Both ends in the terminal

Pick a hard-to-guess path. Start the receiver first (or within the rendezvous window — either side may connect first):

# on the RECEIVING machine — waits for the sender, writes to disk
curl https://exl.ink/p/secret7 > out.tar.gz

# on the SENDING machine — pipe data into the same path
cat in.tar.gz | curl -T - https://exl.ink/p/secret7

Works for any stream — back up a database, move stdout between hosts, etc. GET https://exl.ink/api/pipe/new suggests a random path.

# receiver
curl https://exl.ink/p/db | psql mydb

# sender
pg_dump mydb | curl -T - https://exl.ink/p/db

How it behaves

Either side may connect first; whoever arrives waits up to 60s for the counterpart.
Strictly 1:1 — a second reader or writer on the same path gets 409 pipe busy.
If no counterpart shows up in time, the waiting side gets 504 and the channel is dropped.
Backpressure is honored: the sender pauses when the receiver reads slowly — nothing is buffered to disk.
1024MB max per transfer · 30-minute max duration · nothing is stored, bytes only pass through.