Client reports, prototypes and internal dashboards are exactly the files you don't want sitting on a third party's server. Self-hosting Hushdrop puts the share links on your domain and the files in your own Vercel Blob store. It takes one deploy and two commands.
What you get when you self-host
Everything in the CLI works against your own store: password-locked pages, expiring links (--expire 7d, cleaned up by hush gc), whole static sites from a folder or zip, branded download pages for PDFs and other files, and site-wide password locks. Links live on your domain, and you can audit every line of the code that serves them.
Hook up your agents
The same commands work from any coding agent. For MCP clients, add the server:
npx -y hushdrop-mcp
It exposes publish_html and friends, and publishes to whichever backend hush init configured. For Claude Code, the skill in the repo teaches the agent to publish locked by default when you say "share this".
What it costs
Your Vercel Blob usage, which for HTML reports usually fits in the free tier. There's no Hushdrop fee for self-hosting, ever.
Self-host or hosted?
Self-host if you want your own domain, full file support and nothing outside your account. Use the hosted service at hushdrop.dev if you want links without a Vercel account: hush login once, then publish. You can move later with hush migrate, which re-homes your hosted drops to your own store.
Deploy the backend
Click Deploy to Vercel. Vercel clones the repo and creates a Blob store for it.
Connect your terminal
npx hushdrop setup pulls the Blob token from your Vercel project.
Add your domain
hush init --domain share.yoursite.com, then add the same domain in Vercel's project settings.
Publish
hush report.html prints a link on your domain and a password.