Send the result, not the setup.
Give stakeholders a polished report they can open immediately—without a zip file, local server, or walkthrough.
Private publishing for HTML reports
Give your report a real address.
Publish a finished HTML file without rebuilding it as a website. rlake keeps the interactions intact and returns one durable link—ready for a client, a teammate, or an agent.
- Private by default
- No deployment setup
- Interactive HTML preserved
publish
$ rlake publish quarterly-review.html ✓ permanent link createdrlake.ai/r/q3-portfolio
Private linkOnly you control the library
Built for the last mile between finished and shared.
01 One file 02 One command 03 One stable link
The shortest publishing pipeline
From artifact to archive in three moves.
Skip the repository, build system, hosting configuration, and hand-written deployment instructions. If the report already works, it is ready for rlake.
- 01
Bring the finished file
Upload from the browser or pass the HTML artifact directly to the CLI.
- 02
Publish it once
rlake validates the report, stores it durably, and creates the viewer URL.
- 03
Share the address
Open it on desktop or mobile without exposing the rest of your report library.
One link, many handoffs
A clean endpoint for the work around the report.
Publish inside the workflow.
Agent-friendly tooling turns generated HTML into a durable artifact before the run ends.
Keep a link that survives the handoff.
Your report stays reachable after the notebook closes, the chat ends, or the temporary environment disappears.
Field note 01
Not every HTML report needs a website.
We compared file sharing, static hosts, repository-backed deployment, and private report archives—so you can choose the right amount of infrastructure for the handoff.
Read the 2026 guideReady when the report is
Publish the file.
Keep the address.
Sign in with your verified account and put the next report somewhere it can stay.
Enter rlake