Track one01
KodeBack recovery assessment

Buy clarity before committing to a recovery.

A good fit may include:

  • a deployed application whose usable source is missing or stale
  • a vendor or agency handoff that left production ahead of the repository
  • an acquisition with a functioning application but uncertain maintainability
  • an Electron or browser-extension product with incomplete build ownership
  • a high-value interactive web application whose behavior must be captured before modernization
  • a need to retain one critical capability while deliberately removing others
Request a KodeBack assessment
Track two02
KodeProof private alpha

Evaluate one bounded, risky change honestly.

A good fit may include:

  • a JavaScript/TypeScript-family repository
  • a risky decomposition, module move, consolidation, hard cut, or public-contract refactor
  • an engineering owner who can define project gates and review the result
  • willingness to compare workflow cost, catches, false blocks, and independent task quality
  • no requirement for unattended production transfer
Apply for private alpha

What participation requires

Clear authorization and a named technical owner.

  • clear authorization
  • a named technical champion
  • bounded scope
  • honest disclosure of constraints
  • regular feedback
  • acceptance that the correct result may be a refusal or recommendation not to proceed

It does not require public reference permission, a polished innovation program, or pretending the product is more mature than it is.

General route

Tell us where the uncertainty is.

Use the general form for company, research, partnership, or routing questions. Do not send sensitive artifacts here.

General inquiry

Start with the problem

Please do not submit source archives, credentials, HAR files, private URLs, or confidential materials through this form.

Form endpoint not configured yet. Set PUBLIC_GENERAL_FORM_ENDPOINT before launch; this form will not send until then.

Take the next step

Already know your track?

Use the dedicated KodeBack or KodeProof intake so the first conversation starts with the right technical context.