When working with Agile, you need to control architecture, satisfy non-functional requirements, and reduce technical debt in short iterations. In this paper find out how the CAST AIP can be incorporated into a continuous integration environment to evaluate if newly integrated components violate rules of good architectural and coding practice affecting security, robustness, changeability, performance efficiency, and maintainability; adhere to the application’s architectural rules; and have structural problems that create technical debt.