miinideck

This is exactly what I needed! Drag-and-drop hosting with password protection makes sharing prototypes with clients so much smoother. Love that the link stays the same after re-uploads. A perfect solution for static deliverables! Great work.

This looks good, made me think of vapor locker but for files. Great job!

The private-by-default links, optional password protection, and no-install viewing sound ideal for sharing client prototypes without adding deployment overhead.

Very wonderful. This is a perfect solution

Turning HTML or ZIP bundles into private shareable links with password protection and expiry is a clean way to send client deliverables without a full hosting setup. If model bills start adding up behind the tools you use at work, pzero.studio is where we buy leftover capacity.

The no-build upload flow and private share links sound especially useful for sharing interactive prototypes with clients. The built-in password protection and expiry controls are a thoughtful touch.

The problem this solves is so relatable — emailing standalone HTML reports always breaks something, and full Vercel/Netlify setups feel like overkill for private deliverables. The fact that the link stays the same across revisions so client bookmarks don't go stale is a huge win. One question: for pinned element comments, does it also support mobile touch targets cleanly, or is it primarily optimized for desktop viewports?

This looks really useful for sharing AI-generated prototypes with clients without setting up hosting. Password protection, expiry dates, and keeping the same link after updates are especially practical.

The branching-from-a-frame idea is clear from the first screen — curious how you handle continuity when users leave and come back mid-path.

The same-URL-across-revisions promise is the part people will lean on hardest, so two things I'd spell out on the page: what a viewer with the tab already open sees after you re-upload (silent stale copy until they refresh, or a nudge?), and what the page looks like once an expiry date passes. A bare 404 reads as "broken link" to a client; "this link expired, ask the sender for a new one" reads as intentional. Also worth stating the ZIP limits outright - max size, and whether relative asset paths nested a few folders deep resolve as-is. That's the first thing anyone dropping an exported report will want to know before they try it.

The "drop a file, get a private link" flow is exactly right for client work. One question: for agencies sending deliverables, would you consider an option to white-label the share page — our own logo or domain instead of the default branding — or is keeping it minimal a deliberate choice?

The private-by-default links and simple HTML/ZIP workflow look very useful for sharing finished client work. Password protection and expiry on every link are especially thoughtful touches.

As a solo mobile game developer, I usually end up sending WebGL build folders over Drive links for playtesting, and it's always messier than it should be. The password protection plus a link that stays stable across re-uploads would make sharing updated builds with testers much cleaner. Curious whether the ZIP size limits comfortably fit a typical HTML5/WebGL export with assets bundled in.

Keeping one private URL across revisions, while letting reviewers pin comments to exact elements, turns this into a lightweight client-review workflow—not just static hosting. A useful edge case to clarify is what happens to annotations after the HTML structure changes. Do comments remain attached across re-uploads, and is there a version history or rollback option?

nice this is wonderful build

For client handoffs, can I download the original HTML/ZIP bundle again later, including its assets? The stable share URL is useful for reviews, but an export option would also let clients keep an offline copy of the approved deliverable before the link expires.

This is a really useful solution. I love how simple the workflow is — upload the files, process them, and get the result without unnecessary steps. Definitely something I can see myself using regularly.

I built this because of a small, stupid moment that kept repeating. I'd finish something — a deck, a report, a little interactive thing — and then spend longer figuring out how to send it than I'd spent making it. Email mangles an HTML file. A public host puts it on the open web when only one person was ever meant to see it. And every revision meant a new link and another "use this one instead" message. So miinideck is the boring middle: drop the file, get a private link, send it. The link is unguessable and off search by default, a password and an expiry are there on the free tier, and re-uploading keeps the same URL so nobody's bookmark goes stale. It only serves static front-end files — if what you built needs a backend or auth, that belongs on a real deploy platform and I'd rather say so than pretend otherwise. Would genuinely like to hear where it feels clumsy. That's the part I can still fix.

The 'no account for the client' part is the actual feature here, not the hosting. I build a lot of one-off interactive prototypes, and the number of times a client wouldn't bother signing up for yet another tool just to look at something I made for them is... a lot. Does the private link expire on its own, or is it on you to kill it?

The drop-a-file-get-a-link flow is exactly right for pre-release demos — most teams over-engineer this with a full hosting setup just to show one static page to a client. Two things that would make it a keeper for client work: link expiry or password protection so an unfinished prototype doesn't circulate forever, and the ability to replace the file without changing the URL, since the link inevitably ends up in an email thread already. Curious how you handle relative asset paths inside a dropped ZIP — that's usually where these tools break on real exports.