The product line
Two products. One evidence philosophy.
KodeBack and KodeProof address different stages of the software lifecycle. One helps regain practical ownership of deployed software. The other controls the way software changes under AI-assisted engineering.
| KodeBack | KodeProof | |
|---|---|---|
| Primary problem | The application runs, but usable source is missing, stale, or untrusted | An agent can make the change, but the team cannot safely trust the diff alone |
| Starting authority | The deployed donor and captured behavior | An immutable before-state and declared transaction |
| Main output | Editable recovery workspace plus evidence and residuals | Candidate, causal verdict, evidence, and controlled transfer or block |
| Current stage | Selected assessments and internal research | Private alpha and controlled trials |
| Primary CTA | Request a recovery assessment | Apply for a private-alpha trial |
Shared foundation
Different products, shared discipline.
The products share principles and selected engines for:
- immutable input or before-state
- source and dependency provenance
- protected surfaces
- bounded semantic judgment
- deterministic mutation
- behavior and boundary evidence
- rollback and controlled transfer
- append-only history
- longitudinal evaluation
They remain distinct products. KodeBack does not require KodeProof, and KodeProof can operate on ordinary source repositories that were never recovered.
Take the next step
Know which hard moment you are in?
Route a deployed-software recovery problem to KodeBack or a risky AI-driven refactor to KodeProof. If the boundary is unclear, start with the company.