Kimi can hold a whole build in one long thread and hand back a finished site; the friction is getting it out of the thread. While it lives in the conversation, anyone you want to show it to has to be signed in there beside you. Export the HTML and drop it into miinideck instead: you get a private, unguessable link that opens in any browser — no Kimi account, no platform sign-in on their end. It runs the way Kimi built it, and only the people you send the link to ever see it.
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.
Export your Kimi-generated site as an HTML file — or zip the folder if the build split into separate CSS, JS, and image files — and drop it in. miinideck publishes it to a private link in seconds, scripts and styling intact.
Send the link to whoever needs it. They open it in any browser with no Kimi account and no sign-up; the link is unguessable and no-indexed, so the site stays off search and out of any public feed.
Kept iterating in the same Kimi thread? Re-export the latest build and re-upload — the link stays the same, so your reader always lands on the current version instead of an old paste. Add a password or an expiry while it's still rough.
Export the site to HTML and drop it into miinideck. You get a private link that opens the site in any browser, completely independent of Kimi — the person you send it to needs no Kimi login and no sign-up of any kind. You decide who gets the link.
Take the final HTML Kimi produced (zip the folder if it shipped as separate CSS, JS, and asset files) and drop the export in. miinideck serves exactly those files, so what your reader opens is the build from the end of your thread, not a screenshot or a re-typed copy. Re-export and re-upload any time you take the conversation further.
Yes. JavaScript runs, CSS applies, and external libraries loaded over HTTPS resolve, so the site behaves as Kimi generated it. The one thing it can't do is run a backend server — miinideck serves static front-end files, not a running server.
miinideck hosts the static front-end slice — HTML, CSS, JavaScript, and assets that run in the browser. If your build needs a live server, a database, or server-side API routes, host it on a platform built for that, like Vercel or Netlify. For a self-contained Kimi site that runs entirely in the browser, a private miinideck link is the faster path.
Yes. Turn on Review and anyone with the link can pin a note to the exact element — no account needed — and you resolve each one. Review is free on every plan; on Studio you can export the whole thread as a prompt to take back into Kimi or another AI tool.
No card to try, no sign-up to get a link. Sign up free to keep links forever, password-protect them, and store more.