// the find
screego/server
screen sharing for developers https://screego.net/
Screego is a self-hosted screen sharing server built specifically for the code-sharing use case — low latency, high resolution, WebRTC under the hood with an integrated TURN server for NAT traversal. It's a Go binary or Docker container you run yourself, aimed at developers who've been burned by Teams or Zoom turning code into a blurry slideshow.
The integrated TURN server is the right call — most WebRTC self-host projects punt on NAT traversal and leave you debugging why it works on your LAN but nowhere else. The WebSocket event handling is split into discrete files per event type (event_create.go, event_join.go, etc.), which is clean and makes the signaling flow easy to follow. Single-binary distribution via goreleaser means actual zero-dependency deployment. Prometheus metrics are baked in, which matters if you're running this for a team and want to know when something breaks.
This is screen sharing only — no audio, no chat, no remote control. That's by design ('Nothing else (:') but it means you'll still be on a call in something else while using it, which is awkward. The UI is React/TypeScript embedded in the Go binary via go-embed; if you want to customize the frontend you're building the whole thing from source. Activity on the repo has slowed considerably — commits are sparse and the last meaningful feature work appears to be years old, so don't expect active development if you hit a WebRTC edge case. The auth story is basic: it's either 'no auth' or a global username/password list in config, with no per-room passwords or SSO.