HarnessRouter gives your product one Apache-2.0 API across agent harnesses (Codex, Claude Code, Hermes), so you can switch harness without rewrites.
Yes, HarnessRouter is open source under the Apache-2.0 license.
HarnessRouter has a free tier plus paid plans. The open-source version can be self-hosted with no license cost; you pay only for your own infrastructure.
Yes, HarnessRouter can be self-hosted (the source is available under the Apache-2.0 license).
Apache-2.0 abstraction layer, pitched as an OpenRouter for agent harnesses: one API your product calls to run a task, retrieve the result, and switch between coding-agent harnesses (Codex, Claude Code, Hermes and others) without re-implementing each integration. It handles persistent sessions, file handling and streaming behind that single interface. It is self-hostable via Docker with your own keys and infrastructure, and a managed cloud version exists separately.
The harness, the thing that lets an agent read files, call tools and loop, is becoming the layer teams get locked into, the same way they once got locked into a single model. HarnessRouter does for harnesses what OpenRouter did for models: put one API in front of them so your product can run a task on Codex today and Claude Code tomorrow without a rewrite. For a builder shipping GTM tooling on top of an agent, that is the difference between betting the product on one vendor's harness and keeping the option open. The honest read: this only pays off if you genuinely switch or hedge, the hosted version is where the money is, and every abstraction layer is another dependency to trust. If you are building on agents and do not want to be married to one harness, it earns a look.