Situation
Legacy migration is difficult to trust when repositories contain many dependencies, inconsistent patterns, and behavior that must survive translation.
Agentic software modernization
LegacyLens
An agentic modernization platform that treats migration as an engineering workflow rather than a one-shot code translation. It combines repository intelligence, planning, transformation, dependency awareness, post-migration validation, provenance, and release gating.
Project story
Task
Build a modernization workflow that could understand a repository before changing it, plan the migration, transform code with context, and prove whether the result was ready to release.
Action
- Used AST/CTags analysis and dependency intelligence to build deterministic repository context before generation.
- Stored analysis artifacts in Qdrant and retrieved bounded context instead of sending the whole repository to the model.
- Separated planning, context-grounded conversion, post-migration QA, repair, and release gating into explicit workflow stages.
Result
- Turned modernization into an observable engineering workflow rather than a one-shot LLM translation.
- Added structural and execution-aware validation plus a release gate so generated code could be inspected before packaging.
Interactive demo · BYOK
Try LegacyLens live
Bring your own provider key to create a short-lived session for this project. The portfolio does not store the credential.
Used once to create the temporary portfolio session. It is not stored by the portfolio.
One session · reusable across project pages · provider key never stored