About this project
TechToony Meeting Room is a small, browser-based video call for up to seven people. No accounts, no app installs, no plug-ins — open the page, send the link, and talk. It is built on WebRTC, the open standard for real-time audio and video already living in your browser.
Why it exists
Most video calls are routed through corporate cloud infrastructure: your camera feed travels to a remote data center, is decoded, re-encoded, mixed, and sent back out to everyone else. That is what makes a 200-person webinar possible, but it also means a third party sits between you and the people you are talking to, holding the decrypted picture.
For a handful of people, none of that is necessary. Browsers can talk straight to each other, with a server involved only for the introduction. The result is lower latency, better quality on a good connection, and a far simpler privacy story: there is no point in the path where your video exists in a form anyone could watch.
The project is a demonstration of how lean a modern video call can be — one static page, one small Node.js signaling server, and the WebRTC stack your browser already ships.
How it works, in plain English
- You open the page and press Start call. The server creates a random room ID and signs it, handing your browser two different links.
- The invite link is the one you send out. The host link is the signed one, and it stays with you — it is what proves you are the host.
- When someone opens the invite link they do not walk in. They knock, and you get a prompt showing their name, device, and rough location. Nobody joins until you say yes.
- Once admitted, the two browsers exchange a little network information — an "offer" and an "answer" — through the server.
- After that the audio and video go directly between the browsers. The server is no longer in the path.
Why seven people
There is no central server mixing the call, so every participant holds a separate connection to every other participant — a full mesh. In a seven-person call that means each person is uploading six copies of their own camera and downloading six streams, roughly 7.5 Mbps in each direction.
The cost per person grows with the size of the call, and it is the upload that runs out first: home connections are usually far faster downstream than up. Seven is a deliberate ceiling rather than a comfortable one. A good fixed line carries it; someone on mobile data, or sharing their screen to a full room, will feel it.
Past this the honest answer is a media server that mixes the call centrally — which is a different project with a different privacy story, so seven is where this one stops.
Hosts and guests
Only a host link opens a room. An invite link on its own cannot start a call: open one before the host has arrived and you are simply told the call has not started yet. This is deliberate — without it, whoever followed the invite first would own the room, and the person who created it would end up knocking at their own door.
A host admits or refuses each newcomer, and can end the call for everyone at once. If the host closes their tab without ending the call, the role passes automatically to whoever has been there longest, so the door still opens. That inherited role can admit people, but it cannot end the call for everybody — that stays with whoever actually holds the host link.
What it can do
- Camera and microphone calls for up to seven people
- Knock-and-admit entry — no uninvited arrivals, ever
- Screen sharing, one person at a time, with a click to take over
- Click any tile to enlarge it; shared screens can be zoomed and panned
- Mute, camera on/off, and camera switching mid-call
- A live level meter on each tile, so you can see who is talking
- A badge on each tile showing whether that connection is direct or relayed
- Renaming yourself mid-call
- Text chat, sent peer to peer like the video and kept nowhere after the call
- Optional room password on top of the link
- Media encrypted between participants, always, with no way to turn it off
What it does not do
- Calls larger than seven people
- Recording or saving anything
- Persistent rooms or scheduled meetings — a call that ends is gone, and its link will not reopen it
- File transfer
- Chat history — messages exist only while the call does, and someone who joins late sees none of what came before
- Dial-in by phone
- Push notifications — the other person has to be on the page
The technology
- WebRTC — the in-browser real-time media stack (VP8/VP9 video, Opus audio)
- Node.js — a WebSocket signaling server that handles rooms, knocks, and host keys
- HMAC-signed host links — the server recognises a host without storing anything about the room
- STUN servers, operated by Google, for finding a route through NAT
- A TURN relay as a fallback for networks that refuse to route a direct connection
- Self-hosted on a small Linux home server, behind a Let's Encrypt certificate
Contact
Questions, bug reports, or feedback: contact@techtoony.com.