Share a Cursor build
You built it in Cursor. Now put it in front of a client.
Ask Cursor’s agent to deploy it to Roomi. Your client gets a link of their own with nothing to sign up for, and you see what they did.
What sharing from Cursor gives you today
Each line about Cursor is from its maker’s own pages, read on 7 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
| Cursor | Roomi (ours) | |
|---|---|---|
| Puts what you built online | PartlyCursor’s git forge, Origin, connects to Vercel: pushes can trigger deploys, and pull requests can get preview environments. | YesRoomi hosts it for you, on a demo domain kept apart from your own. |
| A link for each person, on Vercel | NoOne public address; per-person links not listed | YesA private link for each person on Pro, with their name on it. Expire or revoke any one. |
| Who looked, and what each did, on Vercel | NoNot listed for individual viewers | YesEach person by name: every visit, click and minute, how far they took the tour, and who they passed it to. |
The Roomi way, from the repository you built it in
Ask Cursor’s agent to run these, or run them yourself. Nothing goes live until you commit.
- Step one
Describe the demo, then rehearse it
Open the repository you built it in, and ask Cursor’s agent to deploy it to Roomi. 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.
- Step two
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.
- 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.
npm install -g @getroomi/cliroomi loginroomi initroomi deployroomi deploy --commitroomi link "Priya Shah"
Ways to share a Cursor build with a client, 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 Vercel deployment, through Origin — Cursor’s git forge, Origin, connects to Vercel: pushes can trigger deploys, and pull requests can get preview environments. On Vercel’s Hobby plan you can create one shareable link to a protected deployment, in total, per account.
- 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 Cursor put my app online for a client?
- Cursor’s git forge, Origin, connects to Vercel: pushes can trigger deploys, and pull requests can get preview environments. On Vercel’s Hobby plan you can create one shareable link to a protected deployment, in total, per account. Roomi hosts the demo for you, with a private link for each client.
- Can Cursor’s agent deploy it for me?
- Yes. The CLI’s first command leaves a guide written for the agent, so it can describe the demo, rehearse the deploy and publish it when you say so.
- 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 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.
- Cursor, read 12 October 2026cursor.com/docs/origin/apps
- Vercel, read 12 October 2026vercel.com/docs/deployment-protection/methods-to-bypass-deployment-protection/sharable-links
- Loom, read 12 October 2026support.atlassian.com/loom/docs/see-who-has-viewed-your-video/
- Vercel, read 7 October 2026vercel.com/pricing
Read more
Guides that go further into the same question.
- How do you show a Cursor project to a non-technical client?: A repository or a localhost link means nothing to a client. How to turn a Cursor project into a working demo with a tour, on a link of their own.
- What should a demo tour script say? A template: A copyable template for a self-guided demo tour: three to six steps, what each says and the screen it opens, with a worked example.
Send the real thing instead of a deck
Let your agent put it in a room, and send your first link today.