# Share a v0 build with a client, and see what they did

- URL: https://getroomi.com/share/v0
- Sources checked: 7 October 2026
- Built: 2026-10-13

You built it with v0. Now let a client try it, and see what they did. Roomi gives each client a link of their own, with nothing to sign up for, and records what each one did.

## What sharing from v0 gives you today

Each line about v0 is from its maker’s own pages, read on 7 October 2026. Each source is listed at the foot of the page.

|  | v0 | Roomi (ours) |
|---|---|---|
| Who can open the published app | Partly: v0 publishes a project to Vercel. Who can open the deployed app depends on your Vercel plan and its deployment protection settings. | Yes: A private link for each person on Pro, with their name on it. Expire or revoke any one. |
| Sharing a protected app outside your team | Partly: On Vercel’s Hobby plan you can create one shareable link to a protected deployment, in total, per account. | Yes: They open their link and they’re in, with nothing to sign up for. |
| What a shared link opens | Partly: A v0 chat shared with “Anyone with the link” opens the chat itself, with its prompt history, to anyone who has the address. Inviting named people needs a Plus, Business or Enterprise plan. | Yes: Your own build, running: every button and screen works, on mock data. |
| Who looked, and what each did | No: Not listed for individual viewers | Yes: Each person by name: every visit, click and minute, how far they took the tour, and who they passed it to. |

v0 and Roomi, side by side. What v0 does is from its own pages, read on 7 October 2026. Roomi is ours.

What the marks mean: “Partly” means partly, or with conditions; “Not listed” means not on their own pages.

## The Roomi way, from your v0 project’s code

Six commands, run by you or by your coding agent. Nothing goes live until you commit.

1. **Describe the demo, then rehearse it** — Work in a folder holding your v0 project’s code, on your own computer: if the project is on GitHub, clone it. The CLI’s first command describes the demo and leaves a guide written for your coding agent, so Claude Code or Cursor can run the rest. Deploy rehearses: it builds, checks for secrets and shows what would go live. Nothing has left your computer.
2. **Put it live** — Deploy again with commit, and the room is live. A new build can go to a preview first, for you to check before any viewer sees it. If a change goes wrong, roll back to the last good build. Each build keeps its log, for when one fails.
3. **Make a link for each person** — On Pro, make a private link for each client, with their name on it. Send it yourself, by email or however you usually reach them. Roomi sends nothing. When you send it, tell them who you are and that Roomi records what they do in the room for you. Our terms ask you to.
4. **See who looked, and what held them** — Each person’s visits in order, the screens they stayed on, how far they took the tour, and who they passed it to.
5. **Follow up while they’re still thinking about you** — Each viewer answers “What happens next?”: a meeting, a yes, later, a colleague, a question, or not for them. Roomi ranks who to call first. Ask your own Claude to draft a follow-up from what they did. Nothing is sent until you send it.

```text
$ npm install -g @getroomi/cli
$ roomi login
$ roomi init
$ roomi deploy
$ roomi deploy --commit
$ roomi link "Priya Shah"
```

## Ways to share a v0 build with a client, ranked

Ranked for one job: a client trying the real thing, and you knowing what they did. Roomi is ours.

1. **Roomi** (ours) — your own build, running, at a private link for each person, with nothing to sign up for. You see every visit, click and minute, by name.
2. **A Vercel deployment** — v0 publishes a project to Vercel. Who can open the deployed app depends on your Vercel plan and its deployment protection settings. On Vercel’s Hobby plan you can create one shareable link to a protected deployment, in total, per account.
3. **A shared v0 chat** — A v0 chat shared with “Anyone with the link” opens the chat itself, with its prompt history, to anyone who has the address. Inviting named people needs a Plus, Business or Enterprise plan.
4. **A screen recording** — easy to send, but they watch you use it rather than try it. Loom names a viewer only when they watch while logged in to Loom. Anyone else shows as an anonymous view.

## Questions

### Can I send a client my v0 link?

A v0 chat shared with “Anyone with the link” opens the chat itself, with its prompt history, to anyone who has the address. Inviting named people needs a Plus, Business or Enterprise plan. That shows them how it was made. A Roomi link shows them the demo itself, running.

### Who can open my published v0 app?

v0 publishes a project to Vercel. Who can open the deployed app depends on your Vercel plan and its deployment protection settings. On Vercel’s Hobby plan you can create one shareable link to a protected deployment, in total, per account.

### Does my client need a Roomi account?

No. Their link takes them straight into the room, with nothing to sign up for. The link is their key, and it carries their name.

### What does Roomi cost?

Free costs nothing: static demos, listed on the community at one public address, with total views. A private link per person and everything each person did start on Pro, at £4 a month or £40 a year, before VAT.

### Do I have to tell a client their visit is recorded?

Yes. Before or when you send the link, tell each viewer who you are and how to reach you about their data. Tell them too that Roomi records what they do in the room and shows it to you. Our terms ask for both.

## Fair, and dated

Every claim about another product on this page is from that product’s own pages, each read on the day beside it, the oldest on 7 October 2026. Roomi is ours, and says so. If something here is out of date, tell us and we’ll fix it the same week.

- v0, read 12 October 2026: [v0.app/docs/deployments](https://v0.app/docs/deployments)
- Vercel, read 12 October 2026: [vercel.com/docs/deployment-protection/methods-to-bypass-deployment-protection/sharable-links](https://vercel.com/docs/deployment-protection/methods-to-bypass-deployment-protection/sharable-links)
- v0, read 12 October 2026: [v0.app/docs/sharing](https://v0.app/docs/sharing)
- Loom, read 12 October 2026: [support.atlassian.com/loom/docs/see-who-has-viewed-your-video/](https://support.atlassian.com/loom/docs/see-who-has-viewed-your-video/)
- Vercel, read 7 October 2026: [vercel.com/pricing](https://vercel.com/pricing)

## Read more

Guides that go further into the same question.

- [How do you share a v0 project with a client?](https://getroomi.com/guides/how-to-share-a-v0-project-with-a-client): v0 shares chats and publishes apps to Vercel. How to put your v0 app in front of a client privately, with a tour, and see what they did.
- [Is it safe to send a client a link to an app you built with AI? A checklist](https://getroomi.com/guides/is-it-safe-to-send-a-client-an-ai-built-app): Eleven checks before an app built with Claude, Lovable or Bolt goes to a client: data, keys, backends, links, and what to tell them.

## Send the demo, not the chat

Put your v0 build in a room, give each client their own link, and see who leaned in.

[Get started free](https://app.getroomi.com/start)