Back to docsWhat Zero delivers

Hosted sites

Publish Zero's HTML output to a public URL you can share.

Last updated July 30, 2026 · 3 min read

Zero can publish static HTML output to a public URL you can send to anyone — no deploy pipeline, no hosting account, no repo. A file on Zero's machine isn't something your colleagues can open; a hosted page is.

Available on every plan, Free included.

What it's for

  • Decks and reports. A generated presentation or metrics report becomes a link you drop in Slack instead of a file people have to download.
  • Landing pages and microsites. Launch pages, event sites, campaign one-offs.
  • Internal hubs. Onboarding pages, runbooks, dashboards for a team that doesn't want another tool.
  • Interactive demos. A prototype someone can click through before you build it for real.
  • Anything an automation produces on a cadence. A weekly report that always lives at the same URL is easier to bookmark than a weekly attachment.

How it works

Ask for it: "Publish this as a page I can share." Zero builds the static bundle, publishes the directory, and replies with the URL.

Details worth knowing:

  • A site has a slug. The slug determines the URL. Publishing to the same slug again ships a new version to the same address — which is what you want for a recurring report.
  • Versions are immutable. Every publish is retained as its own version, so a bad update can be identified and replaced rather than mourned.
  • Single-page apps are supported. Sites built with client-side routing serve unknown paths from index.html so deep links resolve.
  • Existing sites can be edited. Zero can pull a published site back down, change what needs changing, and republish — you don't have to regenerate from scratch.

Practical notes

  • The URL is the deliverable. A local file path or a dev-server address on Zero's machine isn't reachable by anyone but Zero. If someone needs to see it, it needs a hosted URL, a message, or a file export.
  • Hosting is for static output. Pages, decks, reports, and client-side apps work. Anything that needs a live backend, a database, or a background worker belongs in your own deployment pipeline.
  • Assets should be real files. Bundle images alongside the HTML and reference them by relative path rather than inlining them, so they render reliably once published.
  • Public means public. Anyone with the link can open the page. Don't publish anything you wouldn't put in a shared channel — for private material, deliver to Notion, a Google Doc, or a DM instead.

What's next