Private alpha
One repository. One risky change. One honest evaluation.
The KodeProof private alpha is for engineering teams willing to evaluate the workflow—not simply request early access to another coding agent.
Good-fit transactions
Pick a bounded change whose failure would be expensive.
- monolith decomposition
- module or package relocation
- helper consolidation
- public CLI or export-contract refactor
- artifact/schema hard cut
- selected multi-repository dependency wave
- post-recovery structural cleanup
Partner requirements
A technical owner who will review the uncomfortable parts.
- legal authority to provide and run the repository
- JavaScript/TypeScript-family project compatible with the current provider stack
- named technical owner
- exact project commands or willingness to establish them
- bounded transaction scope
- willingness to review catches, false blocks, and missing coverage
- willingness to meet regularly during the trial
- no expectation of unattended production transfer
- permission to retain sanitized aggregate telemetry only if separately agreed
What the trial measures
Task quality, safety, delivery, and friction.
- task completion
- original-worktree integrity
- transfer correctness
- candidate regressions
- false confidence
- catches and false blocks
- time and cost overhead
- command and tool friction
- evidence usefulness
- agent/harness compatibility
- quality of the final handoff
What we provide
Trial scoping, environment and capability preflight, transaction declaration support, isolated execution, native evidence, independent post-run review, findings, and product follow-up on confirmed gaps.
Application
Tell us about the repository, the refactor, and why it is risky.
Do not submit source archives, credentials, private URLs with tokens, or confidential code through the public form. Secure follow-up comes after qualification.
Fallback email
[KodeProof alpha email]