A Gradio app normally needs a Python process running somewhere — a server you pay for around the clock just so a few people can click through it. But often what you're really sharing is the interface and a handful of captured results, not live inference. Export that as a static page, drop the HTML or a zipped folder, and get a private link in seconds. No instance to keep warm, no hosting bill, no deploy pipeline — just an unguessable URL only the people you send it to can open.
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 the demo as static files. A captured Gradio walkthrough, a notebook rendered to HTML, or a front-end that calls an inference endpoint you host elsewhere — save it as a self-contained HTML page or zip the folder with its assets, then drop it in. miinideck unpacks it and serves it behind one private link.
Send the link for a look. It's unguessable and no-indexed, so an unreleased model demo never lands in search and only the reviewers or collaborators you send it to can reach it.
Re-run the demo, re-export, and replace the file — the link stays the same, so people always open the latest version. Add a password or an expiry to scope the review window.
Not here — and it's worth being clear about why. A live Gradio app runs a Python process that loads your model and serves inference, which needs a real server kept running. For that, deploy to Vercel or Netlify (or a GPU host for heavy models) and let it run there. miinideck hosts the static slice: an exported demo, a recorded walkthrough, or a front-end that talks to an inference endpoint you host elsewhere. If the job is 'people need to run my model,' you need a server; if it's 'people need to see my demo privately,' a static link is the lighter path.
Share the front-end as static files instead of keeping an instance live. Export the interface and your captured results to a self-contained HTML page or a zipped folder and drop it in — it opens in any browser with nothing running on your side. This fits demos meant to be seen and clicked through, not ones that need fresh inference on every visitor's input.
That works well. If your model lives behind an API — your own endpoint or a managed inference service — and the Gradio-style page just calls it from the browser, host that page here as static files. The link stays private and no-indexed. Keep your API key and inference on the backend you control, not inside the shared bundle — don't ship secrets in the export.
Yes. Turn on Review and anyone with the link can pin a comment to the exact element — a mislabeled output, a confusing control — without making an account. You resolve threads as you go. Review usage is free on every plan; exporting the whole thread as a prompt for Claude or Codex is a Studio feature.
Yes. Every link is unguessable and no-indexed by default, so a model that isn't public yet stays off search. Add a password (free on every plan) so even someone holding the link needs a passphrase, and set an expiry so the demo doesn't linger after the review. Links that never expire come with the Solo plan.
No card to try, no sign-up to get a link. Sign up free to keep links forever, password-protect them, and store more.