PocketClaw follows the security of self-hosted AI tools. It tracks the CVEs of the agents, model servers and AI apps people run on their own machines, reads the advisories and the patches, and writes down what each one changes for the people who run them. One developer writes it; every figure links to where it comes from, and an opinion is labelled as one.
How it started
In late 2025 the project was an attempt to run a full AI agent gateway around the clock on a Moto E2, a 2015 Android phone with 1 GB of RAM. It took 57 separate workarounds, each written up in the guides, to get an unmodified OpenClaw gateway answering on Telegram and Discord. The hardware notes from that period are archived under /app.
Then OpenClaw became one of the most exposed tools on the internet. On 9 February 2026 The Register reported more than 135,000 OpenClaw instances reachable from the internet, by the count of SecurityScorecard's STRIKE team. CVE-2026-25253 let a single link hand an attacker the token of your gateway. A few days later its creator, Peter Steinberger, joined OpenAI and the project moved to a foundation. The full sequence, with sources, is in the OpenClaw timeline.
By spring 2026 the write-ups were more useful than the phone. PocketClaw became a publication, and then a CVE tracker.
What we publish
- The CVE tracker. Every 6 hours the site reads NIST NVD, CISA's Known Exploited Vulnerabilities catalog, the CVE records and GitHub's reviewed advisories for the components it follows, and sets the affected and fixed versions side by side. The methodology says how a CVE is tied to a component and which source a page follows when they disagree.
- Breakdowns. When a batch of CVEs lands on one tool, a guide reads the advisories and the patches: what the attacker needs, the fixed versions, and the settings that matter more than the patch.
- Agent comparisons. OpenClaw, Hermes Agent, Nanobot, NanoClaw, IronClaw, ZeroClaw and Moltworker, compared on setup, security model and defaults from their documentation, their code and their advisories. We publish no scores from a test suite; where a verdict is our opinion, the page says so.
- Migration and hosting notes. Moving from OpenClaw to Hermes Agent, or from a managed service to your own server, from the projects' own docs; hosting and API costs from the providers' published prices.
Editorial rules
Sources, not impressions. A figure links to where it comes from: NIST NVD, the vendor's advisory, the project's repository, a published price. What we have not run ourselves is not presented as a test, and an estimate is labelled as one.
Security first. A comparison starts with the defaults: authentication, bind address, sandbox, approvals. A setup that runs tools without authentication out of the box gets said plainly.
The boring answer is allowed. Often it is “put it behind Tailscale and update it.” Sometimes it is “do not self-host this one.”
Disclosed money. Partner links go through /go/ and are listed on the disclosure page. No one pays to change a comparison.
Corrections in the open. When a page was wrong, it is fixed and the correction is dated on the page.
Who is behind it
PocketClaw is written and built by Robin Monteiro, a developer in Dijon, France. It is published by Go To Agency SAS, the company he runs (details in the legal notice). The site runs on Next.js and PostgreSQL on servers in Germany, sends email through Amazon SES and takes payments through Stripe.
How it is paid for
- Pro (€9 a month or €49 a year, 7-day free trial): you pick the components you run and get an email, and optionally a Discord or Slack message, when a new CVE lands on one of them. Unlimited full scans are included. See pricing.
- Scan packs (from €1.99 a scan): full StackScanner reports without a subscription.
- Partner links on a short list of tools, disclosed on the disclosure page.
The tracker, the CVE pages, the guides and the scanner preview are free and need no account. The site shows no display ads and publishes no sponsored articles.
Why “PocketClaw”
The name comes from the 2025 project: pocket-sized hardware, and the claw of OpenClaw's lobster mascot. The URLs were indexed and readers knew the name, so it stayed when the focus moved.
Get in touch
Email [email protected], reply to a newsletter, or write to @Pocket_claw on X. Corrections, missing CVEs and tools we should follow: see contact.
See also: changelog, roadmap, pricing, newsletter.