Understand the code
Identify application components, dependencies and configuration from your repository.
- Component inventory + dependency map
How it works
Every step carries the application forward.
Start with the code, review the decisions, then choose what to put into action. The architecture, cost model and deployment artifacts use the same application findings.
Make the AWS decisions
Review modernization recommendations, target services, cost scenarios and migration order together.
- Architecture + costed migration plan
Review the delivery plan
Inspect the generated infrastructure and pipeline files. Resolve blockers and approve the deployment.
- Deployment bundle + plan preview
Run it in your AWS account
The saasups team provisions supported workloads in your AWS account after your approval, and you follow the deployment logs. Current compute paths cover EC2 and EKS.
- AWS resources + application deployment
Understand the boundaries
A plan can surface work that needs engineering judgment: code refactoring, data migration, unsupported dependencies or a separate delivery path. Review these requirements before deployment.
- Scope depends on the application's evidence and target architecture
Let’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.