Vault
A closer look at the build.
A 6-character code instead of a meeting link, an install and a sign-up.
Explore the product- Product
- Vault
- Focus
- Screen and file sharing
- Explore this story
- The problem, the product & the details ↓
Sharing a screen or file without the ceremony
Showing someone your screen still means scheduling a call, sending a meeting link and hoping the other person's client works. Sending a file means an upload form, an account, or a chat app that compresses it. For a two-minute favour, that is a lot of ceremony.
A room, a code, a peer connection
Vault is the no-ceremony answer. Open the page, type a display name (it suggests a fun one), hit Share my screen, and you get a 6-character room code. Viewers join with the code and see the screen live: no plugins, no sign-up. The same page does file transfer with a 24-hour download link, and live chat with floating avatars on the stream.
The privacy posture is stated plainly on the landing page: direct WebRTC connection, P2P encrypted, nothing passes through servers.
What we saw in a room
We opened a share room ourselves. The room came up with its code, a share link, viewer count, reactions, chat and an end button, plus keyboard shortcuts for pointing, typing and emoji on the stream. The room we opened is closed now; the code in the screenshot is masked. One honest note: the site cold-starts on a first visit (we watched the service wake up), then it is fast.
When it is the right tool
It turns "let me show you" into a ten-second action. Support calls, quick design reviews, sending a file that is too big for chat: the common thread is zero setup on both sides.
Planning a similar build
Bring us the workflow you want to improve. Tell us who does the work today, which tools need to connect, and what your team needs to see in a first working version.
- Define the first useful workflow. Use Vault as a starting point. Choose the task your users need to complete and agree what a successful result looks like.
- Shape the screens around that task. Review a working prototype with your team. Decide what information each person needs, what they can change, and what happens when a step fails.
- Connect, test, then launch. Agree the data and integrations in scope. Test with representative examples on phones and desktops, then document how your team will run and maintain the product.
This is a proposed approach for a custom project, rather than a claim that every feature is included in the public demo.
About this case study
Hands-on: we opened a live share room on 9 November 2026. We did not stream an actual screen between two viewers, so picture quality and latency are untested.
Have a similar challenge?
Let’s build your solution.
Bring us the workflow you want to improve. Tell us who does the work today, which tools need to connect, and what your team needs to see in a first working version.