You ran the render. Quarto handed you one self-contained HTML file — plots, tables, and folded code baked in. The friction isn't the analysis; it's getting it to someone who doesn't have R and shouldn't need it. Drop the rendered file into miinideck and get a private, unguessable link in seconds. It opens in any browser, stays out of search, and shows the report exactly as you knit it — tabsets, htmlwidgets, and all. Private delivery, not a public page.
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.
Render with self-contained output on — `embed-resources: true` in Quarto, or `self_contained: true` in RMarkdown — so the plots, CSS, and any htmlwidgets land inside one HTML file. Drop that file into miinideck and it publishes to a private 32-character link in seconds. If your report writes out a `_files` folder of assets instead, zip the folder and drop the ZIP.
Send the link to a co-author, advisor, or client who has no R session and no interest in installing one. They open it in a browser and read the report as rendered — tabset panels switch, plotly and leaflet widgets respond, folded code blocks expand. No account, no login, nothing to set up on their side.
For unpublished findings, add a password so the report only opens for the people you name, and set an expiry so a draft doesn't outlive its moment. Re-render next week, re-upload, and the link stays the same for everyone you already shared it with.
Render to a self-contained HTML file (`embed-resources: true`) and publish it as a link with miinideck. The reader opens the link in any browser — no R, no RStudio, no Quarto CLI on their machine. They see the knitted report as a live page, exactly as you rendered it.
Yes, as long as they're embedded in the HTML at render time. miinideck serves your file as-is — it doesn't sandbox or strip scripts — so JavaScript runs, embedded widgets respond, and CDN libraries load over HTTPS. Tabsets, code folding, and crosstalk linking behave the way the render intended.
No, and that's the honest boundary. A Shiny document, or anything that runs server-side R or queries a database on each load, needs a real server — Vercel, Netlify, or a dedicated Shiny host are the right tools for that. miinideck delivers the static, pre-rendered slice: a knitted HTML report where the computation already ran. If you can render it to a self-contained file, it belongs here; if it needs a backend on every visit, it doesn't.
Every link is unguessable and no-indexed, so a draft never surfaces in search and only the people you send the link to can open it. Add a password to gate sensitive results, and set an expiry so a preliminary report self-destructs once it's served its purpose. The passphrase travels separately from the URL.
Turn on Review and anyone with the link can pin a comment to the exact element — a plot, a table cell, a paragraph — without making an account. You resolve each thread as you address it. Review usage is free on every plan; only 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.