ZeKoder Audit Coming soon
A signed, linked record of how every change was built. Connect requirements, agent sessions, commits, tests and human reviews into evidence your clients can check for themselves.
In development. Evidence capture, client portals and reports are coming later.
Chain verified Works with the agents and tools you already use
Integrations, not customers. Some adapters are in beta.
The proof gap
Coding agents now write many of the changes. The commit history doesn't say which, or who checked them.
Security reviews, DORA supplier checks and sector rules ask you to show controlled development.
It sits across trackers, agent logs, git, CI and scanners, and pulling it together is manual work.
ZeKoder Audit will join it into one signed, linked record. Coming
How ZeKoder Audit works Coming
Developers keep working the way they do now. ZeKoder Audit will take the notes.
The ZeKoder apps, hooks, CLI or adapters will record the work. No extra steps for developers.
[ •‿• ] zekoder 0.4.2 · recording $ claude "add refund endpoint for REQ-142" ✓ session sess_8f2…a91c linked to REQ-142 ✓ 3 commits captured · 14 test results recorded
Each change will be tied to its requirement, agent session, tests and reviewer.
which agent wrote this, and who approved it?
Every event will go into a signed, append-only record.
Reports, a client portal and sign-offs anyone will be able to verify.
Client portal · Release 2.4
Sample · fictional data
Evidence report
Northwind Payments API · Release 2.4
Period 1 Sep to 30 Sep 2026
Chain intact ZKR-2026-0412 · 2026-10-13T14:02:11Z · sha256 a3f9…7c21 · verify at portal.zekoder.[tld]/v/ZKR-2026-0412 · page 1 of 18
2. Requirement traceability
ZKR-2026-0412 · page 7 of 18
Sample report Audit · Coming
This is what your client's reviewer will receive with ZeKoder Audit: a plain, signed document they can check for themselves.
Requirement and client sign-off. What was asked for, and who on the client side agreed it.
Agent session and human review. Which agent wrote the change, and which person approved it.
Report ID, UTC timestamp, hash and verify link. On every page, so any copy can be checked against the record.
Open the sample report Coming
Fictional project data, clearly labelled as a sample.
Who it's for
Capabilities Audit, coming soon
The ZeKoder apps, Claude Code, Codex, Cursor, git hooks and CI, all into one record.
Ask "which agent wrote this, and who approved it?" and get a linked answer.
Append-only and timestamped. Third parties will be able to check it without trusting us.
Requirements, change requests and release acceptance, recorded as signed events.
See the requirements, tests and sign-offs a change touches, always with a confidence level.
Traceability reports, security questionnaire answers and sector packs.
Sector packs in developmentSovereign by design Audit, coming soon
A managed service with your record kept in the EU.
Run ZeKoder inside your own infrastructure, under your own access rules.
No outside connection needed. Use the models you host yourself.
Honest about limits
Design-partner programme · Audit Audit, coming soon
ZeKoder Audit, with the signed evidence record, launches later. We're working with a small group of agencies and suppliers to shape it first.
FAQ
ZeKoder Desktop is free for individuals and comes with in-repo issue management. Audit, coming soon, adds the signed record of how each change was built, plus client portals, sign-offs and reports.
