Why not just email an HTML file to my client?

Email providers flag HTML attachments with security warnings and clients often ask for a PDF instead. An unfurl link opens instantly in any browser with no download required.

What happens when I update my document after sharing the link?

Your live share link always shows the latest published version. Clients keep one bookmark while you publish new versions from the dashboard, API, or MCP.

How does unfurl compare to dropping an HTML file in Slack or a shared drive?

Slack messages get buried in days and shared-drive files create version confusion. unfurl gives you one permanent URL with a full timestamped version history.

Can AI agents read an unfurl document directly?

Yes. Agents read unfurl links natively as HTML, always see the latest version, and use a fraction of the tokens compared to uploading a PDF to their context.

unfurlBeta

Join early access

Host & share AI-generated HTML.One link, always current.

Unfurl turns your AI-generated docs into a single live link—share once, always up to date.

Join early access See the solution

No credit card · free tier during beta · we're shipping fast and listening · Read the docs

Client deliverables
Team handoffs
MCP workflows
Agent-readable links

The problem

Why not just email the file?

✗

Email an HTML file → your client gets a security warning and asks for a PDF instead

✓

Send an unfurl link → opens instantly in any browser, no downloads, no warnings

✗

Drop it in Slack → buried in two days, and you've already updated it twice

✓

One permanent link → always shows the latest published version

✗

Save three versions on your desktop → 'proposal-v2-FINAL-v3.html'

✓

Every update is timestamped → full version history on every plan

✗

Upload a PDF to your agent's context → it's stale by tomorrow and costs 10x the tokens

✓

Share an unfurl link → agents read it natively, always see the latest version, at a fraction of the token cost

The difference

Stop sending files. Start sharing links.

Email attachments get blocked. Slack messages get buried. Filenames pile up. One unfurl link replaces all of it — and always shows the latest version. Wire in our hosted MCP server so anything that already speaks the protocol can publish or refresh without leaving the rest of your toolchain.

The old way

Documents

proposal-v1.html
proposal-v2.html
proposal-FINAL.html
proposal-FINAL-v2.html
proposal-FINAL-actually-final.html
proposal-FINAL-v3-USE-THIS.html
proposal-FINAL-v4-ACTUAL-FINAL.html
proposal-FINAL-SENT.html

Toclient@acme.com

SubjectProposal — Acme Corp

proposal_FINAL_v3.html

This file type may be unsafe. Recipients may not be able to open it.

Slack

you2:14 PM

Here's the proposal — let me know what you think 👇

proposal_FINAL_v3.html

23messages ago— easy to miss.

The unfurl way

app.unfurl.pub/d/acme-proposal

Same URL — every version

Proposal — Acme Corp

Single link for stakeholders: always the latest published copy.

Discovery-first plan: firm pricing follows the SoW and security review.

Out-of-scope items live in section 4; change control applies after kickoff.

Appendix covers security posture, subprocessors, and data residency.

Updated just now

How it works

Publish. Share. Stay current.

Push or upload

Drag and drop any HTML file to go live in seconds. Or publish from a script, the API, or MCP — the link updates automatically, no manual steps.

One link, every version

Your doc gets a permanent URL. Every update creates a timestamped version—see the full list in the dashboard.

Clients see what you publish

Send the link to clients or your team. Everyone sees the latest published version — nothing more. Drafts stay private. MCP-connected agents reuse the same URL as your doc evolves.

Static documents create stale agents.

unfurl links are live context — your agents always read the latest version with full fidelity. Connect the hosted MCP server once and every client that speaks MCP can publish and read without any extra integration.

The old way

~0 tokens

LLM

Generates Python code

Executes python-docx

Produces binary .docx

Recipient downloads

Opens Word

Copy-pastes into agent

Agent parses with errors⚠️ Table structure lost

The unfurl way

~120 tokens

LLM

HTML output

unfurl live link

Agent reads directly✓ Full fidelity

Agent-optimised format

HTML and Markdown are native to LLMs. No PDF parsing failures, no layout hallucinations, no bloated token usage. Agents read unfurl documents with perfect fidelity.

Live context, not snapshots

Attach an unfurl link to any agent workflow. When the document updates, your agent sees the change immediately. No re-uploading, no stale data.

MCP-native publishing

unfurl ships a hosted MCP server. Connect it once and any MCP-compatible client can publish or fetch documents — same API key, same workflow, no extra integration.

Ready for the agent era?

Get started free Read the docs

Early beta · Pricing

Plans for individuals and teams

We're validating unfurl with early adopters. Paid plan pricing will be announced before launch — the core free tier is here to stay.

🆓 Free

30-day Pro trial available

$0forever

Publish from the dashboard, API, or hosted MCP—shareable links and link view counts included. No card required.

✓Up to 10 published documents
✓MCP and API access (connect via OAuth or an API key)
✓Shareable links
✓Link view counts

Join early access

Coming next

⭐ Pro

$15/month

Unlimited docs plus password-protected links, in-dashboard editing, and custom branding—when you outgrow the free tier.

✓Everything in Free
✓Unlimited documents
✓Password-protected share links
✓In-dashboard doc editing (visual updates to published HTML)
✓Custom branding on shared views

Join early access

🏢 Teams (Coming soon)

Coming soon

Multi-seat and org needs — roadmap still open. Join the waitlist and help shape it.

✓Everything in Pro
✓Shared workspace for your team
✓Tell us what you need — we're defining the rest

Join waitlist

🔒 Enterprise

SSO, custom domains, BYO storage, SLAs. Let's talk.