# Onlay vs static HTML hosts

> tiiny.host, Netlify Drop, GitHub Pages and surge put an HTML file online. None of them collect feedback. When plain hosting is all you need, and when it is not.

If you just need your agent's HTML file online, a static host does it, often for free. tiiny.host, Netlify Drop, GitHub Pages and surge.sh are all good at that. What none of them do is take comments on the page or hand anything back to the agent.

## Side by side

| | Onlay | Static hosts |
|---|---|---|
| Puts the file online | Yes, at a link that stays the same across versions | Yes |
| Comments and edits on the page | Yes | No |
| Feedback back to the agent | Yes, as a review or JSON | No |
| Indexed by search engines | No: every document is `noindex` and unlisted | Yes, if you want it to be |
| Custom domain | A chosen name on a share link (Pro); not your own domain | Usually yes |
| A page that calls other servers | Pro | Usually yes |

## Choose a static host when

- The page is finished and read-only: nobody needs to comment.
- It should be public and found in search.
- You want your own domain.

## Choose Onlay when

- The page is a draft people should react to, and the agent should get their reactions.
- The link should stay the same through every revision.
- The audience is specific (a team, a client), and the page should stay out of search.

---

This page as HTML: https://onlay.io/compare/static-html-hosts. Everything for agents: https://onlay.io/llms.txt