Intraface vs here.now
Use here.now when one agent needs files online fast: no account, custom domains, big storage, cheap plans. Use Intraface when several people's agents keep editing the same page. here.now rejects a stale update or lets you overwrite it; Intraface queues publishes and merges edits to different files onto the latest version.
Part of Compare: Intraface and the tools around it, side by side, with what we checked and when.
- here.now in one line
- Instant web hosting for AI agents: files, sites and reports become a live URL at {slug}.here.now docs
- here.now publishing
- Three API calls: POST /api/v1/publish (returns presigned URLs), a PUT per file, then finalize; no MCP server in its docs docs
- here.now stale updates
- The skill sends baseVersionId; if the live site moved, the update fails with version_conflict. You reconcile by hand or re-run with --overwrite docs
- here.now raw API
- An update without baseVersionId is an unchecked full replacement, the default for raw API callers docs
- here.now plans
- Anonymous and Free $0, Hobby $4 a month, Developer $20 a month; anonymous sites expire after 24 hours docs
- Intraface, two publishes to different files
- Both land: from version 3, a style.css edit and an index.html edit became versions 4 and 5
- Intraface, two publishes to the same file
- The first lands; the second returns needs_rebase (HTTP 409) naming the file and who changed it
- Last tested
- 2026-10-26, Intraface: two publishes from the same version: different files merged, same file returned needs_rebase
Side by side
| Intraface | here.now | |
|---|---|---|
| What you publish | One living page per board, edited over time | Any static files, as a site at its own URL |
| How agents connect | Remote MCP server with OAuth, a header token, or the CLI | A skill with publish.sh, or the HTTP API with an hnk_ key |
| Two agents update from the same version | Different files both land; the same file returns needs_rebase | The skill gets version_conflict; --overwrite or a raw API call replaces the site |
| Who can change a page | Board members with contributor rights or above, through their own agents | Workspace members publish and manage their own sites; admins manage everything |
| Comments | Pinned to the page, and addressable to agents | None on sites; Site Data for forms and polls |
| Publishing without an account | No, you need an account. Sign-up is free | Yes, sites expire after 24 hours unless claimed |
| Version history | Every version, with who made it | Every publish is a version you can list, restore or delete (not on anonymous sites) |
Where here.now is better: Publishing with no account, custom and vanity domains with a built-in registrar, password and email-allowlist access, analytics, and big storage on cheap, clear plans.
What each one is
here.now is hosting built for agents. It describes itself as instant web hosting for AI agents: your agent hands over files and gets back a live URL at {slug}.here.now. Publishing is three HTTP calls. You create the publish with a file list and get presigned upload URLs, PUT each file, then call finalize. Updates reuse the same slug. Agents reach it through its skill (which wraps a publish.sh script) or the raw API. There's no MCP server in its docs, OpenAPI spec or skill, and no account is needed for a site that lasts 24 hours.
Intraface is a shared page for a team. Each board is one living HTML page plus its files. Everyone's agent pulls the board, edits locally, and publishes a new version. The board keeps every version with who made it, carries a collab.md with its house rules that every agent reads on pull, and holds comments pinned to the page that people can address to an agent. Agents connect to https://app.intraface.cc/mcp with OAuth, a token in a header, or the intraface CLI.
So the overlap is smaller than it looks. Both turn agent output into a page you can open in a browser. here.now is about getting files online. Intraface is about many people's agents working on the same page over days.
The publish test: two agents, one starting version
We ran this on Intraface on 2026-10-26, on a board called "Publish test: two agents, one page". Two agents started from the same version and published at nearly the same moment.
- Different files. From version 3, one agent changed
style.cssand the other changedindex.html. Both publishes landed, as versions 4 and 5. The second was merged onto the first automatically, so neither edit was lost. - Same file. Both agents changed the same file. The first publish landed. The second came back as
needs_rebase(HTTP 409), naming the file and who had changed it. The agent pulled the new version and redid its edit, and that redo became a version of its own.
Over MCP the merge works per file. If you want line-level merging inside one file, the CLI's intraface pull --merge does a three-way merge on your machine and publishes clean merges for you; otherwise it leaves conflict markers for you to fix.
We didn't publish to here.now. Here is what its docs say happens in the same situation, read on 2026-10-26. Its skill records the live version after each publish and sends it as baseVersionId next time. If the live site has moved on, the update is rejected with version_conflict, naming the live version and what created it. The agent is told to relay that to you and either read the live files and reconcile them by hand, or re-run with --overwrite to replace the live version anyway. A raw API call that omits baseVersionId is, in its own words, an unchecked full replacement, and that's the default for raw callers. There's no automatic merge; reconciling is up to you or your agent.
Where here.now is better
If one agent produces a finished page and you only need it on the web, here.now is simpler and does more around hosting:
- Anonymous publishing with no key, claimable into an account later.
- Custom domains from the Free plan, vanity URLs, and a registrar that sells domains at cost.
- Viewer access by password, an email or domain allowlist, or only you.
- Per-site analytics, SPA mode and proxy routes.
- Clear prices: Free at $0 with 10 GB, Hobby at $4 a month, Developer at $20 a month.
Its workspaces have two roles. In its words, admins manage everything, and "members publish and manage their own Sites" (llms-full.txt). Intraface boards have five roles: owner, editor, contributor, commenter and viewer. Members with contributor rights or above can publish to the board through their own agents; commenters and viewers can't.
Using both together
Draft on an Intraface board while the team works on it. Each person's agent pulls, edits and publishes, comments go to the agent that should act on them, and collab.md keeps everyone's edits in one style. When the page is done and needs its own domain, a password, or analytics, export it and publish that copy to here.now. You get the shared editing where it matters and here.now's hosting features for the finished page.
FAQ
- Is Intraface a hosting service like here.now?
- No. here.now hosts whatever files an agent hands it, at a URL, and it's better at that. Intraface keeps one page per board so a team can go on editing it through their agents, with every version kept.
- What happens on here.now when two agents update the same site?
- Per its skill docs, checked 2026-10-26, the second update is rejected with version_conflict if it was based on an older version. The agent then reads the live files and reconciles by hand, or re-runs with --overwrite. A raw API call without baseVersionId replaces the site unchecked.
- Did you test here.now's conflict handling yourselves?
- No. We didn't publish anything to here.now. The here.now behaviour on this page comes from its skill.md and llms-full.txt, read on 2026-10-26. The publish test on this page was run on Intraface only.
- Can I use Intraface and here.now together?
- Yes. Keep the working page on an Intraface board while the team's agents edit and comment on it, then publish a finished copy to here.now when it needs a custom domain or a password.
Stop sending HTMLover Slack.
Create an account in a minute, connect your coding agent, and make your first board.