Specs, prototypes, playbooks, dashboards, decision memos, the investor update. You generate three to ten of them a week. Hostus gives each one a stable link, decides who can open it, shows you who read what, and lets Claude update it in place.
One artifact, one link, one place where the reaction comes back.
The spec lives in a chat thread, then in a Slack message, then in three slightly different files. Nobody knows which one is the real one.
One private link per doc. Invite the team by email, or share a whole folder once and every doc you add later is covered. Edit on the same link; every version is kept and restorable. You see who opened it and which section they actually read.
Claude or v0 gave you an interactive screen. A screenshot loses the interaction; a repo deploy is overkill for a Tuesday review.
Drop the HTML and send the link. Buttons, tabs and states work in the browser. Each doc runs on its own isolated subdomain, so a prototype cannot touch anything else. Replace the file when v2 is ready; the link stays.
You send the monthly update as a PDF and learn nothing. Did they open it? Did they stop at Runway?
Email-gate the page. Each investor types an email and you see who opened, when, how long they spent on Traction versus Runway. Fix the MRR figure six hours later without re-sending. Follow up with the two who re-read Ask.
You wrote the sales playbook. Two months later you still do not know if the new hires read past the first section.
Host it private for the team. Reading by section shows which parts get read, which get re-read, and where people give up. Rewrite the weak section with Claude and publish on the same link.
Time per section, anchored to your headings. Per reader on gated docs, aggregated on public ones. Cookieless: no IPs, no fingerprinting, no session replay.
The card from a gated proposal. The same card exists for your spec, your playbook and your investor update.
Goals, flows, risks, open questions. Private for the team, a version per review round.
A screen from Claude or v0 that people can actually click, on its own sandboxed subdomain.
Monthly numbers, wins, asks. Email-gated so you know who read Runway.
A static HTML dashboard regenerated by Claude every Monday, replaced on the same link.
Context, options, decision. Shared with the folks who need to weigh in; you see who did.
Sales playbook, onboarding guide, how-we-work. Read by section, fixed in place.
No export, no reformatting. The artifact Claude wrote is the file you host. Claude can also publish it directly.
Prototypes click, dashboards filter, specs collapse and expand. A PDF is a picture of a document.
Your layout, your brand, your typography. Not a wiki's template.
Public, private with invites, or email-gated with a list or a domain. Revocation takes effect on the next request.
Not "12 views": which section held them, what got re-read, where they stopped. Claude reads it too.
Every doc is a .html you can download. Nothing proprietary.
Twelve tools over MCP: publish and update by intent, semantic search across everything you hosted, reading data (hostus_attention), form responses, saved context. One OAuth login in the Claude app.
Ask Claude for a single-file page, or connect Hostus and say "publish this". Drag-and-drop works too.
Private with invites for the team. Email gate for investors and customers. Public for anything else. Switch anytime.
Who opened, which section held them. Fix in place or ask Claude to rewrite. Same link, new version.
Hostus hosts single HTML files, not React or Next builds, and not PDFs. The link is your-doc.v.hostus.io; custom domains are not available yet. Accounts are individual: you can share folders read-only with your team, but there are no seats or co-editing. The free plan covers 20 docs, 2 MB of HTML and 100 form responses a month, with every feature included; paid plans lift the limits. The inline editor is desktop-only.
To open a private doc, each reader signs in with a magic link, which creates a free account in one click. For lower friction use the email gate: they type an email and the doc opens.
Yes. Connect Hostus as a custom connector in the Claude app. Claude publishes new pages, finds existing ones by meaning and updates them by intent, on the same link.
If it exports as a single HTML file, yes. React builds with a server or a build step are not what Hostus is for.
On an email-gated page, per reader: who opened, when, time per section, what got re-read, where they stopped. Enough to know whom to call and what to rewrite.
Switch the doc to private or remove the email from the gate list. It takes effect on the next request. Media in the doc sits behind the same check.
Free plan, no card. The doc Claude wrote this morning can be live, private and measured before lunch.
