Self-hosting
Self-hosting
Run the coordinator and relay yourself.
The service does two jobs: it introduces your computers to each other, and it passes packets when they cannot reach each other directly. Both are small services you can run.
Free for personal use. A licence for business use.
What you get
- Nothing leaves your network. Introductions and relayed traffic stay inside.
- Your records are yours. Computer names, sessions and timings live in your database.
- The same apps, pointed at your setup.
What does not change
Session content was already locked between your two computers. Self-hosting does not make the picture safer. It changes who runs the service and who holds the records.
Who it is for
- Studios and firms whose content contractually cannot leave the building.
- Networks where the hosted service is blocked by policy.
- People who would rather run it.
If none of that is you, the hosted service is less work and looks identical.
What you would run
| Piece | Job | Size |
|---|---|---|
| Coordinator | Accounts, computer list, introductions | Small. One modest VM. |
| Relay | Passes locked data when direct fails | Depends on how much gets relayed |
| Database | Records | Postgres |
Relay bandwidth is the only part with real cost.