You make the invitation.
Run one command on the machine you want to share. Rendezvous starts a private onion service and a temporary SSH listener.
Invite your agent. Or your person.
One temporary connection to the machine you choose. No open ports. No bastion to babysit.
Your machine. Your invitation. Your call when it ends.
$ rdzv host
Starting private Tor service…
Your single-use invitation:
rv1.eyJ… [ share privately ]
Waiting for one connection▍
$ rdzv join
Invitation: rv1.eyJ…
Connected. Invitation consumed.
your-server $ ▍
A RENDEZVOUS, NOT A RESIDENCY
Run one command on the machine you want to share. Rendezvous starts a private onion service and a temporary SSH listener.
Send the invitation through a channel you trust. Your agent or collaborator joins using the same small CLI.
The first authentication consumes the invitation. Disconnect or stop the host to end access. That invitation cannot connect again.
INFRASTRUCTURE YOU DON'T HAVE TO RUN
Your terminal traffic travels through the Tor network with SSH authentication and a pinned host key. It never passes through a Rendezvous-hosted session server.
Understand the trust modelNo accounts. No public IP required. No third-party shell credentials.
ACCESS WHEN YOU NEED IT
Download a self-contained runtime into your home directory and invite your agent. No root access, system packages, or preinstalled Python or Tor.
Linux x86_64 · glibc 2.34+ · ordinary user account.
The installer needs curl, tar, and sha256sum. ARM and musl-based systems are not packaged in this release.
curl -fsSL https://host.rdzv.sh | shcurl -fsSL https://join.rdzv.sh | shAlready installed? rdzv host · rdzv join
Piping a script trusts this distribution endpoint. Prefer review first? Inspect the installer or install manually.
This is the provider deployment. These Cloudflare commands work independently of custom-domain activation.
NO HAND-WAVING
Not after it has been redeemed. Authentication consumes it once, and disconnect never reactivates it. Someone who steals an unused invitation can race the intended guest. Share it privately.
No. Tor relays carry the encrypted session. Neither endpoint needs an inbound port or NAT hairpinning. You depend on Tor's availability, and latency is higher than direct SSH.
It gets a shell as the account that launched the host. This is full account access, not a sandbox. Ending the session does not reverse file changes or reliably stop deliberately detached programs.
This is a working Linux preview, not an independently audited release. Real Tor connectivity and local replay/race tests pass. Read the source and verification notes before trusting it on important machines.
The current preview is free to download and use. There is no Rendezvous subscription or session relay bill. Tor infrastructure is operated by others; its capacity and availability are shared.
A TEMPORARY PLACE TO MEET