Your report.
One command.
A link to share.

Turn a report from your terminal or coding agent into a page anyone with the link can open. Publish again to update the same URL.

Publish your first report → open a live report ↗

Free to start · no credit card · works with curl

1 — publish your file
# after setting your PIPEOUT_TOKEN $ curl -T atlas-reliability-review.html -u :$PIPEOUT_TOKEN https://pipeout.sh/a/ https://pipeout.page/r/23415d3f749ac4b08ea801ff
2 — open & share the report Example reliability report with availability metrics and endpoint performance charts Live example · your HTML, charts, and styles

how it works

Tell the agent to publish. Read the link.

One line in your prompt, one token in the environment. Every run after that ends at a URL you can send to someone.

1provide token + instructions
AGENT.MD
.ENV
2agent publishes
→reading 412 eval runs (last 24h)
→grouping 37 failures by root cause
→writing nightly-audit.html
$curl -T nightly-audit.html \
-u :$PIPEOUT_TOKEN pipeout.sh/a/
←pipeout.page/r/973c517f
3you share it
pipeout.page/r/973c517f4cf18378acdb53c0copy
1views

pricing

Free or Pro

Free

For personal use and small projects.

$0 forever

Start free
  • 250 MB storage
  • 10 MB max artifact size
  • Artifacts stay live 30 days
  • Access to last 5 artifact versions
  • Full render pipeline
launch price

Pro

For production workloads.

$50 /yr $108/yr 2 months free

First 100 subscribers only

Get Pro

Cancel anytime

  • Everything in Free
  • 5 GB storage
  • 100 MB max artifact size
  • Artifacts never expire
  • Every artifact version
  • Private artifacts

faq

Are the links public?

Unlisted by default, which is not the same as private. Nothing links to them, and pages are served noindex with no-referrer. Anyone holding the URL can open it, so treat a push as publishing. The path itself is 96 bits of randomness, so it will not be guessed or enumerated. On Pro you can make an artifact private, and then only your own account opens it — everyone else gets a locked page that will not even tell them what is behind it. Delete an artifact and its links stop working either way.

What happens when I upload again?

The stable URL starts serving the newest version. Each upload also keeps its own permanent version URL, frozen at what you pushed. On free the newest 5 version URLs stay live; older ones are kept but stop resolving until you upgrade. Pro reaches every one.

Do free links expire?

Yes — 30 days after the last push to that file. The clock runs from the push, not from when you created it, so a report your agent refreshes every night never expires; a one-off from five weeks ago does. Nothing is deleted when it expires: the page returns 410 with a note that it can be brought back, and upgrading restores every expired artifact and version immediately. Pro links do not expire.

Does the launch price go up?

The list price becomes $9/mo once the first 100 subscribers are taken. If you are one of the 100, your rate stays where you signed up for as long as the subscription stays open — the lock rides with the subscription, so cancelling gives up the launch price along with it.

Do I need an SDK?

No. Set a token and send an HTTP PUT — curl, fetch, httpx, whatever your agent already has. The dashboard helps you publish your first file and manage what you have shared.

What can I upload?

HTML, Markdown, text, logs, JSON, CSV, images, PDFs, and arbitrary binary files. Up to 10 MB per file on Free and 100 MB on Pro, measured after decompression. Gzip reduces transfer size; it does not raise the file limit.

Will pipeout modify my files?

HTML, images and PDFs are served unchanged — your CSS, your charts, your fonts. Markdown gets typeset, text and logs get line numbers, and anything else gets a download page.

Can I use it from CI or a container?

Yes. It needs one HTTP request and a token, nothing else — CI jobs, containers, cron scripts, agent runtimes, your laptop.