What it does
5 features
IronClaw · Self-hosted personal agent
Product and access
IronClaw is listed as a separate product profile.
Core features
5 features from provider sources · checked on 16 October 2026. Availability and limits are listed below.
Usable AI models
Open choice
You can choose from more than twenty providers, including NEAR AI as the default, OpenRouter, Ollama and an OpenAI-compatible endpoint, and store the key as an environment variable. In a shared workspace, users pick only from the list an admin has approved for the active provider.
Model families named
- Anthropic (Claude)
- OpenAI (GPT)
- Google (Gemini)
- DeepSeek
- Mistral
- MiniMax
- Z.ai (GLM)
- Alibaba (Qwen)
- Other models can be connected freely
- Model choice
- You choose
- Your own API key
- Yes
- Router or custom endpoint
- Yes
- Local models
- Yes
- Depends on
- Admin approval
The rating covers the generally available main access. Documented · Sources accessed on
Does it fit my task?
2 practical tasks · 3 requirements and limits
A good fit if …
- you want to run an agent on your own hardware with locally stored data and no telemetry
- you want routines triggered by cron, events or webhooks and reachable via Telegram or Slack
- you want to grant tool rights one by one and inspect source code under Apache-2.0 or MIT
Less suitable if …
- you expect a managed service with an admin console and several users; the description says nothing on this
- you do not want to set up and maintain a database, services and model access yourself
Editorial assessment based on provider documentation. Not a product test.
Practical tasks
Editorial examples based on documented features. No product tests performed.
Try a webhook routine
- Your input
- A test event and an allowed follow-up action.
- Possible result
- A logged execution of the routine.
- What to check
- Check content, permissions and actions taken.
Find stored knowledge
- Your input
- Approved notes and a specific question.
- Possible result
- An answer based on stored context.
- What to check
- Record time spent, corrections and costs.
Try a webhook routine.
Your possible prompt
Organize these shared documents by topic. Create an overview with deadlines and next steps. Prepare draft replies for my approval.
Adjust the task, data and permissions.
Requirements and limits
Can I use it?
With requirements
Europe & regional availability
Installation instructions and model prerequisites reviewed. The assessment covers the local operating path described; complete country and feature availability of all connected services remains open.
Reviewed scope: Local software and documented self-hosting; external services assessed separately
Reviewed on:
With requirements
Self-hosting with own model access
IronClaw documents local installers and setup with a chosen LLM provider and API key. The web UI is self-hosted; models and installed channel extensions need their own access.
Region, reason and source
Region covered: Europe: own computer or server; model services are country-specific
Documented reason: Technical assessment based on installation and provider selection. These sources do not establish a legal cause for regional restrictions.
Accounts & permissions
Based on provider documentation. Permissions depend on the account, integration and organization policies. Review the permissions actually requested before use.
Configuration covered: Self-hosted IronClaw instance on your own machine or server
Sources reviewed:
Show all 3 points
Documented
Account used
Onboarding creates a login token for the web UI, which can be rotated. The model provider credential is kept in an encrypted local secret store, and secrets are not exposed to tools according to the description.
EvidenceOpen in reviewed sources
Admin approval
No organisation or admin approval is described; the project presents itself as a personal assistant. Rights of individual WASM tools are opted into explicitly.
EvidenceDocumented with conditions
Data access & team sharing
Data is stored locally, with no telemetry according to the project. Tool HTTP access is limited to explicitly approved hosts and paths. The reviewed page does not say whether several users are supported.
Evidence
Memory and conversation continuity
2 of 6 criteria documented
Persistent documents are used through hybrid search and explicit write tools.
Workspace memory and memory tools
Sources accessed:
Documentation by criterion
StoragePartly documented
Storage and scope
Memory stores documents under virtual workspace paths with a search index; the inspected guide names no backend type.
SelectionDocumented
Selection and timing
Instructions require retrieval before questions about the past and saving useful summaries at task completion.
Edit & deletePartly documented
Inspect, edit and delete
Tools read, search and overwrite documents; a deletion tool is not listed among the four described tools.
Access boundariesPartly documented
Agent and channel boundaries
Documents remain in the workspace across sessions. Fine-grained user, project and channel access boundaries are not described there.
RetrievalDocumented
Retrieval
Hybrid search combines full-text and vector search; documents can also be read by known paths.
New conversationsPartly documented
Session reset and compaction
Workspace documents remain persistently available across sessions. The guide describes no specific relationship with conversation compaction.
Cost and effort
Prices as of 16 October 2026
Prices and included usage
Pricing checked
Open source; model and operating costs are separate.
- Total cost depends on access, usage and configuration.
Setup
Run the installer and configure a model provider.
Operation & oversight
Based on public provider documentation. Assessments are editorial inferences from the stated properties. Actual time requirements and reliability have not been measured.
Deployment covered: Self-hosted instance running as a background service
Sources reviewed:
Editorial assessment
Since you run it yourself, the database, updates and backups are your responsibility. Per-action approval and failure alerts are not settled in the description.
Show all 6 points
Documented
Files and working state
State lives by default under $HOME/.ironclaw/reborn. PostgreSQL or SQLite are named as storage; search combines full-text and vectors. Retention and backup are not described.
EvidenceOpen in reviewed sources
Sign-ins
The reviewed page mentions rotating the web login token but gives no expiry times and no behaviour when a sign-in expires.
EvidenceDocumented
Starting further runs
Routines start by cron schedule, event or webhook. A heartbeat handles proactive monitoring and maintenance. On macOS and Linux a background service runs.
EvidenceOpen in reviewed sources
Human intervention
Whether people must confirm tool calls beforehand is not described. Policy rules have severity levels such as Block, Warn, Review and Sanitize, but no review workflow is described.
EvidenceDocumented with conditions
Detecting errors
A full audit log of tool executions and a logs view in the web UI are mentioned. Format, retention and failure notifications are not described.
EvidenceDocumented with conditions
Resuming after failures
The page lists automatic detection and recovery of stuck operations. How jobs are resumed or retried is not stated; configuration changes need a manual service restart.
Evidence
Evidence and open questions
1 source · 2 open points
Open points
The reviewed sources contain no reliable information on these points. A gap says nothing about the product.
Requirements and limits: not yet confirmed
Sources and evidence
Provider sources reviewed; examples are editorial. No hands-on tests.
Editorial team: Michael Meierhoff · sources reviewed on . Provider information is not independent evidence of performance.
Provider
Publishes IronClaw and the linked product information.
- Operator
- NEAR AI
- Organization
- Open-source project
- Website
- github.com
Changes to this profile 1
Added IronClaw with capabilities, sources, pricing and open European availability questions.
These notes describe editorial changes. Source and pricing review dates appear in their respective sections.