LINUX PREVIEW · v0.2.8

Meet in
your shell.

Invite your agent. Or your person.
Ad-hoc shell access to the machine when you need it. No port forwarding. No infrastructure.

user@remote

user@remote:~$ curl -fsSL https://host.rdzv.sh | sh

Downloading Rendezvous 0.2.8…

Starting Tor…

Publishing invitation…

Invitation:

rv1.eyJvbmlvbiI6ICJnd2s3cHJjdG1lcXV...

Waiting for single-use connection.

Connected.

SSH over Tor
user@laptop

$ curl -fsSL https://join.rdzv.sh | sh

Downloading Rendezvous 0.2.8…

Invitation: rv1.eyJvbmlvbiI6ICJnd2s3cHJjdG1lcXV...

Connecting through Tor…

Connected.

user@remote:~$ ▍

How it works

01 / HOST

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.

02 / MEET

Your agent comes to you.

Send the invitation through a channel you trust. Your agent or collaborator joins using the same small CLI.

03 / FINISH

One connection. Then done.

The first authentication consumes the invitation. Disconnect or stop the host to end access. That invitation cannot connect again.

The website delivers
the tool. Not your shell.

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 model
Your hostPrivate onion service
TOR RELAYSEncrypted transport
Your agentOr another human

Temporary access.
On your terms.

Start a shell session for your agent or collaborator. Share the invitation, get to work, and end access when you're done.

Linux x86_64, ARM64, ARMv7 · glibc 2.34+.
Requirements and documentation

ON THE HOST YOU WANT TO SHARE
curl -fsSL https://host.rdzv.sh | sh
JOIN AS
curl -fsSL https://join.rdzv.sh | sh

Know what you're inviting.

Can someone reuse an invitation from my logs?

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.

Is this direct peer-to-peer?

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.

What can the invited agent do?

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.

What does Rendezvous cost?

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.