A Tiiny Host alternative for agent-made HTML.

Where Tiiny Host is great

Tiiny Host has been around for years and does the drag-and-drop static-host thing well. If your workflow is "I have a built HTML file on my laptop and I want a link to send my client this afternoon," Tiiny Host is fine. It's particularly strong for one-shot prototypes, simple SPAs, and the kind of static landing page you'd otherwise stuff into Netlify.

Where the model breaks for agents

Three things start to hurt the moment an agent is involved:

1. The unit is "a file you uploaded," not "a tool an agent called." An agent has to drive a browser, simulate file selection, and wait for the redirect. That's a script that breaks every time the dashboard ships a UI tweak.
2. Replacing the file changes the URL. If your agent iterates on the same artifact ten times, you get ten URLs. Your teammate's bookmark is stale before they open it.
3. Private-by-default is a paid bolt-on, not the basic contract. Stacktree treats the unguessable URL as the default and layers password + email-gate on top. Tiiny Host gates the unguessable URL itself behind upgrade screens.

Two limits worth checking before you build against their API

Both of these are on Tiiny Host's own pricing and API documentation, and both decide whether an agent workflow is possible at all rather than merely awkward.

• The API starts at a paid plan, behind a key a human makes by hand. Their documentation states the API is available on Solo plans and above — £10 a month at the time of writing — and the key is generated from the account dashboard. So an agent cannot start: somebody has to sign up, pay, and paste a credential before the first call. Stacktree's first publish is a single unauthenticated request with no key and no account: curl -X POST https://api.stacktr.ee/sites -F file=@page.html. The response carries a claim token that doubles as a keyless update credential, so an agent can keep one URL current without ever holding an account.
• Projects are capped, and the cap is low for agency work. Their Pro plan, the one described as being for freelancers and agencies, allows 15 active projects. An agency with thirty clients runs out. Stacktree caps activated client spaces rather than pages, and filing work under a client is free on every plan including the free one.

Where they are straightforwardly better: their free tier keeps a link online indefinitely as long as you log in once a quarter. Ours expires a free page after seven days. If a permanent free link is what you need and none of the above applies to you, take theirs.

How Stacktree differs, concretely

• MCP-native. Install once with npx stacktree-install — covers Claude Code, Cursor, Codex, OpenCode and Amp — and your agent can call publish_html directly.
• Replace-in-place. update_site swaps content under a stable URL. The same primitive that makes a Notion page useful — bookmark it once — applied to agent output.
• Three gating layers. Unguessable URL, shared passcode, email-domain gate. Every plan gets the first; the passcode and the gate start on Solo at $19 a month.
• CSP by default. Agent-generated HTML is executable code — a careless <script src> can exfiltrate session data. Stacktree applies a sensible Content-Security-Policy out of the box so you don't have to think about it.
• No-builder, no-DNS. Stacktree never asked you to "configure a site" or wire DNS for an unlisted URL. The URL exists the moment the tool call returns.