Check the findings
Compare the component inventory and dependencies with the source provided. Review missing context and the rationale behind modernization recommendations.
Evaluation approach
Evaluate the output against your application.
Use source evidence, architecture assumptions and reviewable artifacts to evaluate an assessment. Validated comparative benchmark results are not published on this page.
Review the assumptions
Check the selected AWS services, region, sizing and availability requirements. A cost estimate should be read together with those assumptions.
Inspect the delivery scope
Review generated artifacts, prerequisites and blockers. Distinguish an architecture recommendation from a supported automatic deployment path.
Use actual reports
Public reports show application-specific findings. An illustrative walkthrough explains the decision process; it is not a benchmark or a customer success result.
Browse public reportsLet’s map your next step on AWS.
Discuss your codebase, target architecture and delivery requirements in a technical demo.
Have an open-source application? Request a public repo assessment.
Requests are reviewed before analysis. Public reports are published with your consent.