CI/Lock vs HeimWall

CI/lock collects trusted telemetry across every checkpoint between commit and production, CI/CD builds, security scans (SAST/DAST/SBOM), runtime + cluster integrity...

Signal, not surveillance. See how your engineers use Cursor, Claude Code, and Copilot: catch leaked secrets, PII, and confidential data, without blocking them or reading...

About CI/Lock

CI/lock collects trusted telemetry across every checkpoint between commit and production, CI/CD builds, security scans (SAST/DAST/SBOM), runtime + cluster integrity (Falco, Linkerd mTLS, kube-bench), and continuous compliance (CSPM, FIPS, STIG). Signed as in-toto evidence for FedRAMP 20x, the EU Cyber Resilience Act, NIST 800-204D, SLSA, CMMC, and human-controlled cryptographic gates for AI-agent workflows. Witness-compatible, built on the rookery attestor factory. The DSSE + in-toto envelopes CI/lock emits are the same shape across every stage.

About HeimWall

Signal, not surveillance. See how your engineers use Cursor, Claude Code, and Copilot: catch leaked secrets, PII, and confidential data, without blocking them or reading their prompts. Nothing sits in your send path, your prompt reaches the tool untouched, and what you type into an AI tool is never sent to us. To read your prompt before it is sent, the app reads the composer through the macOS Accessibility API and watches the clipboard. Accessibility is a wide permission and macOS does not offer a narrower one for this.