Ollav vs. generic static hosting
Any static host can put an HTML file on the internet: a bucket with a CDN, a git-based deploy platform or a pastebin for HTML. If you just need the file online, use one. This page is about what changes when the goal is getting the file reviewed.
Side by side
| Generic static host | Ollav | |
|---|---|---|
| Hosting a single HTML file | Yes | Yes, up to 15 MB |
| Multi-file sites, custom domains, server functions | Usually yes | No: one self-contained file, no server code |
| Comments on the page | Not built in; add a widget or collect elsewhere | Built in, pinned to elements, with reactions and resolving |
| Versions at a stable URL | Depends on the platform; often a new URL per deploy | Every version at the same link, earlier comments kept |
| Who can view | Usually public, or a password per site | Workspace, link (signed-in) or public, per document; guests for single documents |
| Untrusted HTML isolation | Your site is the origin | Served from a separate origin that never sees Ollav credentials |
| Agent API | Deploy APIs and CLIs | REST + MCP built around share → comment → new version |
| Search indexing | Indexed unless you configure otherwise | Documents are noindex |
| Data residency | Depends on the provider and plan | Stored in the EU |
When a static host is the better choice
- You're shipping a production site, not a prototype.
- You need multiple files, a custom domain or server-side code.
- You want it public and indexed.
When Ollav fits better
- The page is a prototype, mockup or generated report and the point is feedback.
- Reviewers include people who shouldn't need a git account or a deploy preview login.
- An AI agent produces the HTML and should also handle the feedback.
- Documents should be private by default and stay out of search results.