Product studios and freelance developers
Share an AI-built prototype with your client for review
Your agent built a clickable prototype in Claude Code, Cursor or Codex. Publish the folder to a link like acme-app.quickhost.ing, protect it with a password, and send it. Your client clicks through every page as it was built and comments on the text they want changed, and your agent can read those comments and republish the fix to the same link.
By the QuickHost team. Checked against the product on .
The situation
Where does this usually go wrong?
A prototype is a folder of HTML, CSS, JavaScript and images, and showing it to a client often means a screen-share or a hosting setup made for production apps. Feedback then comes back as screenshots in an email.
- A screen-share shows the prototype once, and the client can’t click through it again on their own time.
- The AI tool’s own share link may show a single page, or ask the client to sign in.
- A hosting platform asks for an account and a project setup before the client sees anything, and the link it gives you is public.
- Feedback arrives as screenshots with arrows, and someone has to work out which screen each one shows.
Step by step
How do you do it with QuickHost?
Publish the build folder, put a password on it, and send the link. Comments come back on the page itself, where you or your agent can read them.
- 1
Publish the folder
Drop the build folder or a zip onto the dashboard, or have the agent run qh publish ./dist --name acme-app. Every page, script and image is served exactly as uploaded.
- 2
Put a password on it
Choose password-protected and you get a doorcode you can read back and re-send later. Or make it private and create a named link for each reviewer.
- 3
Send the link
Your client opens it in any browser, on a phone as well, with no account and nothing to install.
- 4
Collect comments in place
Turn comments on. Your client highlights the text they want changed, adds their name and comments, and can reply in the same thread.
- 5
Fix and republish
Ask your agent to read the comments over MCP or with qh comments --json, make the changes, republish to the same address and resolve what it fixed.
What you get
What do you get from it?
Your client reviews the prototype in their own time, and each piece of feedback arrives attached to the part of the page it’s about.
The prototype as it was built
Multi-page sites with their own CSS, JavaScript and images work as they did on your machine, because nothing is rebuilt.
Private until you share it
A password or named links decide who opens it, and every project is hidden from search engines unless you choose otherwise.
Feedback with its location
Each comment carries the text it was left on, so neither you nor your agent has to guess which screen it means.
The same link after every round
Republishing keeps the address. Comments that still match move with the text, and any that can’t be matched are flagged for you.
Other options
What else could you use for this?
These tools come up for the same job. Each comparison is dated and sourced from the other product's own pages, and says when it's the better pick.
- QuickHost vs Netlify Drop
Netlify Drop puts a folder online for free, with no password or link per person.
- QuickHost vs Claude artifacts
A Claude Code artifact is a single file, and relative links to other pages don’t resolve.
- QuickHost vs display.dev
display.dev suits prototypes your own company reviews, with company sign-in and a free plan.
Questions
What else do people ask about this?
The questions that come up when someone is setting this up for the first time, answered plainly.
How do I share a Claude Code prototype with a client?
Publish the build folder to QuickHost from the dashboard, with qh publish, or by asking Claude Code to do it over MCP. Then send the link. Add a password if the client shouldn’t share it.
Does a multi-page prototype work, or only a single HTML file?
Both work. Upload a folder or a zip and QuickHost serves every page, stylesheet, script and image at the paths you built them with.
Can my client leave feedback without an account?
Yes. With comments on, they highlight text, add their name and comment. You can limit commenting to the email addresses you name.
Does QuickHost run a build step or backend code?
No. It serves static files exactly as uploaded, so build the prototype first and publish the output folder. There are no server functions.