Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for self-hosted AI agent users, Hermes (hermes-webui) operators, AI agent power users, and iPhone-first builders who want a native mobile cockpit for the agent that lives on their own hardware — the phone is the control plane, not the compute plane, so the agent, its tools, and the data stay on the user's own machine and the iPhone is a free, native, no-tracking front-end to it.
Who should use it
Who should skip it
Consider uzairansaruzi/hermex lower priority if you already have a working solution in this category.
About this signal
uzairansaruzi/hermex is tracked by RepoRadar as a ios cockpit for self-hosted herm in the AI Agents section. It was first seen on 2026-07-03 and last updated on 2026-07-03. The current verdict is 'try now' with a Silver tier and easy setup difficulty. Across RepoRadar's eight signals, uzairansaruzi/hermex is strongest on workflow potential (9.4) and setup ease (8.8) and weakest on maturity (5.8) — a profile worth weighing against your own priorities. 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 uzairansaruzi/hermex a composite score of 7.9 out of 10, placing it in the Silver 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 1.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 iOS 18+ requirement means older iPhones cannot install the app — verify the user's device is iOS 18+ before recommending; the App Store badge in the README is the canonical reference for the current minimum requirement; The app talks only to the user's hermes-webui server, but the server still has its own threat surface — the user is responsible for the server's TLS, auth, and rate-limiting posture. The README's 'Privacy' framing ('No analytics, no tracking, no third-party relay — the app talks only to your server') describes the iPhone-to-server link, not the server's broader posture; for production deployments, review hermes-webui's own security model and front the server with a reverse proxy that enforces TLS, auth, and rate limits; The Swift 5.9+ / iOS 18+ baseline is the right 2026 shape, but it is also a real constraint for users on older hardware — for those users, the only path is to use a web client against hermes-webui directly. The README does not ship a fallback path; for older iPhones, the hermes-webui web UI is the right substitute.