← Orpheic

Run your own rendezvous

Orpheic ships with a meeting point of its own — but it is built so you never have to trust it. If you would rather trust no one, run your own.

What it is

The rendezvous is an introducer, nothing more. It helps your phone and your desktop find each other through the modern internet's walls — and once they have met, they speak directly, end to end. Only when no direct path can be made does the music pass through its relay, still encrypted between your two devices, so the relay cannot read it.

What it can see is only metadata: which keys are online, from which addresses, and when. That is unavoidable for any introducer — which is exactly why the option to make it yours matters. On your own machine, even that shadow is yours alone.

What you need

A small server with a public address. The cheapest VPS is plenty — introductions are a handful of bytes. Only the optional relay carries music, encrypted, and only when a direct path fails.
Python 3 with websockets and pynacl (both in a normal package manager).
Three ports open: 8750/tcp (control), 8751/tcp (relay, optional), 8752/udp (the address ear that makes hole-punching work).
Its address. A plain IP works fine (203.0.113.10:8750). A DNS name is nicer — its address can then change without re-pointing devices — but optional.

How it runs

The rendezvous is a single small Python file — asyncio, a WebSocket for registration, a blind TCP splice for the fallback relay, and a UDP ear for the punch. You run it under systemd and forget it; it holds no state on disk, no secrets, no keys.

Then, in Orpheic: Settings → Advanced → Rendezvous server, and enter your host:port. Your phone learns it the next time you connect at home. That is the whole switch.

The rendezvous is open source, under the MIT license: github.com/KalGeo/orpheic-rendezvous. Clone it, read the one file, run it. Questions: [email protected].