freo.cloud
Claude Code · Codex · Cursor · Claude.ai · ChatGPT

Publish what your AI agent makes — safely.

Reports, dashboards, HTML pages, drafts — straight from the coding agent or chat assistant you already use to your own corner of the web. You choose who sees each one, and freo keeps it private, sandboxed, and scanned for leaked keys.

No passwords · existing accounts get a sign-in link; new emails join the invite list

your agent Example
$ Install the freo.cloud publishing skill from
https://freo.cloud/skill and use it to publish my documents.
Then I'll just say things like "publish this for me" or "share this with Angela".

This is just an example of what you'll paste. and we'll generate the real one — with your own one-time setup link — on your Connect page.

See what a published document looks like →

See it

What it looks like in your terminal

your agent

How it works

Three steps to your first link

01

Claim your space

Sign in with your email. A magic link drops you into a personal @handle — your own corner of the web. No passwords, ever.

02

Connect your AI

Coding agent (Claude Code, Codex, Cursor, Windsurf…)? Paste one setup prompt — it installs the publishing skill. Chat assistant (Claude.ai, ChatGPT)? Add freo's MCP server as a connector — one-click OAuth, no token to paste. Either way, you do it once.

03

Publish anything

Reports, dashboards, HTML sites, PDFs, drafts, images — go straight to your space. You get a shareable link back in seconds.

The magic

One prompt. Then just ask.

then just ask…

“Publish this for me.”

freo → public link, ready to share · public

“Share this with Angela — just her.”

freo → emailed Angela a private link · email-protected

“Make this ready for Mike to read.”

freo → link only Mike can open · allowlist

“Update the published version — same link.”

freo → content replaced, readers see the new one · same URL

“Make the roadmap private now.”

freo → access changed instantly · re-shared

“Take that draft down.”

freo → unpublished, restore anytime · deleted

Beautiful to read

Documents that read like a product, not a raw file

Every Markdown document gets a polished reading view — automatically, nothing to configure.

On this page

Auto-built contents that follow you as you scroll, and every heading is deep-linkable — readers jump straight to the part they need.

Instant search

Hit ⌘K to search within a document and move between matches — no scrolling through a long report.

Code, highlighted

Fenced code renders with syntax highlighting, a language label and one-click copy.

Light or dark

A reading view that follows the reader's theme, with callouts and reading-time built in.

Access, your call

Choose who sees each document

Set the right level per document — from wide-open to a named few.

Public

Anyone with the link can read it, and it's listed on your public @handle page. Never search-indexed.

Unique link

Only people you hand the unguessable URL to can open it.

Email-protected

Readers verify with a one-time code sent to their inbox first.

Allowlist

Just the people you name. Remove someone — access is revoked instantly.

See who’s reading

Every view is tracked — who opened it and exactly when. The full picture is visible only to you, the owner. No vanity dashboards, just the truth about who’s actually reading your work.

views · q3-roadmap.md3 readers
  • sam@acme.co2m ago
  • lee@studio.io1h ago
  • unique link · #a7f2yesterday

Safe by design

Built so agents can't leak your secrets

Live

Private by default

Files are never public — served only after the access check you set. Never indexed, no referrers leaked.

Live

Sandboxed & isolated

Published HTML runs in a locked-down frame, walled off from your account and ours.

Beta

Secret scanning

Standard publishes are scanned for leaked API keys, tokens and credentials — and blocked before going live. (End-to-end-encrypted documents aren't: we can't read them.)

Beta

End-to-end encryption

Optional zero-knowledge tier: content is encrypted in your agent, the key rides your link and never touches our servers.

Your agent's key is scoped to your documents — publish and manage them, nothing else — and it expires and renews itself.

Straight talk: standard documents are stored privately and processed on our servers to render previews and run the access checks — they're not end-to-end encrypted. The encrypted tier is opt-in, and we never sell your content.

Links that don't outlive their purpose

Old links go quiet on their own

Most leaks aren't a hack — they're a share link from six months ago that everyone forgot was still open. freo shrinks that blast radius for you, automatically.

Goes private when it's idle

A link nobody has opened in about a month quietly flips private — and we email you when it happens, so a stale link can't keep leaking in the background.

Set a hard expiry

Want something gone by Friday? Give it an expiry date. After that the link just says “this has expired” — no content, no guessing. Per document, your call.

One click brings it back

Retired isn't deleted. “Make it live again” restores the exact sharing it had before — same link, same audience. You're never locked out of your own work.

You're always the owner: retired links stay visible to you, and any document can be set to never auto-retire.

What it costs

Free while we're in beta

No card, no plan to choose. Fair-use limits keep one account from swamping the service — they're generous for real work, and we'll tell you well before that changes.

10
new documents per day
10 MB
per file
50 MB
per static-site bundle, up to 200 files

Updating a document you've already published doesn't count against the daily limit.

Give your agent a place to put its work.

No passwords · existing accounts get a sign-in link; new emails join the invite list · what’s this?