OpenClaw.NET

The deciding trait is that it is a whole runtime rather than a library, and it is written in the language your services already use. You get a chat interface, an administrative view and a gateway, all self-hosted, without adding a second language and a second deployment pipeline to a team that did not ask for either.

You are the wrong buyer if nothing else you run is .NET, because then you are inheriting a toolchain for no reason. Pick it if the rest of your estate matches. Pick something in Python if it does not.

Read the word passive. Contracts, the ledger and the safer execution mode ship switched off, which means the install most people run is the one without them, and the feature list describes a configuration nobody is in. This is the pattern where a product is safe in the specification and permissive in practice, and the gap is discovered by the first person who did not read the page.

What it does right is refuse outbound requests to loopback and private hosts by default. One control is on, and it is the correct one.

1. The verification design is unusually explicit for this category: high-risk operations can be routed through a mode that plans, executes and then checks, which makes intent, action and outcome three separate recorded things rather than one narrative. 2. Evidence bundles give that record a shape somebody other than the author can read.

2. A regression suite for the harness itself is shipped and runnable, which is the closest thing to a published evaluation on this row, and it measures the tool rather than the model.

492 stars, no company, and a product defined by its relationship to a project it says it is not affiliated with. Derivative positioning gets you found and it caps you, because the reference point keeps moving and you are always described in somebody else's terms.

The asset is the ecosystem. Being the credible option for teams committed to one platform is a genuine position, and that platform's users are chronically underserved by this market. Moat: language affinity. Likely acquirer: a platform vendor wanting an agent story. Position: adopt if you are in that ecosystem, and watch who else enters it.

Two details make this more adoptable than most of its neighbours. There is an administrative interface, so configuration is a place rather than a folder on each laptop, and setup runs non-interactively, which means my configuration management can install it the way it installs everything else.

What is missing is identity. No SSO, no SCIM, no audit log, so sixty installations produce sixty unlinked histories and I cannot answer who asked for what. Zero licence cost, provider spend uncapped. Approved with conditions: central configuration, and a spend limit per key.

The embedded mode is the detail that decided it. Rather than telling me to run a server and point at it, the runtime supervises a local model in a sidecar it manages, so the offline case is a first-class path instead of an exercise. Ollama works too, for when I want my own stack.

MIT, MCP consumed and served, and OpenAI-compatible endpoints exposed by the gateway, which means the things I already wrote can talk to this and it can talk to them. Ahead-of-time compilation makes it start like a binary rather than a platform.