> Compare Revdoku and here.now for static-site previews, permanent sites, account workflows, access controls, custom domains, analytics, and AI-agent publishing.

# Revdoku vs here.now

Revdoku and here.now both turn a folder of static files into a live website. The
main difference is the account and agent workflow: Revdoku starts with browser
sign-in and offers a local client plus a hosted OAuth MCP server, while here.now
documents an anonymous preview, skill, and API workflow.

This comparison uses the public Revdoku and [here.now documentation](https://here.now/docs) 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 | Browser sign-in, private draft, then explicit publish | Public 24-hour preview |
| Permanent website | Included with a Free account | Sign in and keep the site on a free account |
| Free account limits | Published in Revdoku's live pricing contract | 10 GB total and 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 | Basic analytics | Not included |
| Custom domain | Plan-driven | One domain in the free account |
| 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 a private draft and temporary preview before publishing.

## 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

1. Sign in and preview a folder with `revdoku preview path/to/site`.
2. Review the temporary URL, then publish with `revdoku p path/to/site`.
3. Save the returned main website URL.
4. Edit the original folder.
5. Publish that bound folder again.
6. Reload the original URL and verify the update.

For AI-client setup, see the [Revdoku MCP website-publishing guide](/mcp/).

## Bottom line

Both services are designed for fast static publishing. Revdoku is the stronger
fit when authenticated private drafts, access controls, and a hosted
multi-client MCP workflow matter more.

---

[View the canonical page](https://revdoku.com/compare/here-now/) · [Browse llms.txt](https://revdoku.com/llms.txt)