China Claw Products Guide
A guide to China’s Claw product landscape, including OpenClaw wrappers and self-built domestic competitors.
Two camps define the market
The Orange Paper separates China’s “Claw products” into two broad groups:
- products built on top of OpenClaw
- products built independently with their own agent framework
That distinction matters more than branding, because compatibility and update speed differ a lot.
OpenClaw-based wrappers
These products inherit part of the OpenClaw ecosystem:
- they can be easier to deploy
- they may reuse community knowledge
- they may stay compatible with some OpenClaw patterns
But they also inherit upstream lag and security exposure when upstream issues appear.
The Orange Paper highlights examples such as MaxClaw, AutoClaw, QClaw, KimiClaw, and ArkClaw.
Self-built domestic products
These products usually trade compatibility for tighter integration with their own stack:
- deeper vendor ecosystem alignment
- more productized onboarding
- less direct compatibility with ClawHub or OpenClaw internals
The tradeoff is that they become their own ecosystem, not an extension of OpenClaw’s.
How to choose
Choose an OpenClaw-based wrapper when:
- you want lower setup friction
- you still care about OpenClaw ecosystem compatibility
- you accept some lag behind upstream releases
Choose a self-built product when:
- you want tighter vendor integration
- you care more about product polish than upstream compatibility
- you do not need the OpenClaw ecosystem directly
The practical warning
Do not assume “Claw” in the name means the same architecture, same security posture, or same compatibility story. The Orange Paper treats that assumption as one of the easiest ways to misunderstand the market.
Where to go next
- Read OpenClaw Alternatives
- Read OpenClaw vs Claude Code
- Return to the Compare Hub