vFunction EBAs for AI-Driven Modernization

Are your mission-critical systems stuck on oversized EC2 instances, or frozen with no path to cloud-native architectures like EKS and ECS? vFunction Experience-Based Accelerations (EBAs) are designed to accelerate refactoring and re-architecting work directly inside client environments, building actionable modernization plans and executing them in manageable stages. While AI coding tools are powerful, LLMs often hit context limits or fail to understand business domains on large codebases. By combining runtime analysis, static analysis, and data science, vFunction gives Kiro and other code assistants the context and engineered prompts they need to refactor consistently and correctly — even on applications with millions of lines of code. The vFunction and AWS joint EBA is an opportunity to bring together all stakeholders and leadership to streamline and execute the critical stages of the modernization project. Customers seeking this EBA should have already discussed the details of their project plans (including documentation) with AWS and vFunction. This Marketplace offering provides two distinct engagement models to support your modernization journey: Engagement Models EBA 1-AI Modernization Sprint: This entry-point sprint analyzes your application at runtime to define service boundaries. Targeting a single, high-value domain , it delivers a fully refactored, AI-extracted service running on AWS (EC2/EKS/ECS). You leave with a working service and a prioritized modernization roadmap. EBA 2-AI Modernization at Scale: Expanding the momentum of EBA 1 across all high-priority domains. By leveraging the complete toolchain—vFunction MCP, Amazon Kiro, and AWS Transform—this phase refactors and deploys your key services to AWS. This engagement significantly boosts your Modernization Index and establishes a repeatable process for independent modernization. Technical Pre-requisites -Java 1.6+ or .NET Framework 4.6+ application(s) in scope. -Ability to deploy vFunction’s data collector in the target environment for runtime monitoring. -A functioning landing zone on AWS (or in progress) — required before EBA kick-off. -CI/CD pipeline in place or planned — needed to deploy refactored services.