Onset
The desktop app for joining servers: voice, text, files and screen sharing, with signed in-app updates.
- Windows 10 or 11, 64-bit
- WebView2 (included with Windows 11)
- Microphone and headphones
Self-hosted voice for Windows
Group voice, text rooms and screen sharing that run on a PC you own. No accounts with us, no cloud in between. Just a slim strip on the edge of your screen.
There is no company in the middle. The app talks to one place: the server you were invited to. We don’t run relays. We don’t keep accounts. We never see your calls.
01The app
Onset isn’t another window to manage. It sits on the top or bottom edge of your screen, or floats wherever you drop it, and opens a panel only when you ask. Your call keeps going while you work, play or close it to the tray.
Echo cancellation, noise suppression, a speech gate and loss concealment. Set anyone’s volume, or mute them just for you.
History stays on the server. Replies, edits, @mentions, unread counts and search across messages and files.
Uploads pick up where they stopped, with inline image previews. The server owner sets the limits.
720p, 1080p or Source at up to 60 fps, with the shared app’s sound. Viewers can pop it out into picture-in-picture.
Global shortcuts for talk, mute and deafen work while another app has focus, including media keys.
Round-trip time sits on the strip. Jitter buffer depth and packet loss are one click away in the panel.
02Voice path
Voice runs on its own native audio engine, not in a browser tab. It travels over UDP on Onset’s own encrypted protocol, and the server relays each speaker separately. That’s what lets you set every voice’s volume on your side.
03Server identity
Every server mints its own identity the first time it starts. No domain name to buy, no certificate to renew, no port 80. The invite carries the identity’s fingerprint, and your app pins it on first connect.
203.0.113.42:8080#
This invite is an example. Real ones come from the server owner’s control panel.
04Screen sharing
Pick a window or a whole screen in the Windows picker. When you share a window, only that app’s sound comes along. When you share a screen, Onset leaves its own audio out, so nobody hears themselves back.
Encrypted with DTLS-SRTP and forwarded by your server. Nothing goes through us.
05Host it yourself
Onset Host runs on any Windows PC. A local control panel in your browser handles everything: starting and stopping, LAN or internet mode, invites, registration, backups and logs.
Run the Onset Host installer. A shortcut opens the control panel at 127.0.0.1:9090, on your PC only.
Internet mode finds your public IPv4 address and opens the ports on your router with UPnP. Routers without it can be set up by hand.
Copy the invite and send it to your friends. They paste it into the app, and that’s it.
Defaults. You choose the ports in the panel.
Scheduled, encrypted archives taken from a live snapshot. Calls keep running.
If the server process stops unexpectedly, the panel restarts it with a growing delay.
Closed, invite-token or open registration. Roles, kicks, bans and a moderation log.
Messages and files live in SQLite on that PC. Retention is unlimited unless you set it.
06Download
Both installers are published on GitHub Releases, each with a SHA256SUMS file so you can check what you downloaded.
The desktop app for joining servers: voice, text, files and screen sharing, with signed in-app updates.
The server and its local control panel, in one installer. Run it on a PC that stays on while people talk.
About the Windows warning. The installers aren’t signed with a paid code-signing certificate, so SmartScreen may say Windows protected your PC. Check the file against SHA256SUMS, then choose More info → Run anyway.
07Questions
Yes, this version is. There’s nothing to buy and no subscription, and you run the server on your own PC, so there’s no hosting bill from us either. Later versions may be offered under different terms; what you’ve downloaded stays under the license it came with.
No, and we’d rather say so plainly. Traffic is encrypted between each app and the server: TLS for control, ChaCha20-Poly1305 for voice, DTLS-SRTP for screen sharing. The server stores messages and files and re-seals voice for each listener, so whoever runs it can technically access them. Join servers run by people you trust.
A public IPv4 address and a router that forwards one TCP port and two UDP ports. The control panel opens them for you with UPnP; otherwise you forward them by hand. On a local network you need neither.
Not directly. Behind carrier-grade NAT nobody outside can reach your PC, so internet mode needs a public address. LAN mode works as usual.
Not today. Both the app and the server are built for Windows 10 and 11, 64-bit.
No. The app talks only to the servers you add, and to GitHub when it checks for updates. Call statistics (packet counts, buffer depth, loss) go to the server you’re connected to, never to us, and the owner can turn them off. Audio, video, messages and file names are never included.
The app checks GitHub shortly after it starts and offers a one-click restart. Every package is checked against the signing key built into the app before it’s installed. The app and the server speak one protocol, and it hasn’t changed across 1.x, so an updated app and a server you haven’t updated yet still work together.