Will OpenClaw Win?

OpenClaw has spawned thousands of competitors and copycats: OpenClaw for enterprise, OpenClaw but in Rust, multi-tenant OpenClaw, OpenClaw for SDRs, etc.

Before we decided to build an OpenClaw hosting service, we asked ourselves whether we thought this tech would be around in two years. It’s 2026: software is cheap and changes fast.

The best tech does not always win. JavaScript was written in ten days. The standard library is horrible. Numerous bad decisions live forever to maintain backward compatibility (e.g. [] + {} === "[object Object]"). The type system is a mess; to deal with it one has to write TypeScript and then transpile it.

The ecosystem kludged around these flaws until the kludges became engineering marvels themselves. Node, Bun, npm, ESLint, and React are default choices and beloved parts of our stack. LLMs are exceptionally good at using them.

I have my issues with OpenClaw. There’s too much configuration. It’s too easy to write bad configs. It’s Mac-centric.

But it’s going to win. There are over 20k skills on Clawhub, some with hundreds of thousands of downloads. OpenClaw has 500+ contributors that collectively shipped over 200k lines of code last week, and it’s still at almost 2mm weekly downloads. Many of the add-ons I write to make Klaus better become a part of the core OSS almost immediately after I ship them.

If you’re writing software from scratch that’s designed to compete with OpenClaw, you’d better have a good plan for matching its pace and benefitting from its ecosystem.