DevToolsSecurityAICompliance

AI Code Sign-off Ledger: Hardware-Signed Decisions

Hardware-signed decision tracking for AI-generated code changes, solving audit and compliance pain

Problem
A Show HN launches AnchorGit: a hardware-signed Git decision ledger for AI code. It reflects a new problem: AI agents change code more often, but who approved which change and why is hard to trace. On Reddit developers also discuss that AI lowers the barrier but technical skill is still needed to scale, with trust and transparency at the core.
Solution
A lightweight tool: on Git commit or merge, require a hardware key (e.g., YubiKey) to sign the change rationale and approver, writing decision metadata into a verifiable ledger. A simple audit view shows each AI-generated change's origin, approval chain, and signature status.
Users
Small teams using AI agents to write code, compliance-sensitive dev teams needing audit trails
MVP
Git hook or CI plugin requiring hardware signature on merge; record rationale, approver, and timestamp; local audit view; export verifiable change log; basic GitHub/GitLab integration
Revenue
Per-seat subscription, or open-source core with enterprise audit dashboard; affiliate for hardware keys
Why now
AI-generated code is reaching production, leaving an audit and trust gap; hardware signing infra is mature, and an indie dev can build a light integration

Source discussions · 3

  1. Hacker NewsShow HN: AnchorGit – Hardware-signed Git decision ledger for AI code1↑ 0
  2. Reddit[r/SaaS] Trust or money? (Build log)
  3. Reddit[r/SaaS] Why SaaS and Apps will still be in demand
← Back to list