+ +

Client demos

Turn your AI-built demo into a branded, tracked client link.

Q: Can I password-protect the demo?

Yes. Add an optional password and only people you share it with can open the page. Passwords are encrypted: we can’t see them.

Q: Can the client leave feedback on the demo?

Yes, on Solo and Team, once you switch comments on for the page. They pin a comment on an element, mark an area or quote a line, and can approve or request changes. People you sent a recipient link comment straight away; anyone else confirms their email once with a one-time code or Google.

Q: Will the demo be public or searchable?

No. Pagelive pages are noindex by default (we tell Google not to list them), and they’re served from an isolated content plane, walled off from your dashboard and billing.

Q: Can I update the demo at the same link?

Yes. Publish a new version anytime and the link stays the same: no re-sending, no stale copies in your client’s inbox. Version history keeps your previous edits.

You built a slick demo in Claude or by hand. Don’t hand the client a raw share link that needs a login, or a public page anyone can stumble on. Send a branded, password-protected link, and see when they open it.

Publish your demo Publish from Claude

Free for 2 public pages. Or drop a file on the homepage.

+ +

The problem

A client demo shouldn’t need a login, or show up on Google

A demo carries your client’s name, brand, and sometimes their data. The easy ways to share it either gate it behind someone else’s login or publish it where search engines can find it.

Raw AI share links

A raw artifact share URL can require your client to log in to the AI tool before they see anything, and the address bar says “somebody else’s product,” not yours.

Free hosting tools

The quick free ways to put HTML online were never built for client work. Most publish your demo as a public web page that Google can index and anyone can find in search.

A Pagelive link

Your client clicks one clean link: no account, no login. The page is noindex by default, password-protectable, and lives on your own domain with Solo.

Add a password when the demo is confidential: how password protection works.

+ +

It’s the demo, not a screenshot

The interactivity survives

The whole point of a demo is that the client can click it. A PDF or a screen recording flattens the thing you actually built. Pagelive serves the live HTML: every button, animation, and state works exactly as it does on your machine. In the meeting, present straight from the link. After the meeting, the client explores it on their own, and you see that they did.

How publishing works →

	PDF / recording	Live page
	Clicks and states flattened away	Every interaction works
	Client watches, can’t try	Client explores it hands-on
	New cut for every revision	Update anytime, same link

+ +

Engagement

Know when the client actually looked

Every demo link is tracked: opens, unique viewers, how long they spent, which days, and what country. Get an email when it’s opened, so you follow up while the demo is still on their screen, not a week later. A four-minute exploration the night before the call is a very different signal from a six-second glance. Now you know which one happened.

Acme prototype · last 7 days live

14

Opens

5

Unique viewers

6m 02s

Avg. dwell

Tue

Busiest day

Three viewers on Tuesday: the demo made it past your contact to the wider team.

+ +

Feedback on the demo

Your client pins feedback on the demo. Your agent makes the change.

No screenshots with red circles, no “the third button on the second screen.” With comments on, the client clicks the element they mean, or marks an area, and writes. Every thread knows which version of the demo it was written on, and shows when a later version fixed it.

How comments and approvals work →

acme-prototype · review

Mon 16:20
Pinned on the Export button: should open a menu
Mon 16:24
Area marked on the chart: legend overlaps
Tue 11:02
v4 published · both threads fixed in v4
Tue 15:30
Approved on v4

+ +

How it works

Three steps to a client-ready demo link

1

Publish your demo

Say “publish this” in Claude, or drag the HTML file onto the homepage. No export, no screenshots: the live page goes up exactly as you built it.

2

Add a password and your brand

Lock it for the client’s eyes only and serve it from your own domain with Solo. The link reads as your studio, not a free tool.

3

Send one link, and keep it current

See when the client opens it and how long they explore. Ship a revision anytime; the link never changes, so there’s nothing to re-send.

Publish straight from Claude → Publish a Claude artifact →

+ +

Frequently asked

Does my client need a Claude account? +

No. A Pagelive link opens in any browser: your client never needs a Claude account, a Pagelive account, an app, or a login. If you add a password, that password is all they enter.

Can I password-protect the demo? +

Can the client leave feedback on the demo? +

Will the demo be public or searchable? +

Can I update the demo at the same link? +

Sending demos for an agency? See Pagelive for agencies · plans on pricing.

+ +

Send the demo, not a screenshot.

A branded, password-protected link your client can open without a login, and you’ll know when they do.

Publish your demo Publish from Claude