Legacy code, modernized by supervised AI agents.
Founded in Singapore in January 2026, Stratamend is building an agentic platform that maps, tests and migrates COBOL and aging Java into modern services. The work is done by Claude Code agents, verified against the legacy system’s real behaviour and approved by your engineers.
- Built on Claude Code
- Runs in your cloud
- Human-approved changes
Illustrative simulation of the agent workflow we are building. Module names are examples.
Critical systems run on code few people can still change
Banks, insurers and public agencies depend on systems written decades ago. Full manual rewrites are slow and risky, while keeping the old code running gets harder every year.
Lines of COBOL estimated to still be in use worldwide (Reuters, 2017).
Knowledge is retiring
The engineers who understand these systems are leaving the workforce, and the business rules they carry are rarely written down.
Rewrites stall
Big-bang rewrites take years, freeze new features and often fail to reproduce what the old system really did.
Modernization is an agent-shaped problem
Migrating legacy code is a long chain of reading, changing, testing and fixing. That loop is exactly what autonomous agents are good at, and what autocomplete-style tools cannot do on their own.
Acts, not just suggests
An agent reads the repository, edits files and runs the build itself. A copilot waits for a developer to accept each line.
Verifies its own work
Every change is checked against tests captured from the legacy system. When tests fail, the agent reads the failure and tries again.
Stays on long tasks
Migrating a module means hundreds of steps across many files. Agents keep the plan and context for the whole job, not one prompt.
Knows when to stop
Agents work inside strict boundaries and hand ambiguous business rules to a human instead of guessing.
Map. Pin. Migrate. Ship.
Agents do the repetitive work. Tests prove the result. People make the decisions.
Map
Agents index the codebase and produce an Atlas: dependencies, dead code, embedded business rules and a risk-ranked migration order.
Pin behaviour
Before anything changes, we record what the current system actually outputs and turn it into golden-master tests.
Migrate
Claude Code agents rewrite one module at a time to a modern stack and iterate until every golden test passes.
Review & ship
Each change arrives as a small pull request with the agent’s reasoning. Your engineers decide what merges.
Autonomous where it helps, controlled where it matters
We are designing for regulated industries from the start, with Singapore’s MAS Technology Risk Management Guidelines and PDPA in mind.
- Designed to run inside your own cloud account, calling Claude via Amazon Bedrock or Google Cloud Vertex AI.
- Least-privilege agents: per-module tool allow-lists and hooks that block out-of-scope edits.
- No agent can merge code. Every change needs passing tests and human approval.
- Agent sessions, diffs and test results are logged for audit.
# Illustrative: one headless Claude Code agent per module, # each working in its own git worktree $ git worktree add ../wt/loan-interest $ claude -p "Migrate the loan-interest module to Java 21. Keep every golden-master test green. Do not edit files outside src/loans/interest/." \ --allowedTools "Read,Edit,Bash(mvn -q test:*)" \ --output-format json # A PreToolUse hook rejects edits outside the module. # The agent sees the rejection and stays in scope. ✔ golden-master tests passing · pull request ready for review
What we are building, in order
Each phase is delivered with design partners on real, sandboxed codebases before the next one starts.
Atlas & test harness
- Codebase mapping for COBOL and Java
- Golden-master test generation from recorded runs
- Migration plan export for engineering leads
Supervised migration
- Single-agent module migration with Claude Code
- Pull requests with rationale and test evidence
- Policy hooks for scope, secrets and dependencies
Parallel fleet
- Many agents in isolated git worktrees
- Session audit log export for risk teams
- Deployment inside customer cloud accounts
Questions we hear often
Is Stratamend available today?
We are an early-stage startup, founded in January 2026, working with a small group of design partners. Partners get hands-on access as each phase of the roadmap ships and help shape what we build next.
Why build on Claude Code?
Modernization needs an agent that can read a large repository, run builds and tests, fix its own failures and work for long stretches without a person driving it. Claude Code is built for exactly that, runs from the terminal and in headless mode, and supports hooks that let us enforce hard boundaries on every action.
Does our source code leave our environment?
It does not have to. Our architecture is designed to run inside your own cloud account and call Claude through Amazon Bedrock or Google Cloud Vertex AI in your chosen region.
What happens when an agent gets something wrong?
It cannot merge anything. A change has to pass the golden-master tests, static checks and a human review. Agent sessions are logged so every change can be traced back to how it was produced.
Which languages come first?
COBOL and older Java (6–8) are the first sources we focus on, migrating to Java 21. Other languages follow based on design-partner demand.
Engineering notes
What we look for in a design partner
We are building Stratamend with a small group of design partners, and we are still adding a few more. This note explains…
Keeping source code inside your cloud account
The first question security teams ask us is where their source code goes. For a bank or an insurer, the codebase of…
Java 6 to Java 21: the migration nobody budgets for
COBOL gets most of the attention in modernization conversations, but many of the systems we hear about are just as constrained by…
Help shape agentic modernization while it is being built.
We are looking for a small number of engineering teams with a legacy system they want to modernize.
You get
- Free early access to each phase as it ships
- A codebase Atlas of one repository
- Direct access to the founding team
We ask for
- A sandboxed repository we can work on
- A short feedback call every two weeks