# Kai vs Secure-OpenClaw

> Side-by-side comparison of two projects in the OpenClaw ecosystem.

Canonical HTML: https://shelldex.com/compare/kai-vs-secure-openclaw/
JSON: https://shelldex.com/api/compare/kai-vs-secure-openclaw.json

| Field | Kai | Secure-OpenClaw |
| --- | --- | --- |
| Tagline | OpenClaw alternative in your pocket | Security-hardened OpenClaw by Composio |
| Language | kotlin | typescript |
| Status | active | active |
| Stars | 784 | 1.2k |
| Forks | 103 | 168 |
| Open issues | 40 | 4 |
| License | Apache-2.0 | MIT |
| Last commit | 2026-05-15T16:49:30Z | 2026-05-08T01:24:30Z |
| 7d growth | 64 | -2 |
| MCP support | no | yes |
| Requires LLM | yes | yes |
| Platforms | mobile | server, messaging |
| Categories | mobile, lightweight | security, messaging |
| Health score | 70/100 | 60/100 |
| Leaderboard rank | #28 | #25 |

## Key differences

- Secure-OpenClaw leads in stars (1.2k vs 784), though both have substantial communities.
- Kai is growing faster with +64 stars this week vs +-2 for Secure-OpenClaw.
- Kai is written in Kotlin while Secure-OpenClaw uses TypeScript, which may influence your choice depending on your stack.
- Kai uses the Apache-2.0 license while Secure-OpenClaw uses MIT.
- Secure-OpenClaw has MCP (Model Context Protocol) support while Kai does not.
- Secure-OpenClaw advertises 500+ built-in integrations.

## Descriptions

### Kai

A mobile-first OpenClaw alternative built with Kotlin Multiplatform and Jetpack Compose. Runs on Android and iOS with any OpenAI-compatible endpoint. The first mobile-native entry in the OpenClaw ecosystem.

### Secure-OpenClaw

24/7 AI assistant on WhatsApp, Telegram, Signal, iMessage with full tool access, persistent memory, and 500+ app integrations