Teams already on Cloud Service whose pipelines fail on removed APIs
Fix Cloud Manager Code Quality failures from deprecated AEM APIs
Pipelines failing since Adobe removed Guava, Log4j 1, Jetty and other APIs? We find every usage and deliver reviewed pull requests that pass Code Quality.
What you get
A green Cloud Manager pipeline and code that is ready for the next removal dates (31 March 2027 and 31 December 2027).
- Scan of every module for removed and soon-removed APIs
- Pull requests grouped by pattern, with tests
- Check against the March 2027 and December 2027 removal lists
- Hand-over notes for anything needing a design decision
What our AI does
The AI runs on servers we operate; your code is not sent to third-party AI services without your written consent.
- Rewrites Guava, Log4j, Felix SCR, Sling Commons JSON and similar usages
- Verifies each rewrite before a human sees it
Ways to work
- Done for you: We run the whole job. Your team approves pull requests and signs off milestones.
- Done with you: Our pipeline opens the pull requests; your developers or your current partner review, adjust and merge them. Lower price, your team learns as it goes.
- Self-serve: Your team runs our factory tools on your own code, with our AI server behind them and our engineers on call.
Price
Fixed quote after the free scan. The readiness scan and the Blueprint are free.
Questions
We are already on Cloud Service. Is this relevant?
Yes. Since 14 April 2026 Cloud Manager fails builds that use removed APIs, and since 28 September 2026 environments still using them miss critical Adobe updates.