hub
What teams publish to Stacktree.
Six recurring shapes of work fit a publish primitive. Jupyter notebooks, Storybook builds, architecture diagrams, AI reports, Claude artifacts, single-file internal tools. Each gets its own page below with the exact workflow.
No card · 3 pages free · about a minute
dashboardstacktr.ee/p/…
notebookstacktr.ee/p/…
storybookstacktr.ee/p/…
diagramstacktr.ee/p/…
reportstacktr.ee/p/…
A dashboard your agent built.
Published with one call, shared with one link.
A Jupyter notebook, exported.
Plots intact, and viewers need no login.
A Storybook build, gated.
An email-domain gate keeps it company-only.
An architecture diagram.
Mermaid or D2, rendered behind an unguessable URL.
An AI-written report.
Replace-in-place: the same URL, every revision.
What can you use a private HTML host for?
Any artifact that ends up as a single self-contained HTML file. These are the LLM artifacts an agent produces as it works: data-science output (Jupyter notebook exports), component galleries (Storybook builds), diagrams (Mermaid, D2, Excalidraw, SVG), AI-generated reports (perf, research, status), Claude artifacts moved off claude.ai, and one-off agent-written utilities like JSON viewers or regex testers. Stacktree fits all six because each fits the same primitive: file in, private URL out, optional gate, optional replace-in-place.
Why these artifacts matter more as agents get more autonomous
As agent sessions run longer without supervision, the artifact an agent produces becomes the verification surface: the thing a human actually opens to check what the agent did. A 400-message transcript is not auditable; a rendered report, dashboard, or diff is. That is why agents emit so much HTML, and why it needs a home that is private by default (the artifact usually contains real data) and replaceable in place (the agent revises it as it works). Each use case below is one shape of that verification surface.
Every use case
- workflow Where do you host what you vibe-coded? Apps vs pages Full apps belong on your builder or Vercel. Static output (landing pages, prototypes, dashboards, AI artifacts) just needs a link, private if it is not public.
- share Are Claude artifacts private? How to share one without making it public A published Claude artifact is public: anyone with the link can open it, and the link never expires. How to share an artifact with others behind a private link, a passcode, or your own domain instead.
- share How to share a Claude Design outside your workspace Claude Design shares two ways: workspace access or a public artifact. Export the Project HTML and publish it to Stacktree for a private client link with a password, expiry, or your own domain.
- share Send Claude Cowork output to a client as a link Cowork builds the proposal and stops. The send step: save the output as a page, publish it to a private link, add a passcode, see when the client opened it, and replace it in place after the call.
- workflow Private HTML hosting: how it works and the best options What makes HTML hosting actually private: unguessable URLs, password and email-domain gates, end-to-end encryption, no public index. The mechanisms and options compared.
- workflow How to password-protect an HTML page or shared link Publish an HTML page to Stacktree and add a passcode so only people with the password can open it. Works for any HTML, including Claude and Codex artifacts, on top of an already-unguessable URL.
- workflow One-time view links: a page that deletes itself after the first open Publish an HTML page with burn-after-read: the first open atomically claims the single view and deletes the page behind the reader. Add a password so a link preview or an email scanner cannot spend the view. Privnote for full rendered pages.
- share Share a deliverable with a client, on a private link Send clients a report, prototype, dashboard, or AI-made HTML page as a private, password-protected link on your own domain. No public URL, no account for them, no portal to set up.
- workflow Templates: client documents you publish as a private link in one click Ten client deliverable templates, each a complete page you publish to your own account in one click: business proposal, project proposal, statement of work, pitch deck, brand audit, monthly report, technical due diligence, strategy review, research review, and a board deck. Free, with a passcode.
- workflow Business proposal template: a page the client opens, not a file A complete business proposal template you can publish as a private link in one click: where the client is, the one thing to get right first, the shape of the work, month by month, the fee, and how you will both know it worked. Free, with a passcode and a read receipt.
- workflow Project proposal template: scope, timeline and investment as one page A project proposal template for studios and consultancies, published as a private link in one click: background, objectives, scope cards, approach, timeline, investment table, team and next step. Free, with a passcode and a read receipt.
- workflow Statement of work template (SOW): scope, milestones, fees and sign-off A statement of work template for services firms, published as a private link in one click: parties and dates, background, what is in and out of scope, deliverables, milestones, fees and payment schedule, assumptions, change control, acceptance and sign-off. Free, with a passcode.
- workflow Pitch deck template: eleven slides, sent as one link A pitch deck template that opens full screen in any browser and is sent as a single private link: title, problem, solution, product, traction, market, business model, competition, team, the ask, close. See who opened it. Free, with a passcode.
- workflow What a Stacktree page looks like: example deliverables Three complete, fictional client deliverables published as Stacktree pages: a quarterly report, a project proposal, and a website audit. Open each one the way a client would.
- workflow Workflows: what to have your agent publish as a link Four recipes for turning agent output into a private link: the weekly client report on one self-updating URL, the dashboard your agent built, a Claude artifact moved to a private page, and an agent that publishes its own run report.
- workflow Publish a weekly client report to one link that updates itself Publish the report once, send one link, and update it in place every week with update_site, the n8n node, or the GitHub Action. The client bookmarks one URL that always shows the current numbers, behind a passcode or email gate.
- workflow Host an HTML dashboard your agent built Save the dashboard as one self-contained HTML file and publish it to a private, unguessable URL: drag and drop, one publish_html call, or one curl. Refresh it in place on the same link, gate it, or let it expire on its own.
- workflow Move a Claude artifact to a private link that will not expire A published Claude artifact is a public link; unpublishing kills it for good. Copy the HTML out, publish it to a private URL with a passcode or your own domain, and update it in place. Permanent from Solo; 7 days free.
- workflow Have your agent publish its own run report as a link End every agent run with a link, not a wall of terminal text: the agent renders an HTML run report, calls publish_html, and hands back a private URL. Later runs update the same page, so one bookmark is the standing status.
- workflow Send a client report as a link, not a PDF attachment Stop attaching report_final_v3.pdf. Publish the report as a private web page, send one link that stays current, and know when the client opened it.
- share How to share an HTML file as a link (no login for the client) Turn an HTML file into a link that opens in any browser with no account and no download. The steps, then the private version for client work: passcode or company-email gate, per-recipient links you can revoke, expiry, and burn-after-read.
- workflow Can a client view a page without creating an account? Yes. The link itself is the credential: an unguessable URL, plus an optional passcode or a work-email check by magic link. No registration, no app, no download. What DocSend and portal software ask of viewers instead, and which gate fits which situation.
- workflow How agencies share AI-generated work with clients The agent produced the report. The client cannot receive a raw artifact link. How agencies make AI work client-ready: a design pass, a passcode or email gate, their own domain, per-recipient links, and one URL that stays current when the agent re-runs.
- host Host a private client demo site, no login, no deploy Put a demo in front of a client as one private link: unguessable URL, optional passcode or email gate, your own domain, updated in place as the build moves. No client accounts, no staging server.
- workflow White-label client reports on your own domain Send client reports under your own name: your domain in the link, no vendor badge on paid plans, your title in the unfurl. Two DNS records, automatic SSL, and per-recipient links that record opens.
- workflow Send a deck as a link, not a 40MB attachment Publish the deck as a page: full-screen slides in the browser, arrow keys, one private link. No export, no fonts breaking on their machine, and you can see whether the board read it before the meeting.
- workflow The client feedback loop: comments on the page, closed in place Your client selects the words, or clicks the image, chart or moment in a video, and comments on the page itself with no account. One email a few minutes later, the fix goes to the same link, and the client sees each comment resolved. Free on every plan.
- host How to host a dashboard your AI agent built An AI agent builds a dashboard as HTML, but HTML is not a link. How to host an agent-built dashboard on a private URL that opens without an account and expires on its own.
- workflow ChatGPT Sites custom domains, explained ChatGPT Sites supports custom domains, where available: connect an apex or subdomain you own by updating DNS records. Which plans get it, the documented limits, and the gated own-domain route for client work.
- share Share Jupyter notebooks as private HTML Export your Jupyter notebook to HTML, publish to Stacktree, lock the link to your team. Plots and interactive widgets render exactly like in the notebook.
- host Host Storybook privately (without Chromatic or GitHub Pages) Run storybook build, upload the static folder, gate the link to your @yourco.com email domain. No CI pipeline, no Chromatic minimum tier, no public-by-default Pages URL.
- share Share architecture diagrams as HTML Mermaid, D2, Excalidraw, and hand-coded SVG diagrams all render as HTML. Stacktree hosts the file behind a private link your reviewers open without logging in.
- host Host AI-generated reports on a private URL Your agent writes a perf report, a research summary, a status doc. Stacktree puts it behind one private URL the agent replaces in place every time it re-runs.
- workflow Internal tool hosting for one-off HTML utilities Agents are writing single-file tools — JSON shapers, log filterers, regex testers — every day. Stacktree is where they live without becoming a full repo.
- workflow Can you export a site from a website builder? Mostly no Framer, Squarespace, and Wix offer no HTML export; Webflow's is paid and drops CMS. Mirroring the published site works for all of them. One skill automates it.
- workflow Can you export a Webflow site for free? Yes, mirror it Webflow code export needs a paid Workspace plan and drops CMS content. Mirroring your published site captures everything. A free Claude Code skill automates it.
The common shape
Every use case on this page shares a few traits:
- Single-file HTML. Self-contained. No backend, no build step at view time.
- Private audience. A team, a stakeholder group, a single recipient. Not the public web.
- Iterative. The author (human or agent) revises the artifact. The URL needs to survive revisions.
- Short to medium life. Hours to months, occasionally years. Not "forever in Git."
How to pick the right use-case page
- The artifact is a notebook → Share Jupyter notebooks
- The artifact is Storybook → Host Storybook privately
- The artifact is a diagram → Share architecture diagrams
- The artifact is a report → Host AI reports
- The artifact is a Claude conversation output → Share Claude artifacts
- The artifact is a single-file tool → Internal tool hosting
- The artifact needs a review round-trip → The client feedback loop
- The artifact should not outlive being read → One-time view links
Frequent questions
What kinds of HTML do teams typically publish to Stacktree? +
Six broad categories: (1) Jupyter notebook exports, (2) Storybook static builds, (3) architecture diagrams (Mermaid/D2/Excalidraw), (4) AI-generated reports (perf, research, status), (5) Claude artifacts moved off claude.ai, (6) single-file internal tools (JSON viewers, regex testers, payload inspectors). Each has its own page below.
Is there a use case Stacktree isn't a good fit for? +
Yes — anything dynamic (serverless backends, database-backed apps), anything that needs to be publicly indexable as a marketing page, anything that has to live forever versioned in Git, or anything that needs sub-50ms TTFB under viral load.
Can I see real examples? +
Each use-case page links to a representative live example. The pattern is always the same: a single HTML file, a private URL, optional gating.
Do the use cases work without an agent? +
Yes. Humans can upload via the dashboard or
curl; the agent path is more convenient but never required. The MCP integration is one possible client; the HTTP API is the underlying surface.Sources and further reading
Find your use case. Publish in 60 seconds.
Each page has the exact workflow. Pick yours above.
Sign up free →