The product line
Four products. One evidence philosophy.
KodeCapturepreserves what shipped, KodeBack recovers what matters, KodeAtlas remembers why it exists, andKodeProofcontrols what changes next. Each product has a distinct job while sharing the same commitment to evidence, explicit scope, and honest uncertainty.
| KodeCapture | KodeBack | KodeAtlas | KodeProof | |
|---|---|---|---|---|
| Primary problem | The deployed application must be preserved before it changes or disappears | The application runs, but usable source is missing, stale, or untrusted | The code exists, but its history, intent, risk, planned work, and active work are fragmented | An agent can make the change, but the team cannot safely trust the diff alone |
| Starting authority | The live application, declared routes, and observed browser-visible behavior | A sealed donor and captured behavior | Git history, GitHub collaboration records, repositories, tasks, tests, and explicit evidence | An immutable before-state and declared transaction |
| Main output | Replayable evidence workspace plus explicit capture and replay limits | Editable recovery workspace plus evidence and residuals | Verified archive today; evidence-backed symbol context, durable anchors, and coordination in future phases | Candidate, causal verdict, evidence, and controlled transfer or block |
| Current stage | Early access and design-partner onboarding | Selected assessments and internal research | Archive CLI v0.2.0; context platform in development | Private alpha and controlled trials |
| Primary CTA | Request early access | Request a recovery assessment | Explore the archive foundation or discuss context early access | Apply for a private-alpha trial |
Shared foundation
Different products, shared discipline.
The products share principles and selected engines for:
- immutable input, before-state, or source evidence
- source, dependency, and historical provenance
- protected surfaces and declared boundaries
- bounded semantic judgment
- deterministic mutation where coverage exists
- behavior, boundary, and context evidence
- rollback and controlled transfer
- append-only history
- longitudinal evaluation
They remain distinct products. KodeCapture can preserve an app without a recovery engagement,KodeBackcan consume existing authorized artifacts, KodeAtlas can archive and explain ordinary repositories, andKodeProofcan guard changes in source that was never recovered.
Take the next step
Know which hard moment you are in?
Start with capture when the deployed application is the truth, recovery when maintainable source is missing, memory when history and intent are fragmented, or change control when the next AI-driven refactor carries unacceptable risk.