Nous wants you to own the harness, which means you own the patching too

Switching costs do not disappear in this design; they change owner. Nous Research's own framing concedes the mechanism: model choice gets the attention, while control of memory, permissions, skills and execution history decides how hard it is to leave an agent platform ^[4]. All four of those live in the harness, which is why pointing the runtime at Nous Portal, OpenRouter, OpenAI or a compatible custom endpoint leaves the accumulated context intact ^[6]. Leaving the harness is the expensive move, and Nous has arranged for the harness to be the operator's rather than its own. Forking is available; porting a year of agent state into somebody else's runtime is a different problem, and nothing in the pitch solves it.

The financing makes the neutrality harder to read. TechCrunch reported on July 13 that Nous Research was finalizing at least $75 million led by Robot Ventures ^[12], and separately put hosted plans at $20 to $200 a month ^[11]. At the top tier that is $2,400 a year, so the round is worth roughly 31,250 subscriber-years of the most expensive plan ^[14]. Hermes is the distribution channel for Portal, on a stated mission of unrestricted availability of language models ^[16], and the code treats Portal as one endpoint among several ^[6]. The software does its own paid product no favors. That is consistent, and it is a thin structural moat for the layer that has to earn the revenue.

Then the part with actual labor in it. The runtime is built to stay online, work across communication channels and keep an evolving record of how its operator works, which Nous presents as a broader claim than a terminal coding assistant makes ^[8]. It is also a broader administrative surface than one, and Nous invites the comparison by positioning against Codex CLI, Claude Code, Aider and OpenHands, with OpenClaw as the closest peer and Letta and Block's Goose holding the memory and local-execution slices ^[13]. A managed vendor decides isolation, updates and plugin policy once, centrally, for every customer ^[10]. Self-hosting hands each decision to the deployer, credentials and network exposure and host isolation included, and the deployer is free to get them wrong ^[10].

The plugin review clause is the line to price. A project that shipped in February 2026 and was about six months old on August 24 ^[3] has not accumulated the history a reviewer would need to judge third-party skills against anything but their own reading of the code. So the trade is legible: an asset that survives model vendors, in exchange for the standing job of the security team the operator does not have. For a team that already runs its own infrastructure, that is a fair swap and possibly a bargain. For a team that chose a managed agent because nobody there wants to be on call for a scheduled job with provider credentials, the license fee is the cheapest part of the bill.