ZeKoder Desktop
Plan work as issues, hand each step to Claude Code, Codex, Cursor, OpenCode or Pi, and review the result before it merges. Keep your agents; ZeKoder runs them side by side.
Plugins for frontier agent harnesses such as Claude Code and Codex.
Chain verified Works with the agents and tools you already use
Integrations, not customers. Some adapters are in beta.
ZeKoder apps
Plan work as issues, hand each step to the right agent from any vendor, and review the result from your desk, your tablet or your phone.
Desktop
Tablet and mobile
The proof gap
Agents now produce a large share of changes in small teams. 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. Pulling it together takes days.
ZeKoder Teams will join it into one signed, linked record. Coming
How evidence works on the Teams plan Coming
Developers keep working the way they do now. ZeKoder Teams will take the notes.
The ZeKoder apps, hooks, CLI or adapters. 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 is tied to its requirement, agent session, tests and reviewer.
which agent wrote this, and who approved it?
Every event goes into a signed, append-only record.
Reports, a client portal and sign-offs anyone can 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 Teams · Coming
This is what your client's reviewer will receive on the Teams plan: 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.
Fictional project data, clearly labelled as a sample.
Who it's for
Turn your next security questionnaire into a link.
ZeKoder for agenciesCapabilities
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 can 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 developmentPricing
For solo founders and developers who want to ship faster with several agents at once.
[£ price]per month
For teams who build for demanding clients and need to show how every change was made.
[£ price][per seat / per project] per month
Sovereign by design
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 · Teams
ZeKoder Teams, with the signed evidence record, launches later. We're working with a small group of agencies and suppliers to shape it first.
FAQ
Individual gives you the ZeKoder apps to run agents from several vendors through workflows, with issues built in. Teams, coming later, adds the signed record of how each change was built, plus client portals, sign-offs and reports.
