Give work-in-progress a thoughtful entrance. Knock is 19 open-source React blocks and components for access screens, invitations, expiry states, and draft chrome installed with shadcn and owned in your codebase.
Which Vercel product did you use? What new capability did it give your team, and how did that shape the product you launched?
Maker
We used Vercel Preview Deployments to give every change a production-like URL before release. That let our small team test Knock’s React components, interactive playgrounds, documentation, and responsive states in real browsers without maintaining deployment infrastructure. This preview-first workflow shaped Knock into a library built specifically for sharing polished work in progress.
Report
Maker
📌
Hey Product Hunt 👋
I built Knock after noticing how often the entrance to work-in-progress gets treated as an afterthought.
The preview itself may be carefully designed, but the page around it is usually a plain password field. Then come all the details: who the preview is for, when the invitation expires, what happens after a failed attempt, how the work stays marked as a draft, and how someone asks for access again.
Knock turns those details into 9 complete blocks and 10 individual React components. You can start with a full client preview gate or take only the code field, expiry notice, draft ribbon, watermark, or relock control you need.
Everything installs through shadcn. The source lands in your project, uses React and Tailwind, and is yours to restyle and edit. There is no Knock runtime package.
One important boundary: Knock handles presentation, not authorization. Your application still verifies codes, creates sessions, and protects data on the server.
It is free, MIT licensed, and built for React 18 and 19.
I would love to know: what is the most awkward part of sharing unfinished work with clients or teammates?