OpenWatch
The compliance OS.
A fleet eye, heartbeat, and control plane. Continuous posture, daily snapshots and trends, score-drop alerts, governance workflows, and evidence an assessor can follow, for any team running Linux at scale.
Linux assessment and change tools for the agentic era
Hanalyx builds assessment tools, a control plane, and a spec compiler for assessing and changing Linux with recorded evidence.
“No Linux change should ever be unsafe, unauditable, or unreversible, whether a human or an AI made it. That sentence is our entire company.”
●The portfolio
OpenWatch is the platform. Kensa is the engine. Specter compiles the specs the other two are built from.
The compliance OS.
A fleet eye, heartbeat, and control plane. Continuous posture, daily snapshots and trends, score-drop alerts, governance workflows, and evidence an assessor can follow, for any team running Linux at scale.
The change engine.
Assesses Linux configurations and applies changes through defined mechanisms. A single binary for scripts and pipelines, and the engine OpenWatch runs on.
The spec compiler.
A compiler for specifications: the toolchain we use to build OpenWatch and Kensa, open to anyone who wants machine-enforced spec rigor for their own systems.
Experience across
For AI platform teams
Letting an agent run ssh+sudo on your fleet is unbounded. Kensa offers defined mechanisms with recorded results. Review each plan and its rollback support before an agent applies it.
Evidence
Scan evidence, remediation envelopes, and report exports differ in what they prove. Remediation envelopes verify across runs only when configured with a persistent signing key. Check the artifact and release before relying on a signature. The example shown here illustrates a record; it is not a verified export.
{"schema_version": "v2","transaction_id": "00000000-0000-4000-8000-000000000001","rule_id": "ssh-disable-root-login","host_id": "sample.example.com","started_at": "2026-11-11T14:22:00.000000000Z","finished_at": "2026-11-11T14:22:03.000000000Z","pre_state_bundle": [{ "StepIndex": 0, "Mechanism": "config_set", "Capturable": true,"CapturedAt": "2026-11-11T14:22:00.400000000Z" }],"apply_steps": [{ "StepIndex": 0, "Mechanism": "config_set", "Capturable": true,"Success": true, "Detail": "applied", "Stranded": false, "Staged": false }],"validator_results": [{ "Name": "sshd_t_syntax_check", "Passed": false,"Detail": "sshd -t reported an error", "Evidence": "sample output" }],"rollback_results": [{ "StepIndex": 0, "Mechanism": "config_set", "Success": true,"Detail": "restored [post-state: matches pre-state]","PartialRestore": false, "Source": "inline","ExecutedAt": "2026-11-11T14:22:02.800000000Z" }],"decision": "rolled_back","severity": "high","framework_refs": [{ "FrameworkID": "cis_rhel9_v2", "ControlID": "5.1.20" },{ "FrameworkID": "nist_800_53_r5", "ControlID": "AC-6(2)" }]}
Why now
AI agents are about to make more production changes than humans ever did. That is fine, provided someone can answer one question: can you prove the change was safe, and undo it if it wasn't?
Put OpenWatch and Kensa in front of your fleet, and your agents.