static hosting · no build step
Host a static site or share an HTML report: drop in a file or a ZIP, get a shareable URL. Keep the link public, password-protected, private to named people, or ask each visitor for an email first — and collect feedback pinned to the page itself.
Drop your single html or zip here
HTML & ZIP
baaa-sically instant
How it works
Three steps, at your pace. Pick a step: the last one you can actually try.
Drag in a ZIP, a folder of HTML, or a single file. No build step, no terminal.
Add the pagegoat MCP server to any AI agent: CLI or web app, from OpenAI, Google or Anthropic. One URL, one approval, done. After that, shipping a page is a sentence.
Trademarks of their respective owners. Named to show compatibility; pagegoat is not affiliated with, endorsed or sponsored by any of them.
one setup, forever hands-off →
Publish the hello-goat html and send me the link.
Drag a file in, or POST one. It is live at its own URL either way.
baaa-sically instant →
not sure which door is yours?
Choose your path
One HTML file or a ZIP, and a link that behaves in Slack.
/use-cases →Public, a password, named people, or an email at the door.
/solutions →Readers comment on the line they mean, not in a thread elsewhere.
#feedback →Open comments re-anchor to the passage they were about.
/docs →A single HTML file, or a ZIP with an index.html plus its CSS, JavaScript, images and fonts. No build step and nothing to install: what you drop in is what gets served. If it runs from your filesystem in a browser, it runs here.
You need an account to publish, and publishing needs a paid plan: Starter at $2.99 a month or Pro at $5.99. A free account can still open pages shared with it, leave comments, and help manage sites it has access to. It just cannot create its own.
Those are built around a git repository and a build pipeline. This is built around a HTML document you already have and a person you need to send it to. The difference shows after the URL exists: a page here can be password-protected or limited to named people without you writing any authentication, and readers leave comments anchored to the passage they mean.
Yes, four ways. Public means anyone with the URL. Password means one shared secret, which you can send separately from the link. Private limits the page to people you name by email, and everyone else gets a not-found rather than a login prompt that would confirm it exists. Capture emails asks each visitor for an email address, optionally confirmed by a six-digit code, before the page loads — and you keep the list. The check runs on the server in every case, so page bytes never reach a browser that has not cleared the gate.
Yes. A reader selects text on the rendered page and leaves a note against that selection, so the remark arrives attached to the sentence it is about. Comments re-anchor to their passage after you upload a corrected version. Threads can be resolved and reopened, permissions are per person, and commenting can be switched off entirely by owner.
Both. Pagegoat runs an MCP server with OAuth, so Claude, ChatGPT, Gemini and any MCP-aware CLI can create a page, replace its contents and set its visibility. You approve once in a browser and no API key is ever typed into a chat. For automation there is a REST API with a published OpenAPI spec: exchange a key for a short-lived token, then POST the file.
People use pagegoat to share a client report, password-protect a static site, require an email to view a link, collect feedback on a report, and publish straight from an AI agent. Explore more use cases and solutions, or write a page in the playground.