Share a Claude build
You built it with Claude. Now put it in front of a client.
Say “deploy it to roomi” in the same chat. Your client gets a link of their own with nothing to sign up for, and you see what they did.
What sharing from Claude gives you today
Each line about Claude is from its maker’s own pages, read on 12 October 2026. Each source is listed at the foot of the page.
- Yes
- Partly, or with conditions
- No
- Not listed Not on their own pages
| Claude | Roomi (ours) | |
|---|---|---|
| Opens for a client without an account, shared from Claude’s apps | NoAnyone opening an artifact shared from Claude’s apps, rather than published by Claude Code, needs a Claude account and must be signed in. The one exception is an older artifact published from a chat, which opens without one. | YesThey open their link and they’re in, with nothing to sign up for. |
| Opens for a client without an account, published by Claude Code | YesClaude Code can publish an artifact to a public link that anyone can open, with no claude.ai sign-in. On Team and Enterprise plans, public sharing is off until an owner turns it on. | YesYes. On Pro each link carries one person’s name, and anyone they pass it to is asked who they are. |
| Shared with named people | YesA Claude artifact can be shared with anyone who has its link, or with people you invite by email. An invitation works only for the person invited. | YesA private link for each person on Pro, with their name on it. Expire or revoke any one. |
| Who opened it, and what they did | NoWhen you invite someone to a Claude artifact, Claude doesn’t tell you whether they have an account. Its help page on sharing describes no record of who opened one. | YesEach person by name: every visit, click and minute, how far they took the tour, and who they passed it to. |
| Where it runs | Not listed | YesRoomi hosts it for you, on a demo domain kept apart from your own. |
The Roomi way, from the chat you built it in
Add the connector once. After that it’s one sentence to Claude, and Claude asks you before anything goes live.
- Step one
Add Roomi to Claude
In Claude, open Settings, then Connectors, and add Roomi as a custom connector. You sign in once. Nothing is installed.
- Step two
Say “deploy it to roomi”
In the chat where you built it. Claude checks the demo, drafts a guided tour and shows you what would go live. It publishes only when you say yes. A demo too big for a chat goes out from your computer instead, and Claude says when.
- Step three
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.
- Step four
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.
- Step five
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.
deploy it to roomiMake a viewer link for Priya Shah, expiring in two weeks.
Ways to show a client what you built with Claude, ranked
Ranked for one job: a client trying the real thing, and you knowing what they did. Roomi is ours.
- 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.
- A shared Claude artifact — Anyone opening an artifact shared from Claude’s apps, rather than published by Claude Code, needs a Claude account and must be signed in. The one exception is an older artifact published from a chat, which opens without one. Claude Code can publish an artifact to a public link that anyone can open, with no claude.ai sign-in. On Team and Enterprise plans, public sharing is off until an owner turns it on. Claude Code’s artifacts page describes no record of who opened an artifact, no expiry date and no guided tour. For anyone outside your organisation, it describes a public link, not one for a named person.
- 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.
- Screenshots in a deck — no setup at all, and nothing to click. A deck tells you, at best, that it was opened.
Questions
- Can a client open a shared Claude artifact without an account?
- Anyone opening an artifact shared from Claude’s apps, rather than published by Claude Code, needs a Claude account and must be signed in. The one exception is an older artifact published from a chat, which opens without one. Claude Code can publish an artifact to a public link that anyone can open, with no claude.ai sign-in. On Team and Enterprise plans, public sharing is off until an owner turns it on. A Roomi link opens for the person it was made for, with nothing to sign up for, and can expire or be revoked.
- How do I see who opened what I built with Claude?
- When you invite someone to a Claude artifact, Claude doesn’t tell you whether they have an account. Its help page on sharing describes no record of who opened one. Claude Code’s artifacts page describes no record of who opened an artifact, no expiry date and no guided tour. For anyone outside your organisation, it describes a public link, not one for a named person. On Roomi, each private link carries one person’s name, and everything they do in the room is recorded against it, down to who they passed it to.
- Can Claude deploy it for me?
- Yes. With the Roomi connector added, say “deploy it to roomi” in the chat. Claude checks the demo, rehearses the deploy and publishes it on your yes.
- 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.
how we checked
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 12 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.
- Claude, read 12 October 2026support.claude.com/en/articles/9547008-publishing-and-sharing-artifacts
- Claude, read 12 October 2026code.claude.com/docs/en/artifacts
- Loom, read 12 October 2026support.atlassian.com/loom/docs/see-who-has-viewed-your-video/
- Claude, read 12 October 2026support.claude.com/en/articles/9547008-share-artifacts
Read more
Guides that go further into the same question.
- How can you share a Claude artifact with a client who doesn’t use Claude?: Claude’s apps ask viewers to sign in; a Claude Code public link does not. Five ways to send an artifact to a client, ranked on privacy, effort and what you learn.
- How do you make a Claude artifact private, and send it to one client?: Who can open a shared Claude artifact, plan by plan, how to stop sharing one, and how to send one privately to a client who doesn’t use Claude.
- What is a Claude artifact, and who can see it?: What Claude artifacts are, the kinds there are since September 2026, who can open one when you share it, and how to show one to someone without Claude.
Send the real thing instead of a deck
Deploy it from the chat you built it in, and send your first link today.