Meet in the browser Board and voice on one page
A temporary WebRTC room. Voice, camera, screen share, and a live board. Open the link and join. No signup. No download.
Start a room
The picture stays unclear because talk is not a drawing
When you describe architecture, flow, or UI out loud, people invent their own picture. Screenshots expire after the next edit. Split tools pull the diagram away from the talk.
You talked for minutes. They still cannot see it.
Service boundaries, call paths, and data flow stay fuzzy on a call. Point at one canvas, change the boxes, and the picture is shared. People who join late can read the board instead of guessing which box you mean.
You screenshot a diagram, then send it again after every change.
A diagram expires the moment it changes. Chats fill with versions and nobody knows which one is current. Edit the shared canvas. Everyone stays on this version. No more screenshot, resend, re-explain.
Talk, draw, and present live in different tools.
Switching apps breaks the rhythm. Drawing, talk, screen share, and a vote should stay on one page. Open the mic when you need to speak. Share a screen when you need to show. Do not stack tools first.
A short alignment still asks for signup and permissions.
A short session should not start with a team, an invite, and an approval. The space code is the door. Share it only with people you trust. Leave when the picture is enough.
Change one picture
Not a stack of screenshots, and not a slide each person watches alone. Boxes, arrows, and words stay on this page. Talk and present only when you need them.
Three steps to start
From this page to a live room, usually under a minute.
Open a room
Set a room id, or let the system assign one. A current browser is enough.
Send the id
They open the page, type the id, and join. Eight people at most.
Draw and talk
The board stays in sync. Open mic, camera, or share when needed. Export what you want to keep.
Where this fits
A small group is enough. Use another tool for all-hands, recording, or a long archive.
Architecture
Services, gateways, databases, and call paths sit on one diagram. Change the edges while you talk. Late arrivals can read the board.
Product brainstorm
Notes, sketches, and a vote stay on the same cloth. Write in parallel, then pick what is worth keeping.
Class and office hours
The teacher shares a screen. Students answer on the board. A timer and a random pick push the exercise. No class account.
Interview board
The candidate joins with a space code and draws the algorithm, the system, or the flow. No signup. No client to install.
Design and architecture review
Mark risks and change edges on one picture. Share a screen when the source lives in Figma or code. Write the decision back on the board.
Small workshop
Talk, exercise, a timed task, and a vote live in one space. Eight people or fewer. Export the board when you close.
Alone, or a few people
Local board
Draw on this device only. No sync. Think it through, then open a room.
A few people change one picture
Up to eight people. The board stays in sync. Voice, camera, and one screen share open on demand. Leave when it is enough. Export what you need to keep.
What this page is for
It is for finishing one picture in the session. It is not for all-hands, recordings, or a long archive.
Open a room now
Send them the id. Close it when you are done.
Start a room