# Share a deliverable with a client, on a private link · Stacktree

Source: https://stacktr.ee/share-with-clients

[Skip to content](#main)   [stacktr.ee](/)  [Examples](/#proof) [How it works](/#how) [Pricing](/pricing) [Security](/security) [Log in](https://app.stacktr.ee) [Publish one](https://app.stacktr.ee/?join=1)     By [Steve Smith](/about) · Founder, Stacktree Last updated September 20, 2026       Use case

# Send a client the work on a private link, not a public URL.

  Publish the deliverable, add a password and your domain, send the link.
A report, prototype, dashboard, or a page your AI just built. The client opens it in a
        browser with no account, and it never shows up anywhere you did not send it.

  [Publish one free →](https://app.stacktr.ee/?join=1) [See a live proposal](https://example-proposal.stacktr.ee/)   No account for your client · No card to start · About a minute

##  How do you share a deliverable with a client privately?

Publish the HTML to Stacktree and send the link. It lives at an unguessable URL that is never listed or indexed, so it is private by default; add a password or your own domain and the client opens it in any browser with no account to create. When you revise the work, the link stays the same, so you never resend it.

         See a real one first. Here is an actual client proposal, sanitised and hosted on Stacktree, password-protected exactly as described below. Open it with the password preview: [view the example deliverable](https://stacktr.ee/p/LcWaNc7gWbgUTDeMPsFMYK/).

## The handoff AI made harder, not easier

 AI got very good at producing a finished, self-contained page: a discovery document, a status report, an interactive prototype, a dashboard, a pitch. The work is done in minutes. Then you hit the part nobody solved: getting it to the client cleanly.

 The usual options all give something away. An HTML file attached to an email looks improvised and half the time renders wrong. A screenshot throws away the interactivity that made the work worth building. Standing up a Vercel or Netlify project is developer plumbing one page should not need. A Notion or Drive link is generic, unbranded, and often pushes your client into a sign-in wall. And a design-tool preview can expose your working file or demand an account from the viewer. None of these says: here is a private, professional link to the work.

## The flow

  - Publish the file. Drop the HTML in, or ask your AI to publish it directly. You get a private, unguessable link straight away.
 - Gate it if you need to. From Solo, add a password or restrict viewing to the client’s email domain. Set an expiry so the preview does not outlive the engagement.
 - Put your name on it. Serve it from your own domain so it reads as your studio’s work, not a file on someone else’s host.
 - Send the link. The client clicks and sees the real, interactive deliverable. No account, no app, no download.
 - Know it landed. From Solo, see how many people opened it and when; Studio adds how far they read. Either way you follow up informed instead of chasing.
 - Collect the changes. Turn on the [client feedback loop](/client-feedback-loop) and comments come back on the page itself, anchored to the exact element, and the fix ships to the same URL.

## Why a private link beats the alternatives

  - vs emailing a file: renders perfectly every time, and you control access instead of letting an attachment travel.
 - vs Notion / Google Drive: branded, on your domain, and no sign-in friction for the client.
 - vs a full client portal: no setup and no account for the client. Portals are where deliverables go to be un-opened, and [the login is the reason](/blog/clients-never-log-into-your-portal). One deliverable stays one link; when the work keeps coming, a [client space](/client-spaces) gathers it behind one address without anyone logging in.
 - vs a design-tool preview: a password, no exposed working file, and no forced account on the viewer.

## Private, professional, and under your control

 The link is the credential, and you decide who gets in: passcode, email-domain gate, expiry, or a [burn-after-read link](/one-time-view-links) for a contract, an offer letter, or a credentials handoff that should not outlive being read. For confidential client material you can encrypt the page end-to-end, so even the host cannot read it. And because you can replace the page in place, sending a revision never means sending a new URL: the client keeps the same link and always sees the latest version.

FAQ

## Frequent questions

     How do I send a client a deliverable without making it public? +  Publish the file to Stacktree and send the link. Every page lives at an unguessable URL that is never listed or indexed, so it is private by default. Add a password or restrict it to the client's email domain if you want a second layer. Nothing about it is searchable, and there is no public gallery it could turn up in.   Does the client need an account to open it? +  No. The link opens in any browser with no login and no account to create. That is the main reason a hosted link beats a Figma or Notion share, where the client often gets pushed into a sign-in wall before they can see the work.   Can I password-protect a client preview link? +  Yes. Set a passcode and the page asks for it before rendering, so forwarding the link is not enough to open it. You can also set an expiry so a preview does not stay live forever after the project ends. See [password-protecting a page](/password-protect-html-page).   Can I put it on my own or my agency's domain? +  Yes. Point your own domain at the site so the client sees your brand, not a third-party host. The deliverable looks like part of your studio, not a generic file-share link.   I made the HTML with AI (Claude, Codex, etc.). Can I share that with a client? +  That is the most common case. AI is very good at producing a self-contained report, prototype, or dashboard as one HTML file; the hard part is handing it over. Publish that file to Stacktree and you get a private link in seconds, instead of emailing an HTML attachment, screenshotting it, or standing up a whole hosting project for one page.   How is this different from a client portal like Notion or SuiteDash? +  A portal is software you ask the client to adopt: an account, a login, invoices, messages. For receiving finished work the login buys the client nothing, which is why portals mostly go unopened. Stacktree never asks the client to log in. One deliverable is one link; when the work keeps coming, publish it under a [client space](/client-spaces) and it gathers behind a single address of yours, gated by one passcode the client types once. If what you need is a CRM, a portal is still the right tool.
Keep reading

## Related guides

   -  [ Security at Stacktree How Stacktree protects agent-generated HTML: unguessable URLs, password and email-domain gates, end-to-end encryption. ](/security)
-  [ Templates Ten client documents, each publishable as a private link in one click. ](/templates)
-  [ See how the client read it Opens, reactions, and how far they got through your deliverable. ](/page-engagement)
-  [ Password-protect a page Put a passcode on a client preview before you send it. ](/password-protect-html-page)
-  [ Share Claude artifacts privately Hand a client a page your AI built, on a private link. ](/share-claude-artifacts)
-  [ Host AI-generated reports Send a report as a live page instead of a PDF or screenshot. ](/host-ai-reports)
-  [ Host a private client demo site One gated link for the demo, no staging server or preview deploy. ](/host-client-demo-site)
-  [ Client spaces One address per client, on your domain, with no client login. ](/client-spaces)

References

## Sources and further reading

   -  [ MDN: URL fragment ↗ Why an end-to-end-encrypted page's key, kept in the URL fragment, never reaches the server. ](https://developer.mozilla.org/en-US/docs/Web/API/URL/hash)
-  [ OWASP: password storage ↗ How a page passcode is stored as a hash, never in plaintext. ](https://cheatsheetseries.owasp.org/cheatsheets/Password_Storage_Cheat_Sheet.html)

## Hand the client a link you would be proud to send.

 Private by default, your own domain, no account for them. Free to start, no card.

 [Publish one free →](https://app.stacktr.ee/?join=1)       stacktr.ee  [About](/about) [Blog](/blog) [Changelog](/changelog) [Pricing](/pricing) [Security](/security) [FAQ](/faq) [Made with Stacktree](/made-with)  Building with AI agents? See the [developer docs →](/developers)

---
Full markdown summary of the Stacktree marketing surface: https://stacktr.ee/llms-full.txt