A Vue build is already a folder of static files — the dist output Vite hands you after npm run build, with your single-file components compiled down to plain HTML, CSS, and JS. So getting one reviewer to look at it doesn't need a deploy pipeline or a hosting dashboard. Zip dist, drop it in, and get a private, unguessable link that runs the app live in any browser. It stays off search, opens with no sign-in on their end, and goes only to the people you send it to. Add a password or an expiry while the build is still pre-release.
Try it now
Drop a file — get a private link in seconds. No sign-up.
Drop an HTML file or ZIP bundle, or click to choose.
Single file or ZIP. Max 3 MB.
Up to 3 MB, link self-destructs after 7 days. Sign up free to keep links forever, password-protect them, and store more.
Run npm run build. Vite compiles your single-file components, router, and scoped styles into a dist folder of plain HTML, CSS, and JS. Zip that folder — not the src tree — and drop the ZIP in. miinideck unpacks it and serves the whole build behind one private link, with chunked assets and dynamic imports intact.
Send the link for review. It carries a no-index tag and the URL is long enough that nobody guesses it, so a pre-launch Vue build never lands in search and only your reviewers can open it. It runs live in their browser — no install, no account on their side.
Lock it with a password or set an expiry for the review window. Re-run your build and replace the ZIP whenever you iterate — the link stays the same, so reviewers always open the latest version from one URL.
Upload the build output instead of standing up a pipeline. After npm run build, your dist folder is just static HTML, CSS, and JS — zip it and drop it in, and the app runs in the browser behind a private link. No hosting account, no DNS, no deploy step to maintain. This covers any client-side Vue app; the one thing it can't run is an app that needs its own server.
Hash mode works out of the box. History mode expects the server to rewrite unknown paths back to index.html, which a static host doesn't do — so share the entry link and let single-page navigation take over inside the app, or switch the router to hash mode for the shared build. Either way, all your assets and dynamic imports resolve because the entire dist is served together.
Then part of the job needs a real backend, and a static link can't provide it. If your app has server routes, a database, or SSR — for example a Nuxt app rendered on the server — host that on Vercel or Netlify, which are built for it. miinideck owns the front-end slice: a client-side Vue build that talks to an already-deployed API still works fine here, served privately as static files.
Yes. The link is unguessable and no-indexed, so a pre-release build stays off search; add a password (free on every plan) so even someone with the link needs a passphrase. To revise, replace the ZIP from your dashboard — the link doesn't change, so reviewers keep one URL across every build.
Yes. Turn on Review and anyone with the link can pin a comment to the exact element they mean — no account needed — and you resolve each one as you fix it. Collecting and resolving feedback is free on every plan; exporting the whole thread as a prompt for Claude or Codex is a Studio feature.
No card to try, no sign-up to get a link. Sign up free to keep links forever, password-protect them, and store more.