AWS and rhino.ai have agreed a multi-year collaboration to help businesses modernise legacy software, using governed business logic to guide AI agents from discovery through deployment. The practical pitch is not simply an agent that writes code: it is a managed process for understanding old systems, transforming them and keeping a record of the decisions along the way.
AWS AI Watch analysis
What happened
The agreement brings together rhino.ai’s Logic Hub, which the company says reconstructs and governs business logic across legacy systems, and a modernisation workbench coordinating rhino agents, human experts and AWS services including AWS Transform and Amazon Bedrock AgentCore.
The collaboration is organised around understanding existing systems, modernising them and reusing approved patterns across repeated transformations. Two rhino.ai offerings, for legacy modernisation and mainframe modernisation, are available through AWS Marketplace. The company says its platform runs inside a customer’s AWS environment, with logic artifacts traceable to their source and human approval gates available before later generation and deployment.
rhino.ai also cites a financial-services engagement in which it says it reconstructed and modernised more than 500 undocumented Java processes in nine months, against an original 18-month scope. It says some federal engagements achieved 60% faster discovery. Those are company-reported customer results, not an independent comparison.
Why it matters
Legacy modernisation often begins with the tedious task of working out what decades-old systems actually do. This partnership aims to turn that knowledge into a governed, machine-readable record that agents can use during the transformation, rather than treating an AI-generated plan as the finish line.
For customers, the promise is a clearer path from old code to deployed replacement, with traceability and human approval available along the way. The harder test is whether the approach works reliably across the tangled, idiosyncratic systems that make modernisation such a long job in the first place.
Our read
The useful idea here is making business rules explicit before asking agents to change the systems built around them. That is more compelling than sprinkling “agentic” over a code-conversion tool and hoping nobody asks what happens when it meets a mainframe.
The cited customer examples are encouraging, but they come from rhino.ai. Organisations considering the platform should ask for evidence on their own systems, including how reconstructed rules are checked and who signs off before deployment.
What to watch
- Whether AWS and rhino.ai publish more detail on how business logic is validated against source systems.
- How customers use the approval gates and traceability features in live transformations.
- Whether the reported discovery and delivery gains hold across other customer projects. Activity teaser: AWS and rhino.ai are joining forces on AI-assisted modernisation, aiming to take legacy systems from discovery all the way to deployment. The approach pairs a governed record of business rules with agents, human experts and AWS services. rhino.ai says one financial-services project covered more than 500 undocumented Java processes in nine months, against an original 18-month scope. That is a striking company-reported result. The real test is whether the method can safely make sense of other organisations’ legacy estates. Should companies let AI agents help carry modernisation through to deployment, or keep them firmly in the recommendation seat?
Discussion spark: Should companies let AI agents help carry legacy modernisation through to deployment, or keep them firmly in the recommendation seat?
Sources and evidence
not affiliated with or endorsed by Amazon Web Services (AWS)