Revdoku vs here.now
Revdoku and here.now both turn a folder of static files into a live website and both let you try a public 24-hour preview without creating an account. The main difference is the agent workflow: Revdoku offers a local client plus a hosted OAuth MCP server, while here.now documents its skill and API workflow.
This comparison uses the public Revdoku and here.now documentation checked on August 14, 2026. Limits and interfaces can change, so verify the linked documentation before choosing a host for an important project.
Quick comparison
| Capability | Revdoku | here.now |
|---|---|---|
| First publish without an account | One public 24-hour preview | Public 24-hour preview |
| Permanent website | Claim the preview with a free account | Sign in and keep the site on a free account |
| Free account storage | 5 GB total | 10 GB total |
| Free account site limit | Up to 100 published websites | Up to 500 sites |
| Update the same URL | Yes, by reusing the website or bound folder | Yes, by updating the existing site |
| Password access | Supported | Supported |
| Email-based access | Require Email access is supported | Restricted access is documented |
| Analytics in the free account | Not included | Not included |
| Custom domain in the free account | One website | One domain |
| Agent connections | Local client, AI skill, hosted MCP with OAuth, HTTP API | AI skill and HTTP API |
| Static hosting | Yes | Yes |
Choose Revdoku when
- Your agent connects through a hosted MCP server with browser-based OAuth.
- You want the same website available to Claude, Codex, ChatGPT, OpenClaw, and other compatible clients.
- You need Public, Password, or Require Email access.
- You want to publish a local folder with binary assets through a dedicated client.
- You want an anonymous preview that can be claimed without changing its URL.
Choose here.now when
- Its larger documented free storage or site count is the deciding factor.
- You already use its publishing skill or API.
- You want its documented site workflow and do not need Revdoku’s hosted MCP connection.
Same-URL update workflow in Revdoku
- Publish a folder with
revdoku p path/to/site. - Save the returned website URL and claim link.
- Claim within 24 hours if the website should remain online.
- Edit the original folder.
- Publish that bound folder again.
- Reload the original URL and verify the update.
For AI-client setup, see the Revdoku MCP website-publishing guide.
Bottom line
Both services are designed for fast static publishing. here.now documents higher free storage and site-count limits. Revdoku is the stronger fit when access controls and a hosted multi-client MCP workflow matter more.