A home for the HTML files you (and your AI) keep generating. Drag a file in, get a link — a link you can edit in place, that keeps every version, and tells you how it was read.
"The unreasonable effectiveness of simple HTML." Hacker News, 1,064 points
For the people who never needed React in the first place — and for the AI assistants who keep handing you a single .html file with nowhere to put it.
You asked Claude for a pitch deck and got back a 1.5 MB HTML file. You wrote a one-pager. You generated a dashboard. You exported a PRD as HTML.
Now what? Vercel wants a git repo. GitHub Pages wants a workflow. Drive doesn't render. Email won't open it. You upload it somewhere, share the link, and ten minutes later notice a typo — and the link is already in someone's inbox.
Hostus is the missing layer between I have an HTML and here's the URL.
Open any document you own and the editable parts come alive — headings, paragraphs, table cells, list items. Click. Type. Save. The URL doesn't change. The person you sent it to doesn't know you fixed it.
And every save is kept: a version history you can browse and restore. Ship v2 to the same link — and roll back if v2 was a mistake.
It's how docs should work when the doc is just HTML.
Send a proposal and you get more than a view count. Hostus measures reading time per section — which parts held attention, what got re-read, where people stopped. On email-gated docs, you see it per reader.
Cookieless, like everything here. No IPs stored, no fingerprinting, no creepy pixels, no session replay — just time per section, counted the same way we count views.
The "Reading by section" card from a gated proposal's analytics. Your client saw a document — you see what held them, what worried them, and where they closed the tab.
You ask Claude to generate a pitch in HTML for an investor. You drop it into Hostus, copy the link, paste it into Slack. Six hours later you notice the MRR figure is outdated. You open the doc, click the number, type the new one, hit save. Same link, v2 — the investor reloads and never knows. Next morning you ask Claude how it went: opened three times, most of the reading time on traction. Time to follow up.
That's the workflow Hostus is built around.
Drag any .html into your dashboard — or ask Claude to publish it. Live in under ten seconds, with SSL, a slug you pick, and a link preview you control.
Public link, invite-only, or email-gated — readers leave an email before the doc opens, and you know who opened it, and when.
Open the live URL as owner, click into any text, save. Same link, new version — and every version kept, ready to restore.
Cookieless analytics plus reading by section: what held attention, what got re-read, where readers stopped.
Connected via MCP, Claude finds your docs, updates them by intent, and reads the reaction data to draft the next version — on the same link.
The founder, PM, or consultant who lives between Claude / ChatGPT / v0 and a Slack thread with investors, clients, or co-founders. The person who generates 3–10 HTML artifacts a week — pitches, PRDs, dashboards, mockups — and needs to share them like docs, not deploys.
If that's you, Hostus is built around your exact week.
The web got heavy because we forgot what it was for. Most documents — a one-pager, a pitch, a brief, a report — don't need a build pipeline, a CDN config, a 200KB JS bundle, or a deploy that fails six months later because Node moved on.
They need to load fast, render anywhere, stay accessible by default, and live at a stable URL.
That's HTML. It's been there the whole time.
Hostus is infrastructure for that idea — and for the moment in 2026 where every AI assistant in your life can output one in two seconds.
Connect Hostus to the Claude app and Claude publishes, finds and updates your pages straight from the chat — and remembers them. Eleven tools: semantic search across everything you've hosted, updates by intent ("fix the pricing table"), saving meeting notes as context, and reading how your docs were read. One login — no API key, no terminal:
You'll paste it in the next step.
https://app.hostus.io/api/mcp
In Claude (web or desktop), click “Add custom connector” and paste the URL.
That's it. Ask Claude to publish a page — it lands on your Hostus, with a public link.
Prefer the terminal? claude mcp add plugs it into Claude Code with an API key. There's also a public API — POST /api/v1/documents with a Bearer key — and a Claude Skill.
A real loop, live today: Claude reads the reaction data through hostus_attention and rewrites through hostus_update.
Every account starts with a 7-day free trial — no card required. After that, one product and two billing rhythms. Cancel anytime. Same features either way — the annual plan just gets you a deep discount for committing.
Pay as you go. Switch to annual whenever you want.
Equivalent to $4.17/month. Best value if you're shipping HTML weekly.
Start with a 7-day free trial — drop a file at the top of this page, no card needed. You'll only pick a plan when the trial ends; your links stay live either way.
You don't, really. Drop an HTML file at the top of this page, give us your email, and we send you a magic link. Click it and you're in your dashboard with the doc already there. No password, no separate signup form.
You can upload a build output, but that's not what Hostus is optimized for. The product is built around single HTML files — the kind a person writes or an AI generates. For SPAs, Vercel and Netlify are great.
Tiiny is great for drag-and-drop static hosting. Neocities is a cultural project for personal websites. Hostus is built around editing the live document — same link, in-browser, owner-only — and around the workflow of someone shipping AI-generated HTML weekly. Different shape of problem.
Your files are .html. We make them downloadable. No proprietary format, no lock-in.
Private docs require a magic-link sign-in tied to a grant we issue when you accept an invite. Each document lives on its own isolated subdomain (<id>.v.hostus.io) so even the HTML running on one doc can't see another.
A middle ground between public and invite-only: the viewer types an email before the doc opens, and you see who viewed and when in your analytics. It's consent-based identification — perfect for knowing who opened a pitch — not hard security. For truly restricted access, use a private link with invites.
Time spent per section of your document, anchored to its headings (h1–h6). You see which sections held attention, which got re-read, and where readers stopped — per reader on email-gated docs, aggregated otherwise. It's cookieless: no IPs stored, no fingerprinting, no scroll recordings, no heatmap pixels. Your own visits don't count. Docs without headings don't generate this data.
Eleven tools over MCP: publish and update docs (by intent — "fix the pricing table" works), semantic search across everything you've hosted, read summaries or specific sections, find related docs, save meeting notes as context tied to a doc, and read the reading data (hostus_attention) to suggest the next version. One OAuth login in the Claude app — no API key.
Every new account starts with a 7-day free trial — no card required up front. When it ends, you pick a plan to keep publishing and editing: $9.99/month or $49.99/year. Docs you already published stay live either way.
Viewing works everywhere. The inline editor is desktop-only in v1.
No account first. Drop a file, give us your email, click the link we send.
Drop your HTML ↑