You ran astro build and the dist folder is ready — but it isn't public yet, and you want one person to walk through it first. Instead of standing up a staging deploy for a single review, zip dist and drop it in. You get a private, unguessable link that serves the whole site — every pre-rendered route, your content collections, the hydrated islands — and only the people you send it to can open it. The public deploy waits until you're sure.
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 astro build. Astro writes a dist folder of static HTML, CSS and JS — every route pre-rendered, every island bundled. Zip that folder and drop it in; miinideck serves the site behind one private link with routes and assets intact.
Send the link for review. It's no-indexed and unguessable by default, so a not-yet-launched site never shows up in search and reaches only the people you invite — no staging environment to provision, no DNS to touch.
Rebuilt? Re-zip a fresh dist and replace it — the link stays the same, so reviewers always land on the current build. Add a password or an expiry to fence the review window, and when it's approved, deploy it publicly wherever it's meant to live.
Run astro build, zip the dist folder, and drop it in. You get a private, unguessable link that serves the full static output — every pre-rendered route and hydrated island — so a reviewer can walk the real build before it's live anywhere public. No staging deploy to stand up for one round of feedback.
Yes — you upload the built output, not the source. astro build already resolves your content collections into static pages and bundles your interactive islands, whichever framework you wrote them in. Zip the whole dist folder and miinideck serves it with paths intact, so navigation, images, and client-side hydration all work the way they will once deployed.
Then part of it needs a real server, and this is the wrong tool for that part. Astro's server output — an SSR adapter, Astro Actions, or API routes under src/pages/api — runs on a Node or edge runtime, so host that on Vercel or Netlify, which are built to run it. miinideck owns the static slice: if your output is fully pre-rendered (output: 'static', the default), the dist folder runs here behind a private link.
Yes. Turn on Review and anyone with the link can pin a comment to the exact element they mean — a misaligned hero, a typo on a content-collection page — without an account. You resolve threads as you fix them, and on Studio you can export the whole thread as a prompt to hand straight to Claude or Codex. Review usage is free on every plan; only the export is Studio.
Yes — the link is unguessable and no-indexed by default, so search engines never reach a pre-launch build, and only the people you send the link to can open it. Add a password (free on every plan) for a second gate, or set an expiry so access ends on a date. The public deploy happens on your schedule, not by accident.
No card to try, no sign-up to get a link. Sign up free to keep links forever, password-protect them, and store more.