IronClaw: Dual MIT/Apache-2.0 Secure Personal AI Assistant / Agent OS (Privacy-First, Auditable, Extensible)

Score8.5

Popularity0.0

Risklow

TierGold

Score breakdown

Usefulness9.0

Novelty8.0

Momentum8.0

Maturity6.6

Open-source/build8.4

Evidence7.2

Workflow potential9.6

Setup ease8.8

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Most end users today who want a personal AI assistant have been either (a) using closed SaaS like ChatGPT / Claude.ai / Gemini that exfiltrate the user's data to a third-party cloud, or (b) running command-line llama.cpp + a hand-wired chat UI that requires Linux-fu. nearai/ironclaw inverts both patterns: a single dual MIT/Apache-2.0 secure personal AI assistant / Agent OS, with on-device-by-defau

Who should use it

End users who want a private on-device personal AI assistant without the privacy cost of closed SaaS + developers building privacy-first AI applications + security-conscious users who need an auditable agent surface + multi-language users (English / zh-CN / ru / ja / ko) + any developer wanting a dual MIT/Apache-2.0 secure personal AI assistant / Agent OSEnd users + on-device-by-default users that want the privacy-first architecture (all data lives on-device by default) -- the right on-device-by-default primitive for any end user who has been paying the privacy cost of closed SaaSEnd users + auditable-agent-surface users that want the security-first model (agent surface is constrained and auditable) -- the right auditable-agent-surface primitive for any end user who has been worried about an AI agent exfiltrating credentials or session cookiesEnd users + extensibility-first users that want the user-pluggable LLM providers / tool surface / data sources -- the right extensibility-first primitive for any end user who has been locked into a single vendor's LLM providerEnd users + 5-install-surface users that want the 5 install surfaces (prebuilt binary + Homebrew + Docker + cargo install + source build) -- the right 5-install-surface primitive for any end user who has been fighting install scriptsEnd users + 4-language-README users that want the 4-language README (English / zh-CN / ru / ja / ko) -- the right 4-language-README primitive for any multi-language user who has been blocked by English-only documentation

Who should skip it

Skip IronClaw: Dual MIT/Apache-2.0 Secure Personal AI Assistant / Agent OS (Privacy-First, Auditable, Extensible) unless the captured evidence suggests it solves a problem you are actively working on.

About this signal

IronClaw: Dual MIT/Apache-2.0 Secure Personal AI Assistant / Agent OS (Privacy-First, Auditable, Extensible) is tracked by RepoRadar as a tool in the Radar section. It was first seen on 2026-07-08 and last updated on 2026-07-08. The current verdict is 'try now' with a Gold tier and easy setup difficulty. The standout signals for IronClaw: Dual MIT/Apache-2.0 Secure Personal AI Assistant / Agent OS (Privacy-First, Auditable, Extensible) are workflow potential (9.6) and practical usefulness (9.0), while maturity (6.6) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.

How this item is evaluated

RepoRadar assigned IronClaw: Dual MIT/Apache-2.0 Secure Personal AI Assistant / Agent OS (Privacy-First, Auditable, Extensible) a composite score of 8.5 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 0.0 and never affects the composite score or tier. The risk label of 'low' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.

Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.

Risk explanation

The 12506* / 1466-fork / 78-subscriber repo is at active maintenance but the consumer SHOULD note the README's framing 'Your secure personal AI assistant; always on your side' is end-user first; not developer first -- developers can still embed IronClaw via the CLI / SDK surface but the headline value is the on-device personal-AI experience; the consumer SHOULD note the on-device-by-default architecture means the consumer's data stays on the consumer's machine by default.

Evidence links

github.com

Closest alternatives / related signals

open-sourcedual-mit-apache-2-0nearaiironclawpersonal-ai-assistantagent-osprivacy-firstsecurity-first