LessUp WebRTC is designed for people who want a small, readable codebase that still covers the core moving parts of real-time browser communication:

• WebSocket signaling with identity binding and room management
• peer-to-peer media and DataChannel chat
• screen sharing
• a framework-free frontend served directly by Go
• Docker-ready deployment and a public docs site

git clone https://github.com/LessUp/webrtc.git
cd webrtc
go run ./cmd/server

Open http://localhost:8080, join the same room in two browser windows, and start a call.

make check
cd web && npm test

docker build -f deploy/docker/Dockerfile -t webrtc .
docker run --rm -p 8080:8080 webrtc

Browser UI
 └─ web/src/core/app.js
 ├─ controllers/media.js
 ├─ controllers/peers.js
 ├─ controllers/signaling.js
 └─ controllers/ui.js
Go server
 ├─ cmd/server/main.go
 └─ internal/signal/

The server exposes:

• GET / — static frontend
• GET /config.js — runtime RTC config
• GET /healthz — health probe
• GET /ws — signaling socket

This repository uses OpenSpec as its only planning and requirements system.

• Main specs: openspec/specs/
• Active changes: openspec/changes/
• Public spec guide: docs/specs.md

Typical flow:

1. propose or update an OpenSpec change
2. implement against proposal.md, design.md, and tasks.md
3. validate with repo checks
4. review before merge

cmd/server/ application entrypoint
internal/signal/ signaling hub and tests
web/ static frontend
docs/ public documentation
openspec/ specs and change artifacts
deploy/ Docker, Caddy, and deployment assets

• Docs home
• Technical guide
• Signaling protocol
• Deployment guide
• API reference
• Troubleshooting

Start with CONTRIBUTING.md and the active OpenSpec change. This repo prefers focused, low-noise contributions that keep the implementation, docs, and repo metadata aligned.